Java Application for handling records(CRUD)

javaxml

I am new to JavaEE and am faced with a tight situation here.

I have to develop a Java application for (CRUD) handling records and saving and loading an XML concerning that record. Obviously, I won't be asking you to do this for me. What I would be asking you is to give me some hints/pointer. Initially I thought JAXB would be enough for this but after putting a lot of time learning it and implementing the program I realized that it just can create the XML and read it but for update, delete I would have to do something else. Even if it wasn't for update and delete features requirement for my project I would still think that by just using JAXB is not a good implementation.

I was wondering if "REST with Java (JAX-RS) using Jersey" should do the trick for me. ?

Best Answer

JAX-RS isn't really going to help you for this. Much as JAX-B is for binding and unbinding XML to Java, JAX-RS is about building and consuming RESTful services. Neither really deals with data persistence.

What you need to look at is an XML database, such as BaseX, which allows you to use XQuery to query and manipulate your XML.

Related Solutions

Java – Selecting a JAX-RS Implementation for a New Project

I've grown to love Dropwizard for an overall solution

Rather than go with some huge application container approach, Dropwizard advocates a lightweight solution that offers much faster development cycles. Essentially, it provides the glue for the following well-known frameworks:

Jetty (HTTP)
Jersey (JAX-RS)
Jackson (JSON or XML)
Guava (excellent additions to JDK libraries)
Metrics (real time application monitoring)
Hibernate Validator (input verification)
OAuth (RESTful authentication)

The combination of the above, coupled with a solid approach to functional testing, gives a complete solution to getting your service up and running quickly.

Yeah? And the JAX-RS question I asked...

You'll notice that their choice was Jersey, the reference JAX-RS implementation. Being a RESTEasy guy I thought this would be a problem, but there was zero learning curve. The two are largely interchangeable. However, I would say that the Jersey client offered a fluent interface for constructing tests. An example would be...

 @Override
  protected void setUpResources() {
    addResource(new HelloWorldResource("Hello, %s!","Stranger"));

    setUpAuthenticator();
  }

  @Test
  public void simpleResourceTest() throws Exception {

    Saying expectedSaying = new Saying(1,"Hello, Stranger!");

    Saying actualSaying = client()
      .resource("/hello-world")
      .get(Saying.class);

    assertEquals("GET hello-world returns a default",expectedSaying.getContent(),actualSaying.getContent());

}

Java – Exception Handling in Java Web Applications

1) No.

2) Not if you put relevant information into the Exception's message - I find that a much preferable alternative.

Best Answer

Related Solutions

Java – Selecting a JAX-RS Implementation for a New Project

Java – Exception Handling in Java Web Applications

Related Topic