Category: Java

From time to time I have to implement some SOAP based web services. Usually these web services are used for application integration so the contract first approach is used where one creates the WSDL  document first.

To create the server stub from the WSDL document I found out that using Maven in combination with NetBeans is the most straight forward approach.

Just choose “New File” from the menu:

package ch.simas.demo.ws;

import javax.ejb.Stateless;
import javax.jws.WebService;

@WebService(serviceName = "CalculatorService", 
  portName = "ICalculator", 
  endpointInterface = "org.example.ICalculator", 
  targetNamespace = "http://Example.org", 
  wsdlLocation = "META-INF/wsdl/calculator.wsdl")
@Stateless
public class CalculatorService {

    public java.lang.Integer add(java.lang.Integer a, java.lang.Integer b) {
        //TODO implement this method
        throw new UnsupportedOperationException("Not implemented yet.");
    }

    public java.lang.Integer subtract(java.lang.Integer a, java.lang.Integer b) {
        //TODO implement this method
        throw new UnsupportedOperationException("Not implemented yet.");
    }
}

<plugin>

Hint for Eclipse/JBoss Tools users: This works not only in @NameQuery!

If you get a error 500 without any additional information. when developing a REST service you probably have a class as parameter or return value that has no default constructor!

I had problems using Git behind a proxy. The solution took me some time so here is how I solved the problem:

First I had to set HTTP_PROXY and HTTPS_PROXY.

Then I encountered a problem with the SSL certificate. So I  had to set GIT_SSL_NO_VERIFY=1

That’s all.

JTAF a track and field event management solution is ready as SaaS (Software-as-a-Service) in the OpenShift cloud: http://jtaf-simas.rhcloud.com/jtaf/

JTAF is open source and available on GitHub: https://github.com/simasch/jtaf

It uses Java EE 6 with REST services in the back end. The front end is entirely developed using JavaScript and HTML5. JTAF does yet not use any JavaScript frameworks to keep it as lean as possible.

Some thoughts about application configuration (in German):

http://www.simas.ch/2014/03/applikationskonfiguration-in.html

There is an interesting report form Markus Eisele, Simon Maple, Hildeberto
Mendonca, Oleg Shelajev and Oliver White available on RebelLabs about Migrating from GlassFish to JBoss or TomEE.

Check it out: http://zeroturnaround.com/rebellabs/abandon-fish-migrating-from-glassfish-to-jboss-or-tomee/#!/

There are a lot of people talking about Java EE configuration these days. But often they forget about JNDI (Java Naming and Directory Interface).

Configuration using JNDI has the advantage that you can use dependency injection. i.e.

@Resource(mappedName = “java:global/mystring”)
private String mystring;

The configuration for example in JBosss EAP or Wildfly is pretty simple made in the standalone.xml (or domain.xml) file:

 
    <simple name="java:global/mystring" 
            value=”My String” 
            type=”java.lang.String”/>
     
     

As you can see the type can be defined. If you need more complex objects simply use ObjectFactory http://docs.oracle.com/javase/7/docs/api/javax/naming/spi/ObjectFactory.html

Read more about JNDI in WildFly: https://docs.jboss.org/author/display/WFLY8/JNDI+Reference
and more about ObjectFactory: http://middlewaremagic.com/jboss/?p=1690

Lukas Eder just posted a note about when to use a framework: http://blog.jooq.org/2014/03/05/when-to-use-a-framework/

I totally agree! And I think it is not only limited to big frameworks like JPA/Hibernate.
Often developers spend a lot of time evaluating a library that solves their problems. But sometimes it would be easier to write a few lines of code to solve the problem.

If you do it your self there are two advantages 1) you better understand the problem because you solved it on your own and 2) your solution is exactly what you need. There are no dependencies to a big framework or library that may have their own dependencies etc.

For sure my idea does not scale. If your problem is O/R-mapping it doesn’t make sense to create your own Hibernate. But if you just need some small utilities – why not think about…