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 Thu, 07 Jun 2012 09:25:38 GMT


Thank you.

My FileNotFoundException Wrapper starts with


@Webfault(name="FileNotFoundExceptionWs", targetNamespace="/", faultBean="")

The implementation of WebFault under JDK 6.0 takes 3 arguments see above, while WebFault under
JDK 7.0 takes 4 arguments

@Webfault(name="FileNotFoundExceptionWs", targetNamespace="/", faultBean="",


It compiles under 6.0 because WebFault is in fact an interface only delivered with JDK.60
and it has a implementation somewhere in JDK 6.0 as well using only 3 arguments.


The guilty in my mind is axis2's JavaClassToDBCConverter class which tries to set the messageName
attribute through the WebFault Interface. It fails as shown below.


Martin, I never used endorsements myself unless exactly told how to do it. For me endorsements
are something like a patch and not a midterm robust solution.

I do not understand why I a shall package my FileNotFoundExceptionWs class belonging to my
FileService WebService up/download solution into a jar and then put that jar into the jre/lib/endorsement
directory of my JDK6.0 environment. I would assume, as read on several places, having exact
the same problem, Google shows 1010 entries for this bug, that I have to seek the JDK7.0 jar
file which implements the WebFault class and place this JDK7.0 jar file into jre/lib/endorsed


NOW - I am confused, and hope you can help me , can you clarify this.


I expect from endorsement that Axis2's JavaClassToDBCConverter finds the proper class in a
jar file in the endorsement directory.






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