You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by robert lazarski <ro...@gmail.com> on 2006/04/12 23:05:51 UTC
[Axis2] 1.0RC1 module problems
Hi all,
I'm trying to port a module from around .94 to RC1 . I had some engagement
problems, so I decided to try deploying the LoggingModule from the user
guide - my module largely follows that example. The debug logs show:
- Deploying module : LoggingModule
- org.apache.axis2.i18n.resource::handleGetObject(modulenotavailble)
- org.apache.axis2.i18n.resource::handleGetObject(modulevalfailed)
- Module validation failed Trying to engage a module which is not available
: logging
- org.apache.axis2.i18n.resource::handleGetObject(modulenotavailble)
- org.apache.axis2.i18n.resource::handleGetObject(modulevalfailed)
- Module validation failed Trying to engage a module which is not available
: logging
Now the steps I followed was:
1) Move LoggingModule.mar to WEB-INF/modules.
2) add <module ref="logging"/> to my services.xml
3) Edit axis2.xml to put <phase name="loggingPhase"/> in the inflow,
outflow, and faults.
4) add <module ref="logging"/> to axis2.xml .
That's the way I remember it working. Any ideas?
Robert
http://www.braziloutsource.com/
Re[2]: Server.userException and InvocationTargetException - what does it mean?
Posted by Martin Wunderlich <ma...@gmx.net>.
Thanks a lot to Vartan, Dies and Robert for your comments. I seem to
have missed Dies' message the first time round, so I am glad that
Robert took it up.
The situation as described by Dies is perfectly correct.
As for mapping Hibernate collections to arrays, I think I could
replace the existing set with arrays.
(the only limitation being this:
" Please note that Hibernate does not support bidirectional
one-to-many associations with an indexed collection (list, map or
array) as the "many" end, you have to use a set or bag mapping.").
In
this case however, I'd lose the code generation capabilities from the
Hibernate tool I'm working with, which for some reason assumes Set as
the default for collections.
I presume going down the adapter road might the most feasible. I have
some manager classes for the POJOs, which provide a facade to the
database (add, delete, update etc.). These classes could also serve as the adapters to convert the
WSDL2Java generated objects that are used on the client side to POJOs
used on the server side. I hope this makes sense, I don't really have that
much experience (as you may have guessed).
Cheers,
Martin
> I agree with dies - just one small caveat. I use hibernate with axis quite a
> bit:
> You can use xs:dateTime
> <http://www.w3.org/TR/xmlschema-2/#dateTime> with
> java.util.Calendar<http://java.sun.com/j2se/1.4.2/docs/api/java/util/Calendar.html>-
> its pretty easy to get from there to
> java.util.Date . Some databinding frameworks - JWSDP for example - support
> java.util.Date directly.
> The way I use Hibernate collections is to map them to Arrays. WSDL handles
> array well. java.util.List and java.util.Set works well in that regard
> directly via Collection.toArray() . For java.util.Map, I create a complex
> type that has an array each of the keys and values, and then just compare
> the size to make sure they're equal.
> For Hibernate based POJO's with lots of fields - you need to map one to one
> the POJO to a complex object. I typically do this in an Adapter.
> HTH,
> Robert
> http://www.braziloutsource.com/
Re: Server.userException and InvocationTargetException - what does it mean?
Posted by robert lazarski <ro...@gmail.com>.
I agree with dies - just one small caveat. I use hibernate with axis quite a
bit:
You can use xs:dateTime <http://www.w3.org/TR/xmlschema-2/#dateTime> with
java.util.Calendar<http://java.sun.com/j2se/1.4.2/docs/api/java/util/Calendar.html>-
its pretty easy to get from there to
java.util.Date . Some databinding frameworks - JWSDP for example - support
java.util.Date directly.
The way I use Hibernate collections is to map them to Arrays. WSDL handles
array well. java.util.List and java.util.Set works well in that regard
directly via Collection.toArray() . For java.util.Map, I create a complex
type that has an array each of the keys and values, and then just compare
the size to make sure they're equal.
For Hibernate based POJO's with lots of fields - you need to map one to one
the POJO to a complex object. I typically do this in an Adapter.
HTH,
Robert
http://www.braziloutsource.com/
On 4/19/06, Dies Koper <di...@jp.fujitsu.com> wrote:
>
> Hello Martin,
>
> Let me first summarize what I think you say your problem is. If I got it
> wrong, no need to read the rest of this e-mail :)
>
> You have POJOs generated by Hibernate. You want to have a method in your
> web service that takes these POJOs as arguments, so that data can be
> exchanged between the client and database with the least hassle.
> However, after generating the WSDD and Java classes from the WSDL that
> you generated from your interface, you notice that some Java types of
> the fields in the Javabeans changed. Right?
>
> First of all, the web service is a middle layer and I wonder whether it
> is a good idea to expose classes that depend so much on your schema
> directly to your clients. A little change to your DB schema would give
> you a lot of maintenance.
>
> As there are no XML types that map to java.util.Set, java.util.Date,
> you'd either have to look at your schema or Hibernate to see if you
> can't have your Hibernate generated POJOs use Java types that can be
> mapped to, or write adapters. I'd go for the latter solution, as it has
> the added advantage of separating the DB and client layers.
>
> Good luck,
> Dies
>
> Martin Wunderlich wrote:
> > Hello Vartan,
> >
> > Thank you very much for your help and your suggestion.
> >
> > In the meantime, I seem to have identified the root cause of my
> > problems and it seems to be on a conceptual level rather than a coding
> > level. Taking a closer a look at the classes generated by WSDL2Java I
> > noticed that the utility will also produce its own versions of any
> > objects (POJOs) that serve as complex type arguments. A number of
> > important changes are made there: final static constants are removed,
> > (de)serializers are added, java.util.Date get converted to Calendar
> > type, Sets are converted to object arrays.
> >
> > This
> > is worsened by the fact that I am using Hibernate for the persistence
> > of these objects and they were auto-generated from the database. I am
> > a bit lost now how to deal with this situation. It seems that I have
> > to create and maintain two versions of the same object type, one for
> > the web service and one for the persistence layer or perhaps work with
> > some sort of adapter class, thereby tripling all the efforts. Seems like
> too much
> > maintenance hassle than I would want to deal with.
> >
> > Are there any
> > established best practices for how to deal with such a situation?
> >
> > Cheers,
> >
> > Martin
>
>
>
Re: Server.userException and InvocationTargetException - what does
it mean?
Posted by Dies Koper <di...@jp.fujitsu.com>.
Hello Martin,
Let me first summarize what I think you say your problem is. If I got it
wrong, no need to read the rest of this e-mail :)
You have POJOs generated by Hibernate. You want to have a method in your
web service that takes these POJOs as arguments, so that data can be
exchanged between the client and database with the least hassle.
However, after generating the WSDD and Java classes from the WSDL that
you generated from your interface, you notice that some Java types of
the fields in the Javabeans changed. Right?
First of all, the web service is a middle layer and I wonder whether it
is a good idea to expose classes that depend so much on your schema
directly to your clients. A little change to your DB schema would give
you a lot of maintenance.
As there are no XML types that map to java.util.Set, java.util.Date,
you'd either have to look at your schema or Hibernate to see if you
can't have your Hibernate generated POJOs use Java types that can be
mapped to, or write adapters. I'd go for the latter solution, as it has
the added advantage of separating the DB and client layers.
Good luck,
Dies
Martin Wunderlich wrote:
> Hello Vartan,
>
> Thank you very much for your help and your suggestion.
>
> In the meantime, I seem to have identified the root cause of my
> problems and it seems to be on a conceptual level rather than a coding
> level. Taking a closer a look at the classes generated by WSDL2Java I
> noticed that the utility will also produce its own versions of any
> objects (POJOs) that serve as complex type arguments. A number of
> important changes are made there: final static constants are removed,
> (de)serializers are added, java.util.Date get converted to Calendar
> type, Sets are converted to object arrays.
>
> This
> is worsened by the fact that I am using Hibernate for the persistence
> of these objects and they were auto-generated from the database. I am
> a bit lost now how to deal with this situation. It seems that I have
> to create and maintain two versions of the same object type, one for
> the web service and one for the persistence layer or perhaps work with
> some sort of adapter class, thereby tripling all the efforts. Seems like too much
> maintenance hassle than I would want to deal with.
>
> Are there any
> established best practices for how to deal with such a situation?
>
> Cheers,
>
> Martin
Re: Re[2]: Server.userException and InvocationTargetException - what does it mean?
Posted by Rhimbo <rh...@yahoo.com>.
Hello Martin,
I have not used WSDL2Java to generate client-side code. So my
following comments might not be so helpful....
I use a WSDD file to deploy my web service. Then I just write
JAX-RPC client code "by hand" using the javax.xml.rpc.* and
org.apache.axis.client libraries.
Would that help your situation? Then you would not have to
address the issue of POJOs or their class definitions that are
different than what you produced before with Hibernate.
My apologies if I didn't understand your last comments.
Vartan
--- Martin Wunderlich <ma...@gmx.net> wrote:
> Hello Vartan,
>
> Thank you very much for your help and your suggestion.
>
> In the meantime, I seem to have identified the root cause of my
> problems and it seems to be on a conceptual level rather than a coding
> level. Taking a closer a look at the classes generated by WSDL2Java I
> noticed that the utility will also produce its own versions of any
> objects (POJOs) that serve as complex type arguments. A number of
> important changes are made there: final static constants are removed,
> (de)serializers are added, java.util.Date get converted to Calendar
> type, Sets are converted to object arrays.
>
> This
> is worsened by the fact that I am using Hibernate for the persistence
> of these objects and they were auto-generated from the database. I am
> a bit lost now how to deal with this situation. It seems that I have
> to create and maintain two versions of the same object type, one for
> the web service and one for the persistence layer or perhaps work with
> some sort of adapter class, thereby tripling all the efforts. Seems
> like too much
> maintenance hassle than I would want to deal with.
>
> Are there any
> established best practices for how to deal with such a situation?
>
> Cheers,
>
> Martin
>
> > Hello Martin,
>
> > Apologies in advance if the comment below is not addressing the
> > right question....
>
>
> > I had to set a serializer and deserializer when passing a complex
> > type or when expecting a complex type as a return value from a call.
>
> > I did something like this on my call object:
> > QName classQName = new QName("http://my.namespace", "Foo");
> > Class cl = Foo.class;
>
> > BeanSerializerFactory bsf =
> > new BeanSerializerFactory(cl, classQName);
> > BeanDeserializerFactory bdf =
> > new BeanDeserializerFactory(cl, classQName);
>
> > call.registerTypeMapping(cl, classQName, bsf, bdf);
>
> > This was for expecting a Java Bean as a return value. I saw a
> > section about complex types that are not Java beans in the AXIS
> > user's guide. Look at the section "Encoding your Beans - the
> > Bean Serializer". Also see the section below it:
> > "When Beans Are Not Enough - Custom Serialization".
>
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re[2]: Server.userException and InvocationTargetException - what does it mean?
Posted by Martin Wunderlich <ma...@gmx.net>.
Hello Vartan,
Thank you very much for your help and your suggestion.
In the meantime, I seem to have identified the root cause of my
problems and it seems to be on a conceptual level rather than a coding
level. Taking a closer a look at the classes generated by WSDL2Java I
noticed that the utility will also produce its own versions of any
objects (POJOs) that serve as complex type arguments. A number of
important changes are made there: final static constants are removed,
(de)serializers are added, java.util.Date get converted to Calendar
type, Sets are converted to object arrays.
This
is worsened by the fact that I am using Hibernate for the persistence
of these objects and they were auto-generated from the database. I am
a bit lost now how to deal with this situation. It seems that I have
to create and maintain two versions of the same object type, one for
the web service and one for the persistence layer or perhaps work with
some sort of adapter class, thereby tripling all the efforts. Seems like too much
maintenance hassle than I would want to deal with.
Are there any
established best practices for how to deal with such a situation?
Cheers,
Martin
> Hello Martin,
> Apologies in advance if the comment below is not addressing the
> right question....
> I had to set a serializer and deserializer when passing a complex
> type or when expecting a complex type as a return value from a call.
> I did something like this on my call object:
> QName classQName = new QName("http://my.namespace", "Foo");
> Class cl = Foo.class;
> BeanSerializerFactory bsf =
> new BeanSerializerFactory(cl, classQName);
> BeanDeserializerFactory bdf =
> new BeanDeserializerFactory(cl, classQName);
> call.registerTypeMapping(cl, classQName, bsf, bdf);
> This was for expecting a Java Bean as a return value. I saw a
> section about complex types that are not Java beans in the AXIS
> user's guide. Look at the section "Encoding your Beans - the
> Bean Serializer". Also see the section below it:
> "When Beans Are Not Enough - Custom Serialization".
Re: Server.userException and InvocationTargetException - what does it mean?
Posted by Anne Thomas Manes <at...@gmail.com>.
You haven't declared the "tns1" namespace.
On 4/17/06, Martin Wunderlich <ma...@gmx.net> wrote:
>
> Hello again,
>
> Since there haven't been any replies, yet, to this questions, I
> thought I could post the relevant bit of the web service's WSDL.
> Please find it below. Sorry about the long post. As I said, the
> sayHello service method is working perfectly fine. It's just the one
> that's using the complex type User that's causing me problems. I'd be
> most greatly for any hints into the right direction.
>
> All the best,
>
> Martin
>
>
> <wsdl:definitions targetNamespace="urn:mypackage.com">
> <!--
> WSDL created by Apache Axis version: 1.2.1
> Built on Jun 14, 2005 (09:15:57 EDT)
> -->
> <wsdl:types>
> <schema targetNamespace="urn:mypackage.com">
> <import namespace="
> http://dataObjects.database.mypackage.com"/>
> <import namespace="
> http://schemas.xmlsoap.org/soap/encoding/"/>
>
> <complexType name="ArrayOf_xsd_anyType">
> <complexContent>
> <restriction base="soapenc:Array">
> <attribute ref="soapenc:arrayType"
> wsdl:arrayType="xsd:anyType[]"/>
> </restriction>
> </complexContent>
> </complexType>
> </schema>
> [...]
> <schema targetNamespace="http://dataObjects.database.mypackage.com
> ">
> <import namespace="urn:mypackage.com"/>
> <import namespace="
> http://schemas.xmlsoap.org/soap/encoding/"/>
> <complexType abstract="true" name="AbstractUser">
> <sequence>
> <element name="contactsForUser1"
> nillable="true" type="impl:ArrayOf_xsd_anyType"/>
> <element name="contactsForUser2"
> nillable="true" type="impl:ArrayOf_xsd_anyType"/>
> <element name="email"
> nillable="true" type="xsd:string"/>
> <element name="firstName"
> nillable="true" type="xsd:string"/>
> <element name="id" nillable="true"
> type="xsd:int"/>
> <element name="lastName"
> nillable="true" type="xsd:string"/>
> <element name="password"
> nillable="true" type="xsd:string"/>
> <element name="projects"
> nillable="true" type="impl:ArrayOf_xsd_anyType"/>
> <element name="targetteams"
> nillable="true" type="impl:ArrayOf_xsd_anyType"/>
> </sequence>
> </complexType>
> <complexType name="User">
> <complexContent>
> <extension base="tns1:AbstractUser">
> <sequence/>
> </extension>
> </complexContent>
> </complexType>
>
> [...]
>
> <wsdl:message name="registerRequest">
> <wsdl:part name="in0" type="tns1:User"/>
> </wsdl:message>
>
> <wsdl:message name="sayHelloRequest">
> <wsdl:part name="in0" type="soapenc:string"/>
> </wsdl:message>
>
> <wsdl:message name="registerResponse">
> </wsdl:message>
>
> <wsdl:message name="sayHelloResponse">
> <wsdl:part name="sayHelloReturn" type="soapenc:string"/>
> </wsdl:message>
>
> <wsdl:portType name="Handler">
>
> <wsdl:operation name="register" parameterOrder="in0">
> <wsdl:input message="impl:registerRequest"
> name="registerRequest"/>
> <wsdl:output message="impl:registerResponse"
> name="registerResponse"/>
> <wsdl:fault message="impl:MyException"
> name="MyException"/>
> </wsdl:operation>
>
> <wsdl:operation name="sayHello" parameterOrder="in0">
> <wsdl:input message="impl:sayHelloRequest"
> name="sayHelloRequest"/>
> <wsdl:output message="impl:sayHelloResponse"
> name="sayHelloResponse"/>
> </wsdl:operation>
> </wsdl:portType>
>
> <wsdl:binding name="HandlerSoapBinding" type="impl:Handler">
> <wsdlsoap:binding style="rpc" transport="
> http://schemas.xmlsoap.org/soap/http"/>
> <wsdl:operation name="register">
> <wsdlsoap:operation soapAction=""/>
> <wsdl:input name="registerRequest">
> <wsdlsoap:body encodingStyle="
> http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:mypackage.com"
> use="encoded"/>
> </wsdl:input>
> <wsdl:output name="registerResponse">
> <wsdlsoap:body encodingStyle="
> http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:mypackage.com"
> use="encoded"/>
> </wsdl:output>
>
> <wsdl:fault name="MyException">
> <wsdlsoap:fault encodingStyle="
> http://schemas.xmlsoap.org/soap/encoding/" name="MyException"
> namespace="urn:mypackage.com" use="encoded"/>
> </wsdl:fault>
> </wsdl:operation>
>
> <wsdl:operation name="sayHello">
> <wsdlsoap:operation soapAction=""/>
> <wsdl:input name="sayHelloRequest">
> <wsdlsoap:body encodingStyle="
> http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:mypackage.com"
> use="encoded"/>
> </wsdl:input>
> <wsdl:output name="sayHelloResponse">
> <wsdlsoap:body encodingStyle="
> http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:mypackage.com"
> use="encoded"/>
> </wsdl:output>
> </wsdl:operation>
> </wsdl:binding>
>
> <wsdl:service name="IHandlerService">
> <wsdl:port binding="impl:HandlerSoapBinding" name="Handler">
> <wsdlsoap:address location="
> http://localhost/MyProject/services/Handler"/>
> </wsdl:port>
> </wsdl:service>
> </wsdl:definitions>
>
> > Dear all,
>
> > I have deployed a couple of web services and I keep getting an exception
> > when calling one of them. I am calling two services. One takes as
> > input a String and returns a String. This one works just fine. Another
> one
> > takes as input a complex type (a Java bean) and has no return value.
> > This is the one that fails with the somewhat cryptic
> > exception give below (both are called using the auto-generated test
> > case). The web service's method
> > is called register() and basically meant to write a User object to a
> > database. Calling "getCause()" returns a null value. The object I pass
> in
> > looks fine. I can out.println() its values.
>
> > Could anyone give me a hint as to what this means? Thanks a lot in
> > advance.
>
> > Cheers,
>
> > Martin
>
> > AxisFault
> > faultCode:
> > {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> > faultSubcode:
> > faultString: java.lang.reflect.InvocationTargetException
> > faultActor:
> > faultNode:
> > faultDetail:
> > {http://xml.apache.org/axis/}hostname:Hermes
>
> > java.lang.reflect.InvocationTargetException
> > at
> > org.apache.axis.message.SOAPFaultBuilder.createFault(
> SOAPFaultBuilder.java:221)
> > at
> > org.apache.axis.message.SOAPFaultBuilder.endElement(
> SOAPFaultBuilder.java:128)
> > at
> > org.apache.axis.encoding.DeserializationContext.endElement(
> DeserializationContext.java:1087)
> > at
> > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown
> Source)
> > at
> >
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
> Source)
> > at
> >
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
> Source)
> > at
> >
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
> Source)
> > at
> > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
> Source)
> > at
> > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
> Source)
> > at
> > com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown
> Source)
> > at
> > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown
> Source)
> > at javax.xml.parsers.SAXParser.parse(SAXParser.java:379)
> > at
> > org.apache.axis.encoding.DeserializationContext.parse(
> DeserializationContext.java:227)
> > at
> > org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
> > at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
> > at
> > org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(
> MustUnderstandChecker.java:62)
> > at
> > org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
> > at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
> > at org.apache.axis.client.Call.invoke(Call.java:2748)
> > at org.apache.axis.client.Call.invoke(Call.java:2424)
> > at org.apache.axis.client.Call.invoke(Call.java:2347)
> > at org.apache.axis.client.Call.invoke(Call.java:1804)
> > at
> >
> > com.mypackage.ServiceHandlerSoapBindingStub.register(
> ServiceHandlerSoapBindingStub.java:270)
> > at
> >
> > com.mypackage.IServiceHandlerServiceTestCase.test1ServiceHandlerRegister
> (IServiceServiceTestCase.java:45)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:39)
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at junit.framework.TestCase.runTest(TestCase.java:154)
> > at junit.framework.TestCase.runBare(TestCase.java:127)
> > at junit.framework.TestResult$1.protect(TestResult.java:106)
> > at
> > junit.framework.TestResult.runProtected(TestResult.java:124)
> > at junit.framework.TestResult.run(TestResult.java:109)
> > at junit.framework.TestCase.run(TestCase.java:118)
> > at junit.framework.TestSuite.runTest(TestSuite.java:208)
> > at junit.framework.TestSuite.run(TestSuite.java:203)
> > at
> > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(
> RemoteTestRunner.java:478)
> > at
> > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(
> RemoteTestRunner.java:344)
> > at
> > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(
> RemoteTestRunner.java:196)
>
>
> --
> ----------------------------------------------------------
> Martin Wunderlich, M.A.
> Translation/Localisation EN <-> DE
>
> www.martinwunderlich.com
> ----------------------------------------------------------
> Free / open-source software for translation/localisation:
> www.martinwunderlich.com/foss-links.html
> ----------------------------------------------------------
> Random aphorism:
> "Aquela reinspiração, sem a qual traduzir é apenas parafrasear noutra
> língua."
> "That new inspiration - without which to translate merely means to
> paraphrase into another language."
> - Fernando Pessoa
> ----------------------------------------------------------
>
>
Re: Server.userException and InvocationTargetException - what does it mean?
Posted by Rhimbo <rh...@yahoo.com>.
Hello Martin,
Apologies in advance if the comment below is not addressing the
right question....
I had to set a serializer and deserializer when passing a complex
type or when expecting a complex type as a return value from a call.
I did something like this on my call object:
QName classQName = new QName("http://my.namespace", "Foo");
Class cl = Foo.class;
BeanSerializerFactory bsf =
new BeanSerializerFactory(cl, classQName);
BeanDeserializerFactory bdf =
new BeanDeserializerFactory(cl, classQName);
call.registerTypeMapping(cl, classQName, bsf, bdf);
This was for expecting a Java Bean as a return value. I saw a
section about complex types that are not Java beans in the AXIS
user's guide. Look at the section "Encoding your Beans - the
Bean Serializer". Also see the section below it:
"When Beans Are Not Enough - Custom Serialization".
Vartan
--- Martin Wunderlich <ma...@gmx.net> wrote:
> Hello again,
>
> Since there haven't been any replies, yet, to this questions, I
> thought I could post the relevant bit of the web service's WSDL.
> Please find it below. Sorry about the long post. As I said, the
> sayHello service method is working perfectly fine. It's just the one
> that's using the complex type User that's causing me problems. I'd be
> most greatly for any hints into the right direction.
>
> All the best,
>
> Martin
>
>
> <wsdl:definitions targetNamespace="urn:mypackage.com">
> <!--
> WSDL created by Apache Axis version: 1.2.1
> Built on Jun 14, 2005 (09:15:57 EDT)
> -->
> <wsdl:types>
> <schema targetNamespace="urn:mypackage.com">
> <import
> namespace="http://dataObjects.database.mypackage.com"/>
> <import
> namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
>
> <complexType name="ArrayOf_xsd_anyType">
> <complexContent>
> <restriction base="soapenc:Array">
> <attribute
> ref="soapenc:arrayType" wsdl:arrayType="xsd:anyType[]"/>
> </restriction>
> </complexContent>
> </complexType>
> </schema>
> [...]
> <schema
> targetNamespace="http://dataObjects.database.mypackage.com">
> <import namespace="urn:mypackage.com"/>
> <import
> namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
> <complexType abstract="true"
> name="AbstractUser">
> <sequence>
> <element
> name="contactsForUser1" nillable="true"
> type="impl:ArrayOf_xsd_anyType"/>
> <element
> name="contactsForUser2" nillable="true"
> type="impl:ArrayOf_xsd_anyType"/>
> <element name="email"
> nillable="true" type="xsd:string"/>
> <element name="firstName"
> nillable="true" type="xsd:string"/>
> <element name="id"
> nillable="true" type="xsd:int"/>
> <element name="lastName"
> nillable="true" type="xsd:string"/>
> <element name="password"
> nillable="true" type="xsd:string"/>
> <element name="projects"
> nillable="true" type="impl:ArrayOf_xsd_anyType"/>
> <element name="targetteams"
> nillable="true" type="impl:ArrayOf_xsd_anyType"/>
> </sequence>
> </complexType>
> <complexType name="User">
> <complexContent>
> <extension base="tns1:AbstractUser">
> <sequence/>
> </extension>
> </complexContent>
> </complexType>
>
> [...]
>
> <wsdl:message name="registerRequest">
> <wsdl:part name="in0" type="tns1:User"/>
> </wsdl:message>
>
> <wsdl:message name="sayHelloRequest">
> <wsdl:part name="in0" type="soapenc:string"/>
> </wsdl:message>
>
> <wsdl:message name="registerResponse">
> </wsdl:message>
>
> <wsdl:message name="sayHelloResponse">
> <wsdl:part name="sayHelloReturn"
> type="soapenc:string"/>
> </wsdl:message>
>
> <wsdl:portType name="Handler">
>
> <wsdl:operation name="register" parameterOrder="in0">
> <wsdl:input message="impl:registerRequest"
> name="registerRequest"/>
> <wsdl:output message="impl:registerResponse"
> name="registerResponse"/>
> <wsdl:fault message="impl:MyException"
> name="MyException"/>
> </wsdl:operation>
>
> <wsdl:operation name="sayHello" parameterOrder="in0">
> <wsdl:input message="impl:sayHelloRequest"
> name="sayHelloRequest"/>
> <wsdl:output message="impl:sayHelloResponse"
> name="sayHelloResponse"/>
> </wsdl:operation>
> </wsdl:portType>
>
> <wsdl:binding name="HandlerSoapBinding" type="impl:Handler">
> <wsdlsoap:binding style="rpc"
> transport="http://schemas.xmlsoap.org/soap/http"/>
> <wsdl:operation name="register">
> <wsdlsoap:operation soapAction=""/>
> <wsdl:input name="registerRequest">
> <wsdlsoap:body
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> namespace="urn:mypackage.com" use="encoded"/>
> </wsdl:input>
> <wsdl:output name="registerResponse">
> <wsdlsoap:body
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> namespace="urn:mypackage.com" use="encoded"/>
> </wsdl:output>
>
> <wsdl:fault name="MyException">
> <wsdlsoap:fault
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> name="MyException" namespace="urn:mypackage.com" use="encoded"/>
> </wsdl:fault>
> </wsdl:operation>
>
> <wsdl:operation name="sayHello">
> <wsdlsoap:operation soapAction=""/>
> <wsdl:input name="sayHelloRequest">
> <wsdlsoap:body
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> namespace="urn:mypackage.com" use="encoded"/>
> </wsdl:input>
> <wsdl:output name="sayHelloResponse">
> <wsdlsoap:body
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> namespace="urn:mypackage.com" use="encoded"/>
> </wsdl:output>
> </wsdl:operation>
> </wsdl:binding>
>
> <wsdl:service name="IHandlerService">
> <wsdl:port binding="impl:HandlerSoapBinding" name="Handler">
> <wsdlsoap:address
> location="http://localhost/MyProject/services/Handler"/>
> </wsdl:port>
> </wsdl:service>
> </wsdl:definitions>
>
> > Dear all,
>
> > I have deployed a couple of web services and I keep getting an
> exception
> > when calling one of them. I am calling two services. One takes as
> > input a String and returns a String. This one works just fine.
> Another one
> > takes as input a complex type (a Java bean) and has no return value.
> > This is the one that fails with the somewhat cryptic
> > exception give below (both are called using the auto-generated test
> > case). The web service's method
> > is called register() and basically meant to write a User object to a
> > database. Calling "getCause()" returns a null value. The object I
> pass in
> > looks fine. I can out.println() its values.
>
> > Could anyone give me a hint as to what this means? Thanks a lot in
> > advance.
>
> > Cheers,
>
> > Martin
>
> > AxisFault
> > faultCode:
> > {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> > faultSubcode:
> > faultString: java.lang.reflect.InvocationTargetException
> > faultActor:
> > faultNode:
> > faultDetail:
> > {http://xml.apache.org/axis/}hostname:Hermes
>
> > java.lang.reflect.InvocationTargetException
> > at
> >
>
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
> > at
> >
>
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
> > at
> >
>
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
> > at
>
=== message truncated ===
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: Server.userException and InvocationTargetException - what does it mean?
Posted by Martin Wunderlich <ma...@gmx.net>.
Hello again,
Since there haven't been any replies, yet, to this questions, I
thought I could post the relevant bit of the web service's WSDL.
Please find it below. Sorry about the long post. As I said, the
sayHello service method is working perfectly fine. It's just the one
that's using the complex type User that's causing me problems. I'd be
most greatly for any hints into the right direction.
All the best,
Martin
<wsdl:definitions targetNamespace="urn:mypackage.com">
<!--
WSDL created by Apache Axis version: 1.2.1
Built on Jun 14, 2005 (09:15:57 EDT)
-->
<wsdl:types>
<schema targetNamespace="urn:mypackage.com">
<import namespace="http://dataObjects.database.mypackage.com"/>
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<complexType name="ArrayOf_xsd_anyType">
<complexContent>
<restriction base="soapenc:Array">
<attribute ref="soapenc:arrayType" wsdl:arrayType="xsd:anyType[]"/>
</restriction>
</complexContent>
</complexType>
</schema>
[...]
<schema targetNamespace="http://dataObjects.database.mypackage.com">
<import namespace="urn:mypackage.com"/>
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<complexType abstract="true" name="AbstractUser">
<sequence>
<element name="contactsForUser1" nillable="true" type="impl:ArrayOf_xsd_anyType"/>
<element name="contactsForUser2" nillable="true" type="impl:ArrayOf_xsd_anyType"/>
<element name="email" nillable="true" type="xsd:string"/>
<element name="firstName" nillable="true" type="xsd:string"/>
<element name="id" nillable="true" type="xsd:int"/>
<element name="lastName" nillable="true" type="xsd:string"/>
<element name="password" nillable="true" type="xsd:string"/>
<element name="projects" nillable="true" type="impl:ArrayOf_xsd_anyType"/>
<element name="targetteams" nillable="true" type="impl:ArrayOf_xsd_anyType"/>
</sequence>
</complexType>
<complexType name="User">
<complexContent>
<extension base="tns1:AbstractUser">
<sequence/>
</extension>
</complexContent>
</complexType>
[...]
<wsdl:message name="registerRequest">
<wsdl:part name="in0" type="tns1:User"/>
</wsdl:message>
<wsdl:message name="sayHelloRequest">
<wsdl:part name="in0" type="soapenc:string"/>
</wsdl:message>
<wsdl:message name="registerResponse">
</wsdl:message>
<wsdl:message name="sayHelloResponse">
<wsdl:part name="sayHelloReturn" type="soapenc:string"/>
</wsdl:message>
<wsdl:portType name="Handler">
<wsdl:operation name="register" parameterOrder="in0">
<wsdl:input message="impl:registerRequest" name="registerRequest"/>
<wsdl:output message="impl:registerResponse" name="registerResponse"/>
<wsdl:fault message="impl:MyException" name="MyException"/>
</wsdl:operation>
<wsdl:operation name="sayHello" parameterOrder="in0">
<wsdl:input message="impl:sayHelloRequest" name="sayHelloRequest"/>
<wsdl:output message="impl:sayHelloResponse" name="sayHelloResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HandlerSoapBinding" type="impl:Handler">
<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="register">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="registerRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:mypackage.com" use="encoded"/>
</wsdl:input>
<wsdl:output name="registerResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:mypackage.com" use="encoded"/>
</wsdl:output>
<wsdl:fault name="MyException">
<wsdlsoap:fault encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" name="MyException" namespace="urn:mypackage.com" use="encoded"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="sayHello">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sayHelloRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:mypackage.com" use="encoded"/>
</wsdl:input>
<wsdl:output name="sayHelloResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:mypackage.com" use="encoded"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="IHandlerService">
<wsdl:port binding="impl:HandlerSoapBinding" name="Handler">
<wsdlsoap:address location="http://localhost/MyProject/services/Handler"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
> Dear all,
> I have deployed a couple of web services and I keep getting an exception
> when calling one of them. I am calling two services. One takes as
> input a String and returns a String. This one works just fine. Another one
> takes as input a complex type (a Java bean) and has no return value.
> This is the one that fails with the somewhat cryptic
> exception give below (both are called using the auto-generated test
> case). The web service's method
> is called register() and basically meant to write a User object to a
> database. Calling "getCause()" returns a null value. The object I pass in
> looks fine. I can out.println() its values.
> Could anyone give me a hint as to what this means? Thanks a lot in
> advance.
> Cheers,
> Martin
> AxisFault
> faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> faultSubcode:
> faultString: java.lang.reflect.InvocationTargetException
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}hostname:Hermes
> java.lang.reflect.InvocationTargetException
> at
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
> at
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
> at
> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown Source)
> at
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:379)
> at
> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
> at
> org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
> at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
> at
> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
> at
> org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
> at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
> at org.apache.axis.client.Call.invoke(Call.java:2748)
> at org.apache.axis.client.Call.invoke(Call.java:2424)
> at org.apache.axis.client.Call.invoke(Call.java:2347)
> at org.apache.axis.client.Call.invoke(Call.java:1804)
> at
>
> com.mypackage.ServiceHandlerSoapBindingStub.register(ServiceHandlerSoapBindingStub.java:270)
> at
>
> com.mypackage.IServiceHandlerServiceTestCase.test1ServiceHandlerRegister(IServiceServiceTestCase.java:45)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at junit.framework.TestCase.runTest(TestCase.java:154)
> at junit.framework.TestCase.runBare(TestCase.java:127)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at
> junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
--
----------------------------------------------------------
Martin Wunderlich, M.A.
Translation/Localisation EN <-> DE
www.martinwunderlich.com
----------------------------------------------------------
Free / open-source software for translation/localisation:
www.martinwunderlich.com/foss-links.html
----------------------------------------------------------
Random aphorism:
"Aquela reinspiração, sem a qual traduzir é apenas parafrasear noutra língua."
"That new inspiration - without which to translate merely means to paraphrase into another language."
- Fernando Pessoa
----------------------------------------------------------
Server.userException and InvocationTargetException - what does it mean?
Posted by Martin Wunderlich <ma...@gmx.net>.
Dear all,
I have deployed a couple of web services and I keep getting an exception
when calling one of them. I am calling two services. One takes as
input a String and returns a String. This one works just fine. Another one
takes as input a complex type (a Java bean) and has no return value.
This is the one that fails with the somewhat cryptic
exception give below (both are called using the auto-generated test
case). The web service's method
is called register() and basically meant to write a User object to a
database. Calling "getCause()" returns a null value. The object I pass in
looks fine. I can out.println() its values.
Could anyone give me a hint as to what this means? Thanks a lot in
advance.
Cheers,
Martin
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.reflect.InvocationTargetException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:Hermes
java.lang.reflect.InvocationTargetException
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:379)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:2424)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
at
com.mypackage.ServiceHandlerSoapBindingStub.register(ServiceHandlerSoapBindingStub.java:270)
at
com.mypackage.IServiceHandlerServiceTestCase.test1ServiceHandlerRegister(IServiceServiceTestCase.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Re: [Axis2] 1.0RC1 module problems
Posted by Deepal Jayasinghe <de...@opensource.lk>.
hmm , sometimes ago we set the module as the name specified in
module.xml , but we changed that recently (0.95) to have module name as
name of the archive file.So previously module.xml had name="logging"
attribute and that become the name of the module even though actual
archive name LogingModule.mar , now the case is different and module
name always be the LogingModule
robert lazarski wrote:
> Hi all,
>
> I'm trying to port a module from around .94 to RC1 . I had some
> engagement problems, so I decided to try deploying the LoggingModule
> from the user guide - my module largely follows that example. The
> debug logs show:
>
> - Deploying module : LoggingModule
> - org.apache.axis2.i18n.resource::handleGetObject(modulenotavailble)
> - org.apache.axis2.i18n.resource::handleGetObject(modulevalfailed)
> - Module validation failed Trying to engage a module which is not
> available : logging
> - org.apache.axis2.i18n.resource::handleGetObject(modulenotavailble)
> - org.apache.axis2.i18n.resource::handleGetObject(modulevalfailed)
> - Module validation failed Trying to engage a module which is not
> available : logging
>
> Now the steps I followed was:
>
> 1) Move LoggingModule.mar to WEB-INF/modules.
> 2) add <module ref="logging"/> to my services.xml
> 3) Edit axis2.xml to put <phase name="loggingPhase"/> in the inflow,
> outflow, and faults.
> 4) add <module ref="logging"/> to axis2.xml .
>
> That's the way I remember it working. Any ideas?
>
> Robert
> http://www.braziloutsource.com/
>
--
Thanks,
Deepal
................................................................
~Future is Open~
Re: [Axis2] 1.0RC1 module problems
Posted by robert lazarski <ro...@gmail.com>.
Yeah that fixed it - thanks. I filed a jira on this:
http://issues.apache.org/jira/browse/AXIS2-570
Robert
http://www.braziloutsource.com/
On 4/13/06, Ali Sadik Kumlali <as...@yahoo.com> wrote:
>
> Hi Robert,
>
> I faced the same problem and posted messages about it yesterday. When
> you rename LoggingModule.mar to logging.mar it should work. Could you
> please give this a try?
>
> Regards,
>
> Ali Sadik Kumlali
>
> --- robert lazarski <ro...@gmail.com> wrote:
>
> > Hi all,
> >
> > I'm trying to port a module from around .94 to RC1 . I had some
> > engagement
> > problems, so I decided to try deploying the LoggingModule from the
> > user
> > guide - my module largely follows that example. The debug logs show:
> >
> > - Deploying module : LoggingModule
> > - org.apache.axis2.i18n.resource::handleGetObject(modulenotavailble)
> > - org.apache.axis2.i18n.resource::handleGetObject(modulevalfailed)
> > - Module validation failed Trying to engage a module which is not
> > available
> > : logging
> > - org.apache.axis2.i18n.resource::handleGetObject(modulenotavailble)
> > - org.apache.axis2.i18n.resource::handleGetObject(modulevalfailed)
> > - Module validation failed Trying to engage a module which is not
> > available
> > : logging
> >
> > Now the steps I followed was:
> >
> > 1) Move LoggingModule.mar to WEB-INF/modules.
> > 2) add <module ref="logging"/> to my services.xml
> > 3) Edit axis2.xml to put <phase name="loggingPhase"/> in the inflow,
> > outflow, and faults.
> > 4) add <module ref="logging"/> to axis2.xml .
> >
> > That's the way I remember it working. Any ideas?
> >
> > Robert
> > http://www.braziloutsource.com/
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
Re: [Axis2] 1.0RC1 module problems
Posted by Ali Sadik Kumlali <as...@yahoo.com>.
Hi Robert,
I faced the same problem and posted messages about it yesterday. When
you rename LoggingModule.mar to logging.mar it should work. Could you
please give this a try?
Regards,
Ali Sadik Kumlali
--- robert lazarski <ro...@gmail.com> wrote:
> Hi all,
>
> I'm trying to port a module from around .94 to RC1 . I had some
> engagement
> problems, so I decided to try deploying the LoggingModule from the
> user
> guide - my module largely follows that example. The debug logs show:
>
> - Deploying module : LoggingModule
> - org.apache.axis2.i18n.resource::handleGetObject(modulenotavailble)
> - org.apache.axis2.i18n.resource::handleGetObject(modulevalfailed)
> - Module validation failed Trying to engage a module which is not
> available
> : logging
> - org.apache.axis2.i18n.resource::handleGetObject(modulenotavailble)
> - org.apache.axis2.i18n.resource::handleGetObject(modulevalfailed)
> - Module validation failed Trying to engage a module which is not
> available
> : logging
>
> Now the steps I followed was:
>
> 1) Move LoggingModule.mar to WEB-INF/modules.
> 2) add <module ref="logging"/> to my services.xml
> 3) Edit axis2.xml to put <phase name="loggingPhase"/> in the inflow,
> outflow, and faults.
> 4) add <module ref="logging"/> to axis2.xml .
>
> That's the way I remember it working. Any ideas?
>
> Robert
> http://www.braziloutsource.com/
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com