axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stadelmann Josef" <>
Subject AW: [axis2-1.6.1] jax-ws 2.0 and JavaClassToDBCConverter of axis2-1.6.1
Date Mon, 11 Jun 2012 16:44:49 GMT
Hi Martin

or everyone able to help me.


after all I have found what causes me the problem, the stack dump as shown in a previous mail.
Understanding is required to develop a solution.

The problem is that rt.jar has a Webfault.calss under; (checked using $ jar tf
rt.jar | grep Webfault) for both jdk1.6.0_30 and jdk1.7.0_03/jre/lib/rt.jar's


Then I extracted the two classes, one after each other, and then I used $ javap -c Webfault
to see a de-compilation without any side effects of high level tools such as NetBeans!!!

The result was as such.


C:\Program Files\Java\jdk1.6.0_30\jre\lib>javap -c WebFault

Compiled from ""

public interface extends java.lang.annotation.Annotation{

public abstract java.lang.String name();

public abstract java.lang.String targetNamespace();

public abstract java.lang.String faultBean();




C:\Program Files\Java\jdk1.7.0_03\jre\lib>javap -c WebFault

Compiled from ""

public interface extends java.lang.annotation.Annotation{

public abstract java.lang.String name();

public abstract java.lang.String targetNamespace();

public abstract java.lang.String faultBean();

public abstract java.lang.String messageName();



As you can see the WebFault of jdk1.7 has one interface to an attribute more, and the relevant
implementation WebFaultAnnot.class supports this by getters and setters is called through
the use of the proper Interface class residing in rt.jar which is either jdk1.6 or jdk1.7


Our OpenVMS runs on JDK1.6 and HP does not yet provide JDK1.7, we'r just about to have a meeting
tomorrow with the responsible HP Enterprise Account Manager and some experts tomorrow about
a clear Java for OpenVMS road map. and other issues.


But until then . . .  I think I need to endorse something. But what? 


Under C:\Program Files\NetBeans 7.1.2\java\modules\ext\jaxws22\api I have found jaxws-api.jar
which has a WebFault.class and extracting the WebFault.class and looking at it with javap
-c WebFault shows me that this WebFault.class has 4 interfaces to Attributes while the previous
NetBeans 7.1.1 comes with the same file but has  a WebFault.class with only 3 interfaces to
attributes. This has confused me before I realized that this classes may have some compile
time effect only but at run time the class is taken from the active jre/lib/rt.jar.


That is why I can compile great but run into problems when I want to deploy my web service
solution into webapps of Catalina/Tomcat, but only if it runs under jdk1.6


Question: would it be sufficient to endorse the api jar file(s) found under C:\Program Files\NetBeans
7.1.2\java\modules\ext\jaxws22\api to a jdk1.6/jre7lib/endorsed directory?

The files are 






because I think endorsing the full rt.jar from jdk1.7 to the jre of jdk1.6 does not work,
is too much of an endorsement.


I ask this also because I do not understand what you have suggested me by packaging the FileNotFoundWs.class
in a jar and endorse only this one. I am really confused with that. Because this FileNotFoundWs.class
is just a wrapper which through @WebFault(name, targetnamespace, faultbean, messagename) engages
further interfaces and implementations residing at the proper rt.jar or in one of the small
api jars such as jaxws-api.jar delivered with NetBeans 7.1.*


Josef - very thanks full for your thoughts - and sorry if I miss a bit of understanding of




Von: Martin Gainty [] 
Gesendet: Mittwoch, 6. Juni 2012 19:43
Betreff: RE: [axis2-1.6.1] jax-ws 2.0 and JavaClassToDBCConverter of axis2-1.6.1


Hi Josef

If you could drop your modified FileNotFoundExceptionWs.jar into endorsed dir you can startup
Tomcat with -Djava.endorsed.dirs=C:\Java\jdk1.6.0_01\jre\lib\endorsed
$CATALINA_HOME/bin/java -Djava.endorsed.dirs=/jdk1.6.0_01/jre/lib/endorsed ........ jar bootstrap.jar

does this help?
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten
wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist
unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet
keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen
wir keine Haftung fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire
prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe
quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information
seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les
email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune
responsabilité pour le contenu fourni.



Subject: [axis2-1.6.1] jax-ws 2.0 and JavaClassToDBCConverter of axis2-1.6.1
Date: Wed, 6 Jun 2012 18:09:10 +0200

@Webfault is an annotation in use since JDK 6.0 ...

I understand that this class needs enhancements over time.

What I do not understand is that 


has a method 

    private void attachWebFaultAnnotation(DescriptionBuilderComposite composite) {

        WebFault webFault = (WebFault)ConverterUtils.getAnnotation(

                WebFault.class, serviceClass);

        if (webFault != null) {

            WebFaultAnnot webFaultAnnot = WebFaultAnnot.createWebFaultAnnotImpl();







which is a show stoper for an JDK 6.0 dependent environment, because the line in red works
only within a JDK 7.0 environment.

I have developed "FileNotFoundExceptionWs", a Wrapper class using the @Webfault annotation
with 3 arguments, 

and all builds fine. But depoyment of this service does not work because I run (un-endorsed)
on a JDK 6.0 platform.

where the following error is thrown by Axis2-1.6.1 code as seen above.:

[INFO] Deploying JAXWS annotated class as a service
- MtomFileService12

[INFO] Exception creating Axis Service : null


        at org.apache.axis2.jaxws.description.builder.converter.JavaClassToDBCConverter.attachWebFaultAnnotation(

        at org.apache.axis2.jaxws.description.builder.converter.JavaClassToDBCConverter.setTypeTargettedAnnotations(

        at org.apache.axis2.jaxws.description.builder.converter.JavaClassToDBCConverter.introspectClass(

        at org.apache.axis2.jaxws.description.builder.converter.JavaClassToDBCConverter.buildDBC(

        at org.apache.axis2.jaxws.description.builder.converter.JavaClassToDBCConverter.produceDBC(

        at org.apache.axis2.jaxws.description.impl.DescriptionFactoryImpl.createServiceDescription(

        at org.apache.axis2.jaxws.description.DescriptionFactory.createAxisService(

        at org.apache.axis2.jaxws.framework.JAXWSDeployer.createAxisService(

        at org.apache.axis2.jaxws.framework.JAXWSDeployer.deployClasses(

        at org.apache.axis2.jaxws.framework.JAXWSDeployer.deployServicesInWARClassPath(

        at org.apache.axis2.jaxws.framework.JAXWSDeployer.init(

        at org.apache.axis2.deployment.DeploymentEngine.initializeDeployers(

        at org.apache.axis2.deployment.DeploymentEngine.setConfigContext(

        at org.apache.axis2.deployment.WarBasedAxisConfigurator.setConfigContext(

        at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(

        at org.apache.axis2.transport.http.AxisServlet.initConfigContext(

        at org.apache.axis2.transport.http.AxisServlet.init(

        at org.apache.catalina.core.StandardWrapper.loadServlet(

        at org.apache.catalina.core.StandardWrapper.load(

        at org.apache.catalina.core.StandardContext.loadOnStartup(

        at org.apache.catalina.core.StandardContext.start(

        at org.apache.catalina.core.ContainerBase.addChildInternal(

        at org.apache.catalina.core.ContainerBase.addChild(

        at org.apache.catalina.core.StandardHost.addChild(

        at org.apache.catalina.startup.HostConfig.deployWAR(

        at org.apache.catalina.startup.HostConfig.deployWARs(

        at org.apache.catalina.startup.HostConfig.deployApps(

        at org.apache.catalina.startup.HostConfig.check(

        at org.apache.catalina.startup.HostConfig.lifecycleEvent(

        at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(

        at org.apache.catalina.core.ContainerBase.backgroundProcess(

        at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(

        at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(

        at org.apache.catalina.core.ContainerBase$


google for the red line and wonder how many runs into a similar problem.

endorsing helps but shifts the problem arround, and there is no guarantee 

that endorsing missing jar files adds to the robsutness of the environment!

is there a chance to have Tomcat using the same automatic endorsment facility as maven has
when it builds and test and runs error free




View raw message