Re: No object was found for class type class java.util.Calendar
I just found a solution, his : There is a, may be, a bug in org.apache.axis.encoding.ConstructorTarget. When axis instanciate a class with a custom constructor (no the default parameterless), it check if class type from webservice are same as constructor parameters, here is the code that do this : if (values.get(i).getClass().getName().toLowerCase().indexOf(classes[c].getName().toLowerCase()) != -1) The problem is the bean class contructor (for me) take a java.util.calendar and the webservice return a java.util.gregorianCalendar, indexOf failed. To correct it without changed axiscode. I change the bean class contructor (generated with wsdl2java) to take gregoriancalendar. unrealone wrote: > > Hallo, > I have a strange problem with getting Calendar/Date (java.util.*) objects > via an Axis/SOAP method. The method's return type is a complex type mapped > as a bean with the beanMapping tag and this complex type has a > Date field (I tried both Date and Calendar - neither worked). > > When calling the method from the client, an exception is thrown upon > deserialization: > org.xml.sax.SAXException: No object was found for > class type class java.util.Calendar > This is even more strange, since I set up another test method that simply > returns a Calendar (or Date - again I tried both) instance. This method > works just fine so I really don't see how this is different from the > previous bean-field case. > > Just to summarize again: > case #1 - complex bean-mapped type with a field of > the type java.util.Date or java.util.Calendar returned by the webservice > method - the above-mentioned exception is thrown upon > deserialization > > case #2 - just java.util.Date or java.util.Calendar > (Axis should handle ser/deser automatically - so no mapping or other black > magic) returned by a webservice method - everything OK > > > PLUS I checked the request/response with the tcpmon utility and > the Date/Calendar values are serialized the same way in both cases: > >xsi:type="xsd:dateTime">2006-08-30T12:33:50.197Z > > I am 99% sure that the complex classes' beanMapping is correct - when I > remove the Date field, the object gets from the server to the client with > NO PROBLEMS. > > I'll appreciate any help you can give me - I feel > kind of silly to even ask this since the issue looks quite elementary, but > it's just not working for me > > > > some sources here: > > > public class CdrRecordSO implements Serializable { > ... >private Calendar date; // THIS IS THE FIELD THAT CAUSES PROBLEMS > >public Calendar getDate() { > return this.date; >} > >public void setDate(Calendar date) { > this.date = date; >} > ... > } > > > -- View this message in context: http://www.nabble.com/No-object-was-found-for-class-type-class-java.util.Calendar-tf2190378.html#a6442007 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis - .NET Interop
According to the WSDL, Axis is doing it wrong. .NET is a lot more tempermental about namespaces. The proper response message should look like this: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://oracle.dao.tooltime.sete.stl.mo.boeing.com"; xmlns:dto="http://dto.dao.tooltime.sete.stl.mo.boeing.com";> Stephen King 2 350 Gerald's Game Stephen King 1 500 The Shining How did you create the service? Anne On 9/21/06, Brian Moffatt <[EMAIL PROTECTED]> wrote: Thanks Anne. I too thought wrapped doc/literal would be my best bet for interoperability. Attached are my WSDL, and some SOAP messages. The file javaSOAPMessages.txt contains the request and response messages captured when calling the Axis service from the Java client (which works beautifully). The file dotNetSOAPMessages.txt contains the request message captured when calling the Axis service from my .NET client. Unfortunately, for whatever reason, the TCP/IP monitor I'm using isn't capturing the SOAP response in this scenario. I'm working on figuring this out. However I know something is coming back because, like I said, I get back an array of two objects (as expected). They just don't have any values on any of their attributes. The one thing that jumps out at me is in the request messages, the Java version uses "soapenv" where the .NET version uses "soap". Aside from that the request messages appear to be identical so one would assume that the response messages coming back would be identical too. Note that this is just some test stuff for a presentation I'm doing for my group, but if we can get something like this working for .NET - Java interop, we want to look into using WS for some "real" stuff within our group. Any further ideas about what might be my problem are greatly appreciated. Brian --- Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > Wrapped doc/literal should work -- although you will > probably do > better using Axis 1.4 rather than Axis 1.3. There > still are some > problems with arrays, but you shouldn't have a > problem with the bean. > Please post some sample WSDLs and SOAP messages. > > Anne > > On 9/20/06, Brian Moffatt <[EMAIL PROTECTED]> > wrote: > > I've seen this exact problem addressed in the > archives > > but never with any clear solution. I was > wondering if > > this was something for which there is a known > solution > > and I'm just not finding it. > > > > Basically, I have an Axis based web service with 5 > > available methods. One returns a simple Java bean > > (made up of three Strings and an int) and one > returns > > an array of said beans. The others return > nothing. I > > am using Axis 1.3 and Apache Tomcat 5.0. I used > the > > document/literal wrapped mode. I got the service > > deployed fine and can call it successfully from > the > > generated Java client proxy code. > > > > My problem is when I try to call it from .NET. I > ran > > the WSDL through the wsdl.exe tool included with > > Visual Studio 2005 and wrote a simple driver > console > > app to call the generated code. It works. . . > sort > > of. The method that returns a bean, returns a > bean > > but all the fields are nulled out or zero. The > method > > that returns an array of beans, returns an array > of > > beans of the appropriate length, but all the > > attributes of the beans in the array are null / > zero. > > I did some testing and can get a method that just > > returns a String or primitive to interoperate > > correctly using Doc/Literal wrapped. > > > > One last thing. I did get the Axis -.NET > > communication to work completely with the complex > > types / arrays of complex types but had to use > > RPC/Encoded when creating my service with Axis to > > achieve success. Ironically, this is the only way > > that makes .NET yell at me for being WS-I > > non-compliant when I run wsdl.exe. > > > > > > Does this sound familiar to anyone? Is it a > common > > problem? Is there a known solution? I've read > that > > Doc/Literal wrapped is THE way to go if you want > Axis > > - .NET interop, but my experience has been that > > RPC/Encoded is the only way that works. I'd > rather > > use whatever is WS-I compliant. Any feedback is > > greatly appreciated. I'll gladly supply a WSDL, > SOAP > > messages, or other data from my test case anyone > > wishes to see. > > > > Thanks, > > > > Brian > > > > > - > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > Request coming in from Java client: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://ww
Missing jar
I got an error when trying to upload a service to the Axis2 web application: Caused by: java.lang.NoClassDefFoundError: org/apache/commons/io/output/DeferredFileOutputStream It was easily fixed by adding commons-io-1.2.jar to the WEB-INF/lib. You may want to include this jar in the nightly build war file. FYI. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 is ignoring my WSDL
On 9/21/06, Martin Gainty <[EMAIL PROTECTED]> wrote: But..If the wsdl you provide (either its content or style) is hosed there is no way for the program to correct it However.. If the program is *somehow* able to intuit from the services operations/methods and parameter(s) what the generated operation and the resulting request and response parameters should be *then* that feature should definitely be supported If I understand you correctly, you're saying that if you have a "bad" .wsdl (whatever that might mean) in your .aar, then Axis should ignore it and generate its own if it can before it pukes. I can't see that being a good thing in my situation. If I have a .wsdl in my .aar that I put there at build time, it means that anyone who has a copy of my .aar has my wsdl and they are going to be coding against it--at least they'd better if they hope to talk to my service and get meaningful results! Now, if you implement this automagical fall-back (which is what you're proposing), then the contract that I have built into my deployed package--the one I'm telling people they *need* to code against--is not going to match what happens in production. So, when a developer codes against a "broken" built WSDL, he's going to be in for a very rude awakening when he finally deploys his client(s)--the contract that I advertised does not reflect reality. At best, it'll just plain bork...but at worst, it may introduce a very subtle, hard-to-track bug. In my experience, it's better to fail in an obvious manner if you cannot guarantee completely safe fallback. -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 is ignoring my WSDL
Good Evening All- I'm finding org.apache.axis2.engine.Service class doesnt exist in my distro's is this a new class? I do however see org.apache.axis2.Service class from core.jar- thanks, M- * This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: "Martin Gainty" <[EMAIL PROTECTED]> To: "D.Kreft" <[EMAIL PROTECTED]>; Sent: Thursday, September 21, 2006 6:21 PM Subject: Re: Axis2 is ignoring my WSDL > You have to start from somewhere ..in our case a definition that is both > complete and syntactically correct > But..If the wsdl you provide (either its content or style) is hosed there is > no way for the program to correct it > However.. > If the program is *somehow* able to intuit from the services > operations/methods and parameter(s) what > the generated operation and the resulting request and response parameters > should be > *then* that feature should definitely be supported > +1 > M- > * > This email message and any files transmitted with it contain confidential > information intended only for the person(s) to whom this email message is > addressed. If you have received this email message in error, please notify > the sender immediately by telephone or email and destroy the original > message without making a copy. Thank you. > > > > - Original Message - > From: "D.Kreft" <[EMAIL PROTECTED]> > To: ; "Martin Gainty" <[EMAIL PROTECTED]> > Sent: Thursday, September 21, 2006 5:52 PM > Subject: Re: Axis2 is ignoring my WSDL > > >> On 9/21/06, Martin Gainty <[EMAIL PROTECTED]> wrote: >> >>> What I found is.. if you use any style other than RPC the wsdl's wont be >>> created under AXIS2 >> >> ...which I maintain is an unnecessary "feature". One should be able to >> specify his own WSDL regardless of what the messageReceiver is set to >> be for that service *and* be able to drop it in the appropriate place. >> Altering the behavior of the WSDL generation based upon the seemingly >> decision that RPC* methods cannot use a pre-generated WSDL does >> nothing more than apply arbitrary rules of engagement and remove power >> from the developer. >> >> No software developer can possibly anticipate all the "crazy" ways >> that other developers will want to use his products or services, so >> it's not a good idea for him to pretend like he knows exactly how >> everyone is going to use them. Software should have sensible, >> intuitive default behavior and allow for developers to deviate from >> the "norm" (whatever that is) by flipping a few bits. One should not >> have to "flip bits" to achieve sensible behavior. >> >> -dan >>
Re: Axis2 is ignoring my WSDL
You have to start from somewhere ..in our case a definition that is both complete and syntactically correct But..If the wsdl you provide (either its content or style) is hosed there is no way for the program to correct it However.. If the program is *somehow* able to intuit from the services operations/methods and parameter(s) what the generated operation and the resulting request and response parameters should be *then* that feature should definitely be supported +1 M- * This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: "D.Kreft" <[EMAIL PROTECTED]> To: ; "Martin Gainty" <[EMAIL PROTECTED]> Sent: Thursday, September 21, 2006 5:52 PM Subject: Re: Axis2 is ignoring my WSDL > On 9/21/06, Martin Gainty <[EMAIL PROTECTED]> wrote: > >> What I found is.. if you use any style other than RPC the wsdl's wont be >> created under AXIS2 > > ...which I maintain is an unnecessary "feature". One should be able to > specify his own WSDL regardless of what the messageReceiver is set to > be for that service *and* be able to drop it in the appropriate place. > Altering the behavior of the WSDL generation based upon the seemingly > decision that RPC* methods cannot use a pre-generated WSDL does > nothing more than apply arbitrary rules of engagement and remove power > from the developer. > > No software developer can possibly anticipate all the "crazy" ways > that other developers will want to use his products or services, so > it's not a good idea for him to pretend like he knows exactly how > everyone is going to use them. Software should have sensible, > intuitive default behavior and allow for developers to deviate from > the "norm" (whatever that is) by flipping a few bits. One should not > have to "flip bits" to achieve sensible behavior. > > -dan >
Re: Axis2 is ignoring my WSDL
On 9/21/06, Martin Gainty <[EMAIL PROTECTED]> wrote: What I found is.. if you use any style other than RPC the wsdl's wont be created under AXIS2 ...which I maintain is an unnecessary "feature". One should be able to specify his own WSDL regardless of what the messageReceiver is set to be for that service *and* be able to drop it in the appropriate place. Altering the behavior of the WSDL generation based upon the seemingly decision that RPC* methods cannot use a pre-generated WSDL does nothing more than apply arbitrary rules of engagement and remove power from the developer. No software developer can possibly anticipate all the "crazy" ways that other developers will want to use his products or services, so it's not a good idea for him to pretend like he knows exactly how everyone is going to use them. Software should have sensible, intuitive default behavior and allow for developers to deviate from the "norm" (whatever that is) by flipping a few bits. One should not have to "flip bits" to achieve sensible behavior. -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis2 is ignoring my WSDL
Makes sense to me also. It should not be ignored by default. -vc -Original Message- From: Dennis Sosnoski [mailto:[EMAIL PROTECTED] Sent: Thursday, September 21, 2006 5:12 PM To: axis-user@ws.apache.org Subject: Re: Axis2 is ignoring my WSDL D.Kreft wrote: > Wait a second... > > It seems *really* counter-intutive to have to supply a configuration > setting to use a file that one intentionally puts in his .aar so that > Axis can use it. It was my understanding after reading the > documentation that a WSDL file in the META-INF directory was supposed > to inhibit the dynamic generation of a WSDL. Would it not be more > reasonable to use this as the default behavior and then provide an > option to *ignore* the supplied WSDL for those special cases when one > would want to do that? This makes sense to me. Anyone have an argument for why a supplied WSDL should be ignored by default? - Dennis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 is ignoring my WSDL
What I found is.. if you use any style other than RPC the wsdl's wont be created under AXIS2 Martin -- * This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: "robert lazarski" <[EMAIL PROTECTED]> To: Sent: Thursday, September 21, 2006 4:10 PM Subject: Re: Axis2 is ignoring my WSDL > You can use your own wsdl provided you use any other message receiver > except for RPC*. If you have a wsdl that you made yourself or got > from somewhere, why not just use databinding via xmlbeans or adb ? > > Robert > > On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: >> On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: >> >> > If you are using RPCMessageReceiver it doesn't make sense to use your >> > own WSDL . This is a FAQ: >> > >> > http://www.wso2.net/kb/104 >> >> Yeah, I saw that a couple of days ago. I think I actually read it more >> than once. >> >> The explanation of why I would *really* like to have a WSDL generated >> at build time is not something I really wanted to get into, so I'll >> try to keep this short and sweet. >> >> The presence of a WSDL at build time makes it much easier for builds >> of other packages (the smallest unit of software development at my >> company) to depend upon my service (at build time)--and it also makes >> it possible to determine if a particular build of my service has the >> contract that another developer is interested in. It is unacceptable >> in our environment to have to query a WSDL from a running service at >> build time--developers might not have network access, they might be >> trying to code to a built-but-not-yet-deployed WSDL, or any one of a >> number of different reasons. >> >> But philosophical arguments aside, I still don't understand why my >> wsdl would not be used if it is where the Axis2 docs say it should be. >> >> -dan >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Axis2 is ignoring my WSDL
D.Kreft wrote: Wait a second... It seems *really* counter-intutive to have to supply a configuration setting to use a file that one intentionally puts in his .aar so that Axis can use it. It was my understanding after reading the documentation that a WSDL file in the META-INF directory was supposed to inhibit the dynamic generation of a WSDL. Would it not be more reasonable to use this as the default behavior and then provide an option to *ignore* the supplied WSDL for those special cases when one would want to do that? This makes sense to me. Anyone have an argument for why a supplied WSDL should be ignored by default? - Dennis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis2 is ignoring my WSDL
Hi, I support Dan's views. We are creating Java Interfaces first and then WSDLs from those interfaces, so that an external non-java client can know about the contract. The implementation of those interfaces will happen in future. If we choose RPCMessageReceivers and deploy services, then Axis2 will start creating its own WSDLs. At this point probably the WSDL which I gave to external system may specify something else then what being generating by AXIS2. An example would be message and part names in WSDL itself, which may be different between my WSDL and AXIS2 generated WSDL. So I guess, definitely, I need an option where I can force Axis to use my WSDL. I hope true will work for RPCMessgereceiver also. -vc -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of D.Kreft Sent: Thursday, September 21, 2006 4:05 PM To: axis-user@ws.apache.org Subject: Re: Axis2 is ignoring my WSDL On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: > If you are using RPCMessageReceiver it doesn't make sense to use your > own WSDL . This is a FAQ: > > http://www.wso2.net/kb/104 Yeah, I saw that a couple of days ago. I think I actually read it more than once. The explanation of why I would *really* like to have a WSDL generated at build time is not something I really wanted to get into, so I'll try to keep this short and sweet. The presence of a WSDL at build time makes it much easier for builds of other packages (the smallest unit of software development at my company) to depend upon my service (at build time)--and it also makes it possible to determine if a particular build of my service has the contract that another developer is interested in. It is unacceptable in our environment to have to query a WSDL from a running service at build time--developers might not have network access, they might be trying to code to a built-but-not-yet-deployed WSDL, or any one of a number of different reasons. But philosophical arguments aside, I still don't understand why my wsdl would not be used if it is where the Axis2 docs say it should be. -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 is ignoring my WSDL
The nightly build has a Java2WSDL.sh, which will get me there, I'm sure...but is there documentation on how to use it (i.e. the arguments it takes)? There's no javadoc in the nightly docs snapshot for org.apache.ws.java2wsdl.Java2WSDL. Or am I relegated to source diving? -dan On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: > On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: > > > You can use your own wsdl provided you use any other message receiver > > except for RPC*. If you have a wsdl that you made yourself or got > > from somewhere, why not just use databinding via xmlbeans or adb ? > > I'm not familiar with either xmlbeans or ADB, but after a cursory > examination it would appear that they do not offer > Java-to- functionality--they seem to work the other > way around. I'm a lot better at writing Java than I am at writing > metadata object descriptors...so I'd like to save myself to tedium of > having to write my own service descriptions at build time. > > -dan > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] context lookup issue
Folks,
Please create a JIRA issue, so that we can track and fix the problem.
thanks,
dims
On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote:
Other way around ... I was suggesting you get a reference to some
class from WEB-INF/classes that your servlet sets up, that you call
from inside the aar . It shouldn't be your servlet - use a singleton
perhaps.
I really don't understand why you could get a bound InitalContext
inside WEB-INF/classes but not inside the aar. I don't think its a 1.0
versus a nightly issue. It might be the other user didn't get the
connection instatiated from inside the aar. What I was suggesting is a
work around ... if the InitialContext works in WEB-INF/classes, store
it there and then get it via one of the classic ServiceLocator pattern
implementations. Sorry I don't have any easier ideas.
Robert
On 9/21/06, Johan Lundberg <[EMAIL PROTECTED]> wrote:
> I'm not sure how I could get a reference to the ServiceClass in
> WEB-INF/classes. Can you be more specific cause I feel a bit isolated
> inside my aar.
>
> also:
> Gábor Prótár got this working the way I intended it to initially. Check
> the thread 'Tomcat + Axis2 + MySQL' fist post from 9/19 2006 2:08 PM
> But he is using the Axis2 release 1.0 and I am using a later nightly
> build from August 31.
> Was he just lucky and am I experiencing the expected axis2 behavior?
>
> /johan
>
>
>
> robert lazarski wrote:
> > Well it might be a classloader issue because an aar uses a different
> > classloader than a servlet. You can of course have an aar which can
> > see classes in a higher classloader - for example you can have an aar
> > whcih references your ServiceClass that is placed in WEB-INF/lib or
> > WEB-INF/classes ... but the aar itself merely contains just the
> > services.xml . I'd try that. Or alternatively you can have you Servlet
> > init a singleton or something and just get your connection from that
> > inside the service.
> >
> > HTH,
> > Robert
> >
> > On 9/21/06, Johan Lundberg <[EMAIL PROTECTED]> wrote:
> >> Hi Robert
> >>
> >> I tried to do this from a special servlet in axis2/WEB-INF/classes and
> >> the lookup works like a charm. Why isn't it accessible from the aar
> >> classes? feature or bug? If it is a feature, how do I get access to the
> >> context from initContext.lookup("java:comp/env"); ?
> >>
> >> My final goal is to use the tomcat DataSource jdbc pooling.
> >>
> >> /johan
> >>
> >> robert lazarski wrote:
> >> > Can you do the same lookup successfully via a non-axis2 class inside
> >> > WEB-INF/classes ?
> >> >
> >> > Robert
> >> >
> >> > On 9/21/06, Johan Lundberg <[EMAIL PROTECTED]> wrote:
> >> >> I am using Axis2 nightly build from 31 August and cannot lookup the
> >> >> java:comp/env context from a created InitialContext created inside a
> >> >> class in the aar-file
> >> >>
> >> >> When I do this:
> >> >> Context initContext = new InitialContext();
> >> >> Context envContext = (Context)initContext.lookup("java:comp/env");
> >> >>
> >> >> I get a NameNotFoundException.
> >> >>
> >> >> By the way, I am using the distributed axis2.war in tomcat 5.5.17
> >> >>
> >> >> Any ideas?
> >> >> johan
> >> >>
> >> >>
> >> >> -
> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >> >>
> >> >>
> >> >
> >> > -
> >> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> > For additional commands, e-mail: [EMAIL PROTECTED]
> >> >
> >> >
> >> >
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 is ignoring my WSDL
java2wsdl is what you are after I believe . Its a bat / sh file under the bin dir. HTH, Robert On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: > You can use your own wsdl provided you use any other message receiver > except for RPC*. If you have a wsdl that you made yourself or got > from somewhere, why not just use databinding via xmlbeans or adb ? I'm not familiar with either xmlbeans or ADB, but after a cursory examination it would appear that they do not offer Java-to- functionality--they seem to work the other way around. I'm a lot better at writing Java than I am at writing metadata object descriptors...so I'd like to save myself to tedium of having to write my own service descriptions at build time. -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 is ignoring my WSDL
On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: You can use your own wsdl provided you use any other message receiver except for RPC*. If you have a wsdl that you made yourself or got from somewhere, why not just use databinding via xmlbeans or adb ? I'm not familiar with either xmlbeans or ADB, but after a cursory examination it would appear that they do not offer Java-to- functionality--they seem to work the other way around. I'm a lot better at writing Java than I am at writing metadata object descriptors...so I'd like to save myself to tedium of having to write my own service descriptions at build time. -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] context lookup issue
Other way around ... I was suggesting you get a reference to some
class from WEB-INF/classes that your servlet sets up, that you call
from inside the aar . It shouldn't be your servlet - use a singleton
perhaps.
I really don't understand why you could get a bound InitalContext
inside WEB-INF/classes but not inside the aar. I don't think its a 1.0
versus a nightly issue. It might be the other user didn't get the
connection instatiated from inside the aar. What I was suggesting is a
work around ... if the InitialContext works in WEB-INF/classes, store
it there and then get it via one of the classic ServiceLocator pattern
implementations. Sorry I don't have any easier ideas.
Robert
On 9/21/06, Johan Lundberg <[EMAIL PROTECTED]> wrote:
I'm not sure how I could get a reference to the ServiceClass in
WEB-INF/classes. Can you be more specific cause I feel a bit isolated
inside my aar.
also:
Gábor Prótár got this working the way I intended it to initially. Check
the thread 'Tomcat + Axis2 + MySQL' fist post from 9/19 2006 2:08 PM
But he is using the Axis2 release 1.0 and I am using a later nightly
build from August 31.
Was he just lucky and am I experiencing the expected axis2 behavior?
/johan
robert lazarski wrote:
> Well it might be a classloader issue because an aar uses a different
> classloader than a servlet. You can of course have an aar which can
> see classes in a higher classloader - for example you can have an aar
> whcih references your ServiceClass that is placed in WEB-INF/lib or
> WEB-INF/classes ... but the aar itself merely contains just the
> services.xml . I'd try that. Or alternatively you can have you Servlet
> init a singleton or something and just get your connection from that
> inside the service.
>
> HTH,
> Robert
>
> On 9/21/06, Johan Lundberg <[EMAIL PROTECTED]> wrote:
>> Hi Robert
>>
>> I tried to do this from a special servlet in axis2/WEB-INF/classes and
>> the lookup works like a charm. Why isn't it accessible from the aar
>> classes? feature or bug? If it is a feature, how do I get access to the
>> context from initContext.lookup("java:comp/env"); ?
>>
>> My final goal is to use the tomcat DataSource jdbc pooling.
>>
>> /johan
>>
>> robert lazarski wrote:
>> > Can you do the same lookup successfully via a non-axis2 class inside
>> > WEB-INF/classes ?
>> >
>> > Robert
>> >
>> > On 9/21/06, Johan Lundberg <[EMAIL PROTECTED]> wrote:
>> >> I am using Axis2 nightly build from 31 August and cannot lookup the
>> >> java:comp/env context from a created InitialContext created inside a
>> >> class in the aar-file
>> >>
>> >> When I do this:
>> >> Context initContext = new InitialContext();
>> >> Context envContext = (Context)initContext.lookup("java:comp/env");
>> >>
>> >> I get a NameNotFoundException.
>> >>
>> >> By the way, I am using the distributed axis2.war in tomcat 5.5.17
>> >>
>> >> Any ideas?
>> >> johan
>> >>
>> >>
>> >> -
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> > -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>> >
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] context lookup issue
I'm not sure how I could get a reference to the ServiceClass in
WEB-INF/classes. Can you be more specific cause I feel a bit isolated
inside my aar.
also:
Gábor Prótár got this working the way I intended it to initially. Check
the thread 'Tomcat + Axis2 + MySQL' fist post from 9/19 2006 2:08 PM
But he is using the Axis2 release 1.0 and I am using a later nightly
build from August 31.
Was he just lucky and am I experiencing the expected axis2 behavior?
/johan
robert lazarski wrote:
Well it might be a classloader issue because an aar uses a different
classloader than a servlet. You can of course have an aar which can
see classes in a higher classloader - for example you can have an aar
whcih references your ServiceClass that is placed in WEB-INF/lib or
WEB-INF/classes ... but the aar itself merely contains just the
services.xml . I'd try that. Or alternatively you can have you Servlet
init a singleton or something and just get your connection from that
inside the service.
HTH,
Robert
On 9/21/06, Johan Lundberg <[EMAIL PROTECTED]> wrote:
Hi Robert
I tried to do this from a special servlet in axis2/WEB-INF/classes and
the lookup works like a charm. Why isn't it accessible from the aar
classes? feature or bug? If it is a feature, how do I get access to the
context from initContext.lookup("java:comp/env"); ?
My final goal is to use the tomcat DataSource jdbc pooling.
/johan
robert lazarski wrote:
> Can you do the same lookup successfully via a non-axis2 class inside
> WEB-INF/classes ?
>
> Robert
>
> On 9/21/06, Johan Lundberg <[EMAIL PROTECTED]> wrote:
>> I am using Axis2 nightly build from 31 August and cannot lookup the
>> java:comp/env context from a created InitialContext created inside a
>> class in the aar-file
>>
>> When I do this:
>> Context initContext = new InitialContext();
>> Context envContext = (Context)initContext.lookup("java:comp/env");
>>
>> I get a NameNotFoundException.
>>
>> By the way, I am using the distributed axis2.war in tomcat 5.5.17
>>
>> Any ideas?
>> johan
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 is ignoring my WSDL
You can use your own wsdl provided you use any other message receiver except for RPC*. If you have a wsdl that you made yourself or got from somewhere, why not just use databinding via xmlbeans or adb ? Robert On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: > If you are using RPCMessageReceiver it doesn't make sense to use your > own WSDL . This is a FAQ: > > http://www.wso2.net/kb/104 Yeah, I saw that a couple of days ago. I think I actually read it more than once. The explanation of why I would *really* like to have a WSDL generated at build time is not something I really wanted to get into, so I'll try to keep this short and sweet. The presence of a WSDL at build time makes it much easier for builds of other packages (the smallest unit of software development at my company) to depend upon my service (at build time)--and it also makes it possible to determine if a particular build of my service has the contract that another developer is interested in. It is unacceptable in our environment to have to query a WSDL from a running service at build time--developers might not have network access, they might be trying to code to a built-but-not-yet-deployed WSDL, or any one of a number of different reasons. But philosophical arguments aside, I still don't understand why my wsdl would not be used if it is where the Axis2 docs say it should be. -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 is ignoring my WSDL
On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: If you are using RPCMessageReceiver it doesn't make sense to use your own WSDL . This is a FAQ: http://www.wso2.net/kb/104 Yeah, I saw that a couple of days ago. I think I actually read it more than once. The explanation of why I would *really* like to have a WSDL generated at build time is not something I really wanted to get into, so I'll try to keep this short and sweet. The presence of a WSDL at build time makes it much easier for builds of other packages (the smallest unit of software development at my company) to depend upon my service (at build time)--and it also makes it possible to determine if a particular build of my service has the contract that another developer is interested in. It is unacceptable in our environment to have to query a WSDL from a running service at build time--developers might not have network access, they might be trying to code to a built-but-not-yet-deployed WSDL, or any one of a number of different reasons. But philosophical arguments aside, I still don't understand why my wsdl would not be used if it is where the Axis2 docs say it should be. -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] context lookup issue
Well it might be a classloader issue because an aar uses a different
classloader than a servlet. You can of course have an aar which can
see classes in a higher classloader - for example you can have an aar
whcih references your ServiceClass that is placed in WEB-INF/lib or
WEB-INF/classes ... but the aar itself merely contains just the
services.xml . I'd try that. Or alternatively you can have you Servlet
init a singleton or something and just get your connection from that
inside the service.
HTH,
Robert
On 9/21/06, Johan Lundberg <[EMAIL PROTECTED]> wrote:
Hi Robert
I tried to do this from a special servlet in axis2/WEB-INF/classes and
the lookup works like a charm. Why isn't it accessible from the aar
classes? feature or bug? If it is a feature, how do I get access to the
context from initContext.lookup("java:comp/env"); ?
My final goal is to use the tomcat DataSource jdbc pooling.
/johan
robert lazarski wrote:
> Can you do the same lookup successfully via a non-axis2 class inside
> WEB-INF/classes ?
>
> Robert
>
> On 9/21/06, Johan Lundberg <[EMAIL PROTECTED]> wrote:
>> I am using Axis2 nightly build from 31 August and cannot lookup the
>> java:comp/env context from a created InitialContext created inside a
>> class in the aar-file
>>
>> When I do this:
>> Context initContext = new InitialContext();
>> Context envContext = (Context)initContext.lookup("java:comp/env");
>>
>> I get a NameNotFoundException.
>>
>> By the way, I am using the distributed axis2.war in tomcat 5.5.17
>>
>> Any ideas?
>> johan
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] context lookup issue
Hi Robert
I tried to do this from a special servlet in axis2/WEB-INF/classes and
the lookup works like a charm. Why isn't it accessible from the aar
classes? feature or bug? If it is a feature, how do I get access to the
context from initContext.lookup("java:comp/env"); ?
My final goal is to use the tomcat DataSource jdbc pooling.
/johan
robert lazarski wrote:
Can you do the same lookup successfully via a non-axis2 class inside
WEB-INF/classes ?
Robert
On 9/21/06, Johan Lundberg <[EMAIL PROTECTED]> wrote:
I am using Axis2 nightly build from 31 August and cannot lookup the
java:comp/env context from a created InitialContext created inside a
class in the aar-file
When I do this:
Context initContext = new InitialContext();
Context envContext = (Context)initContext.lookup("java:comp/env");
I get a NameNotFoundException.
By the way, I am using the distributed axis2.war in tomcat 5.5.17
Any ideas?
johan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Problem in passing XML data as String parameter
Hi,I am using a stub client generated from wsdl using axis wsdl2java. I am trying to execute an operation with a string parameter. When I try to pass some XML data fragment as string for that parameter, it gives me "HTTP Transport error : '400' - 'Bad Request' " error. I looked at the SOAP request being generated. The '<' character in the XML string that I passed was modified into <. Now this happens, I believe, because the stub code is using XMLStreamWriter.writeCharacters() on the XML string which doesn't accept any such character in the string. Now I dont know how I should resolve this problem. Is there anyway in which I can pass an XML data as string parameter. I will appreciate any help. Regards,Satyajit
Re: Axis2 is ignoring my WSDL
If you are using RPCMessageReceiver it doesn't make sense to use your own WSDL . This is a FAQ: http://www.wso2.net/kb/104 The jist of it is that via databinding with xmlbeans, adb, jibx etc you will have your own wsdl. With RPC you are not using your own wsdl and axis2 will generate one for you. HTH, Robert On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: > With a nightly or recent build try: > > true Okay, I tried this and I get no love from Axis2. I've got the WSDL in place: $ jar -tf services/pbqs.aar | grep wsdl META-INF/pbqs.wsdl And the parameter set: true But I'm being told: Unable to generate WSDL for this service Either user has not dropped the wsdl into META-INF or operations use message receivers other than RPC. There is absolutely nothing printed to my catalina.out to indicate what the problem might be. FWIW, all of my messageReceivers are set to be org.apache.axis2.rpc.receivers.RPCMessageReceiver. Any guesses as to what's going on? In case it helps... $ md5sum axis2.war 32f4327ec0dbc733a007327deca40d64 axis2.war -dan > > Or wait for the upcomming release in about a week or so. > > HTH, > Robert > > On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: > > I'm a bit stumped here. I've been scouring documentation, articles, > > commentaries and the like for two days, so now I'm going to pester you > > fine folks. :-) > > > > I am generating a wsdl at build time and inserting into the WEB-INF > > directory in my .aar file like so: > > > > $ jar -tf services/pbqs.aar | grep wsdl > > META-INF/PBQS.wsdl > > > > (On a side-note, isn't there an 'axis2-java2wsdl' Ant target? I > > couldn't find one.) > > > > But when I issue the "?wsdl" command against my service (running under > > Tomcat, in case it matters), the WSDL I get back is most definitely > > *not* the one I had generated. Any ideas on why this might be? This > > worked fine under Axis1.x, but I cannot for the life of me get it to > > work under Axis2. > > > > In case you're inclined to respond with "Just use the > > automagically-generated WSDL", well, I'd rather not at this point. For > > reasons I'd rather not go into, having a WSDL that describes the > > service *as it was built* would be beneficial to me (and the > > developers at my company who may need to deploy an older version of > > the service for some reason). > > > > I'd also much prefer to *not* go from WSDL->Java--starting with Java and > > generating a WSDL is far less tedious. > > > > -dan > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 is ignoring my WSDL
On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: With a nightly or recent build try: true Okay, I tried this and I get no love from Axis2. I've got the WSDL in place: $ jar -tf services/pbqs.aar | grep wsdl META-INF/pbqs.wsdl And the parameter set: true But I'm being told: Unable to generate WSDL for this service Either user has not dropped the wsdl into META-INF or operations use message receivers other than RPC. There is absolutely nothing printed to my catalina.out to indicate what the problem might be. FWIW, all of my messageReceivers are set to be org.apache.axis2.rpc.receivers.RPCMessageReceiver. Any guesses as to what's going on? In case it helps... $ md5sum axis2.war 32f4327ec0dbc733a007327deca40d64 axis2.war -dan Or wait for the upcomming release in about a week or so. HTH, Robert On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: > I'm a bit stumped here. I've been scouring documentation, articles, > commentaries and the like for two days, so now I'm going to pester you > fine folks. :-) > > I am generating a wsdl at build time and inserting into the WEB-INF > directory in my .aar file like so: > > $ jar -tf services/pbqs.aar | grep wsdl > META-INF/PBQS.wsdl > > (On a side-note, isn't there an 'axis2-java2wsdl' Ant target? I > couldn't find one.) > > But when I issue the "?wsdl" command against my service (running under > Tomcat, in case it matters), the WSDL I get back is most definitely > *not* the one I had generated. Any ideas on why this might be? This > worked fine under Axis1.x, but I cannot for the life of me get it to > work under Axis2. > > In case you're inclined to respond with "Just use the > automagically-generated WSDL", well, I'd rather not at this point. For > reasons I'd rather not go into, having a WSDL that describes the > service *as it was built* would be beneficial to me (and the > developers at my company who may need to deploy an older version of > the service for some reason). > > I'd also much prefer to *not* go from WSDL->Java--starting with Java and > generating a WSDL is far less tedious. > > -dan > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: CodeGeneration error while using commandline batch file WSDL2Java
Sharad,
You are using RPC/encoded style, which is not supported by Axis 2.0 (not WS-I
compliant). Given your schema, it doesn't really make any sense, either.
Doc/literal would be more appropriate.
-Original Message-
From: Sharad Baronia [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 21, 2006 10:53 AM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: RE: CodeGeneration error while using commandline batch file
WSDL2Java
Hi,
I have attached new wsdl file, which is validated with XMLSPY. Still
WSDL2Java gives error. Any thoughs!!
C:\apache\axis2v1night\bin>wsdl2Java -uri
D:\sbaronia\workspace\test\corporateac
tion.wsdl -o c:\test1 -l java -d adb -a -s -t -ss -sd -g -u -ssi
Using AXIS2_HOME: C:\apache\axis2v1night
Using JAVA_HOME:C:\j2sdk1.4.2_12
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeAndSymbolResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByExDateResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsBySymbolResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsBySymbolAndExDateResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeAndSymbolAndExDate
Resp
onse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeAndExDateResponse'
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException
: org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeExcept
ion: Element QName is null for CorporateActionExceptionFault!
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:224)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.Runt
imeException: Element QName is null for CorporateActionExceptionFault!
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:769)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:206)
... 2 more
Caused by: java.lang.RuntimeException: Element QName is null for
CorporateAction
ExceptionFault!
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.getFaultParamElements(AxisServiceBasedMultiLanguageEmitter.java:1763)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.getFaultElement(AxisServiceBasedMultiLanguageEmitter.java:1713)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:1430)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.createDOMDocumentForSkeletonInterface(AxisServiceBasedMultiLanguageEmi
tter
.java:1352)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.writeSkeletonInterface(AxisServiceBasedMultiLanguageEmitter.java:1297)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:733)
... 3 more
Thanks,
/Sharad
-Original Message-
From: Spies, Brennan [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 21, 2006 8:54 AM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: RE: CodeGeneration error while using commandline batch file
WSDL2Java
Darn, this "delegation" thing never works for me... ;)
Will do.
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 20, 2006 6:25 PM
To: axis-user@ws.apache.org
Subject: Re: CodeGeneration error while using commandline batch file
WSDL2Java
Brennan,
Please file a JIRA bug with *your* wsdl :)
-- dims
On 9/20/06, Spies, Brennan <[EMAIL PR
Re: Axis documentation
Sending file as attachment as well.
-- dims
On 9/21/06, Erik Norgaard <[EMAIL PROTECTED]> wrote:
Anne Thomas Manes wrote:
> The value of the SOAPAction HTTP header is a URI.
> It may be (and often is) different from the endpoint URL (i.e.,
> targetEndpointAddress).
>
> The value of the SOAPAction URI is specified in the
> definitions/binding/operation element in the WSDL in this line:
>
>
>
> The SOAPAction URI does not need to resolve to a physical location. It
> is simply a name used to indicate what action the service should
> perform.
>
> The value of the endpoint URL is specified in the
> definitions/service/port element in the WSDL in this line:
>
> location="http://company.com:8080/axis2/services/service-name"/>
>
> The endpoint URL must resolve to a physical location.
Thanks, I haven't had my brain wrapped inside out yet, and programming
Java in anything but Java just seems quite unnatural to me.
I did try to generate the java stub from a wsdl file, but this just
generated a huge bunch of files without any hint as to what to do with
them, none of the file's name corresponds to the SOAP Action or the
"portName" (the later still confuses me because I think of a port as a
tcp port which is also in play).
I'm trying to find documentation that
a) makes sense to me
b) is verbose enough to allow me to do stuff
The example in the user-guide does not make it clear to me how to
construct a soap request message, set the soap action, send the request
to the web service and receive the result. The API documentation does
not it anything clearer.
I've spent two weeks searching for documentation and trying to figure
out what this is all about, and yet I find myself unable to write a
single line of code that does stuff.
I would expect to do something like
SOAPMessage requestSoap = new SOAPMessage();
SOAPMessage responseSoap = new SOAPMessage();
requestSoap.readXMLFile("requestfile");
HttpClient socket = new HttpClient(URL
"http://localhost:8080/ws/service";);
socket.connect();
socket.setHttpMethod("POST");
socket.addHttpHeader("SOAPAction","DoThis");
socket.addHttpBody(soapRequest);
socket.sendRequest();
socket.getResponse(responseSoap);
responseSoap.writeXMLFile("responsefile");
This pretty much corresponds to the flow of a RPC call, but I find it
immensely difficult to reduce the problem to anything like that from the
documentation at hand.
Is there some source of documentation that is actually consistent,
sufficient and selfcontained? - or do I need brain surgery to use Axis?
Thanks, Erik
--
Ph: +34.666334818 web: http://www.locolomo.org
X.509 Certificate: http://www.locolomo.org/crt/8D03551FFCE04F0C.crt
Key ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
import org.apache.axis2.client.ServiceClient;
import org.apache.axis2.client.Options;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.transport.http.HTTPConstants;
import org.apache.axiom.om.impl.builder.StAXOMBuilder;
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.OMText;
import org.apache.axiom.om.xpath.AXIOMXPath;
import javax.xml.stream.XMLStreamReader;
import javax.xml.stream.XMLInputFactory;
import java.io.StringReader;
import java.util.List;
import java.util.Iterator;
public class GoogleSearch {
public static void main(String[] args) throws Exception {
// Replace the with your google search API key
String myKey = "";
// Create a Service Client
ServiceClient client = new ServiceClient();
// Set the options
Options options = new Options();
options.setTo(new EndpointReference("http://api.google.com/search/beta2";));
options.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
client.setOptions(options);
// Construct the request to be sent.
String xml = "http://schemas.xmlsoap.org/soap/envelope/\"; " +
" SOAP-ENV:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\"; " +
" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"; " +
" xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\";>" +
" " + myKey + "" +
" axis2" +
" 0" +
" 10" +
" false" +
" \"\"" +
" false" +
" " +
" latin1" +
" latin1" +
"";
XMLStreamReader reader = XMLInputFactory.newInstance().createXMLStreamReader(new StringReader(xml));
OMElement request = new StAXOMBuilder(reader).getDocume
Re: Axis documentation
How does this sample look? works with latest nightly.
import org.apache.axis2.client.ServiceClient;
import org.apache.axis2.client.Options;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.transport.http.HTTPConstants;
import org.apache.axiom.om.impl.builder.StAXOMBuilder;
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.OMText;
import org.apache.axiom.om.xpath.AXIOMXPath;
import javax.xml.stream.XMLStreamReader;
import javax.xml.stream.XMLInputFactory;
import java.io.StringReader;
import java.util.List;
import java.util.Iterator;
public class GoogleSearch {
public static void main(String[] args) throws Exception {
// Replace the with your google search API key
String myKey = "";
// Create a Service Client
ServiceClient client = new ServiceClient();
// Set the options
Options options = new Options();
options.setTo(new
EndpointReference("http://api.google.com/search/beta2";));
options.setProperty(HTTPConstants.CHUNKED, Boolean.FALSE);
client.setOptions(options);
// Construct the request to be sent.
String xml = "http://schemas.xmlsoap.org/soap/envelope/\"; " +
"
SOAP-ENV:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\"; "
+
"
xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"; " +
"
xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\";>" +
" " + myKey + "" +
" axis2" +
" 0" +
" 10" +
" false" +
" \"\"" +
" false" +
" " +
" latin1" +
" latin1" +
"";
XMLStreamReader reader =
XMLInputFactory.newInstance().createXMLStreamReader(new
StringReader(xml));
OMElement request = new StAXOMBuilder(reader).getDocumentElement();
// Send the Request
OMElement response = client.sendReceive(request);
// Process the response.
AXIOMXPath xpathExpression = new AXIOMXPath("//item/URL/text()");
List nodeList = xpathExpression.selectNodes(response);
for(Iterator iterator = nodeList.iterator();iterator.hasNext();){
OMText text = (OMText)iterator.next();
System.out.println(text.getText());
}
}
}
On 9/21/06, Erik Norgaard <[EMAIL PROTECTED]> wrote:
Anne Thomas Manes wrote:
> The value of the SOAPAction HTTP header is a URI.
> It may be (and often is) different from the endpoint URL (i.e.,
> targetEndpointAddress).
>
> The value of the SOAPAction URI is specified in the
> definitions/binding/operation element in the WSDL in this line:
>
>
>
> The SOAPAction URI does not need to resolve to a physical location. It
> is simply a name used to indicate what action the service should
> perform.
>
> The value of the endpoint URL is specified in the
> definitions/service/port element in the WSDL in this line:
>
> location="http://company.com:8080/axis2/services/service-name"/>
>
> The endpoint URL must resolve to a physical location.
Thanks, I haven't had my brain wrapped inside out yet, and programming
Java in anything but Java just seems quite unnatural to me.
I did try to generate the java stub from a wsdl file, but this just
generated a huge bunch of files without any hint as to what to do with
them, none of the file's name corresponds to the SOAP Action or the
"portName" (the later still confuses me because I think of a port as a
tcp port which is also in play).
I'm trying to find documentation that
a) makes sense to me
b) is verbose enough to allow me to do stuff
The example in the user-guide does not make it clear to me how to
construct a soap request message, set the soap action, send the request
to the web service and receive the result. The API documentation does
not it anything clearer.
I've spent two weeks searching for documentation and trying to figure
out what this is all about, and yet I find myself unable to write a
single line of code that does stuff.
I would expect to do something like
SOAPMessage requestSoap = new SOAPMessage();
SOAPMessage responseSoap = new SOAPMessage();
requestSoap.readXMLFile("requestfile");
HttpClient socket = new HttpClient(URL
"http://localhost:8080/ws/service";);
socket.connect();
socket.setHttpMethod("POST");
socket.addHttpHeader("SOAPAction","DoThis");
socket.addHttpBody(soapRequest);
socket.sendRequest();
socket.getResponse(responseSoap);
responseSoap.writeXMLFile("responsefile");
This pretty much corresponds to the flow of a RPC call, but I find it
immensely difficult to reduce the problem to anything like that from the
documentation at hand.
Is there some source of documentation that is actually consistent,
sufficient and selfcontained? - or do I need brain surgery to use Axis?
Thanks, Erik
--
Ph: +34.666334818 web: http://www.locolomo.org
X.509 Ce
Re: Axis2 is ignoring my WSDL
On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: With a nightly or recent build try: Is the omission of log4j in the nightly build intentional? $ jar -tf axis2.war.release | grep log4 WEB-INF/lib/log4j-1.2.13.jar WEB-INF/lib/log4j-LICENSE.txt WEB-INF/classes/log4j.properties $ jar -tf axis2.war.nightly | grep log4 WEB-INF/lib/log4j-LICENSE.txt WEB-INF/classes/log4j.properties -dan true Or wait for the upcomming release in about a week or so. HTH, Robert On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: > I'm a bit stumped here. I've been scouring documentation, articles, > commentaries and the like for two days, so now I'm going to pester you > fine folks. :-) > > I am generating a wsdl at build time and inserting into the WEB-INF > directory in my .aar file like so: > > $ jar -tf services/pbqs.aar | grep wsdl > META-INF/PBQS.wsdl > > (On a side-note, isn't there an 'axis2-java2wsdl' Ant target? I > couldn't find one.) > > But when I issue the "?wsdl" command against my service (running under > Tomcat, in case it matters), the WSDL I get back is most definitely > *not* the one I had generated. Any ideas on why this might be? This > worked fine under Axis1.x, but I cannot for the life of me get it to > work under Axis2. > > In case you're inclined to respond with "Just use the > automagically-generated WSDL", well, I'd rather not at this point. For > reasons I'd rather not go into, having a WSDL that describes the > service *as it was built* would be beneficial to me (and the > developers at my company who may need to deploy an older version of > the service for some reason). > > I'd also much prefer to *not* go from WSDL->Java--starting with Java and > generating a WSDL is far less tedious. > > -dan > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 is ignoring my WSDL
Wait a second... It seems *really* counter-intutive to have to supply a configuration setting to use a file that one intentionally puts in his .aar so that Axis can use it. It was my understanding after reading the documentation that a WSDL file in the META-INF directory was supposed to inhibit the dynamic generation of a WSDL. Would it not be more reasonable to use this as the default behavior and then provide an option to *ignore* the supplied WSDL for those special cases when one would want to do that? -dan On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: services.xml Robert On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: > On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: > > > With a nightly or recent build try: > > > > true > > Is this to go into the axis2.xml or the services.xml? I'm guessing the > latter, but hoping to save myself some time (and more beating my head > against the wall). > > Thanks. > > -dan > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: CodeGeneration error while using commandline batch file WSDL2Java
Hi,
Now it works. Why message-part-type works for input/output, but doesn't
work for fault? This is problem in the code--->you have to change to support
message-part-type for fault?
--
Problem version:
--
--
Working version:
--
Thanks,
/Sharad
-Original Message-
From: Sharad Baronia [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 21, 2006 10:53 AM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: RE: CodeGeneration error while using commandline batch file
WSDL2Java
Hi,
I have attached new wsdl file, which is validated with XMLSPY. Still
WSDL2Java gives error. Any thoughs!!
C:\apache\axis2v1night\bin>wsdl2Java -uri
D:\sbaronia\workspace\test\corporateac
tion.wsdl -o c:\test1 -l java -d adb -a -s -t -ss -sd -g -u -ssi
Using AXIS2_HOME: C:\apache\axis2v1night
Using JAVA_HOME:C:\j2sdk1.4.2_12
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeAndSymbolResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByExDateResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsBySymbolResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsBySymbolAndExDateResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeAndSymbolAndExDate
Resp
onse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeAndExDateResponse'
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException
: org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeExcept
ion: Element QName is null for CorporateActionExceptionFault!
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:224)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.Runt
imeException: Element QName is null for CorporateActionExceptionFault!
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:769)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:206)
... 2 more
Caused by: java.lang.RuntimeException: Element QName is null for
CorporateAction
ExceptionFault!
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.getFaultParamElements(AxisServiceBasedMultiLanguageEmitter.java:1763)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.getFaultElement(AxisServiceBasedMultiLanguageEmitter.java:1713)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:1430)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.createDOMDocumentForSkeletonInterface(AxisServiceBasedMultiLanguageEmi
tter
.java:1352)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.writeSkeletonInterface(AxisServiceBasedMultiLanguageEmitter.java:1297)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.emitSkeleto
SAXParseException in axis1.4
In switching to axis1.4 from axis1.1 I get the following exception when trying to process the response: org.xml.sax.SAXParseException: XML document structures must start and end within the same entity (stack trace shown below) Let me first say that I can make this problem go away by calling responseMsg.getSOAPPartAsString() just before calling responseMsg.writeTo(res.getOutputStream()) . The problem appears to occurr in trying to render the SOAPEnvelope. Apparently, when getSOAPPartAsString() is called first, the SOAPPart instance's currentForm data member get's changed to FORM_STRING, which avoids the execution path that leads to the SAXParseException. Anyone know anything about this problem? Note that my code does not build the response body (I believe the axis engine is doing that) so the error, which suggests that there could be garbage at the beginning of the envelope bytes, is not something I seem to be able to control. Any insight would be most appreciated. The stack trace follows. Thanks. Caused by: org.xml.sax.SAXParseException: XML document structures must start and end within the same entity. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Lorg.apache.xerces.xni.parser.XMLParseException;)Lorg.xml.sax.SAXParseException;(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Ljava.lang.String;Ljava.lang.String;Lorg.apache.xerces.xni.parser.XMLParseException;)V(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Lorg.apache.xerces.xni.XMLLocator;Ljava.lang.String;Ljava.lang.String;[Ljava.lang.Object;S)V(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Ljava.lang.String;Ljava.lang.String;[Ljava.lang.Object;S)V(Unknown Source) at org.apache.xerces.impl.XMLScanner.reportFatalError(Ljava.lang.String;[Ljava.lang.Object;)V(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.endEntity(Ljava.lang.String;)V(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl.endEntity(Ljava.lang.String;)V(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.endEntity()V(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.load(IZ)Z(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.scanContent(Lorg.apache.xerces.xni.XMLString;)I(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanContent()I(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Z)Z(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Z)Z(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Z)Z(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Lorg.apache.xerces.xni.parser.XMLInputSource;)V(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Lorg.apache.xerces.xni.parser.XMLInputSource;)V(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Lorg.xml.sax.InputSource;)V(Unknown Source) at javax.xml.parsers.SAXParser.parse(Lorg.xml.sax.InputSource;Lorg.xml.sax.helpers.DefaultHandler;)V(Unknown Source) 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:435) at org.apache.axis.handlers.SimpleSessionHandler.doClient(SimpleSessionHandler.java:173) at org.apache.axis.handlers.SimpleSessionHandler.invoke(SimpleSessionHandler.java:157) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) -- rp johns software factotum - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RES: Installing Axis2 in Tomcat
Robert, I did what you told but it not work. But, I realized the problem is in my own enviroment because I downloaded two new fresh tomcat installation (the same version e a newer one) and tried to run axis2 under this exactly the the way it came from apache and both work at least the index page. The intance I tried first have some confguration wicht can be causing the unexpected behavior. If I found something I let you know. Thanks a lot Silvio -Mensagem original- De: robert lazarski [mailto:[EMAIL PROTECTED] Enviada em: terça-feira, 19 de setembro de 2006 18:01 Para: axis-user@ws.apache.org Assunto: Re: Installing Axis2 in Tomcat I recommend the following: 1) Remove the axis2.war . 2) Download both the war and the std-bin-SNAPSHOT from the nightly link. 3) Unpack the bin package. 4) Compile your source against the new bin package. 5) Put your war un-expanded into tomcat, let tomcat unpack it. 6) Put your new aar in services. Let us know if that helps. Robert On 9/19/06, Silvio dos Passos Neto <[EMAIL PROTECTED]> wrote: > > Hi Thilina, > > I tried download from this link but it still not working. I belive its > the same file I get in this morning thru axis2 web site... > > I really should extract it or just copy to webapps folder (I tried > both anyway)? And I need to make some library visible putting > something in the lib folder? > > Thanks in advance... > > iColabora do Brasil > Silvio dos Passos Neto > [11] 3255-7328 > [11] 8308-3835 > [EMAIL PROTECTED] > > > > De: Thilina Gunarathne [mailto:[EMAIL PROTECTED] Enviada em: > terça-feira, 19 de setembro de 2006 17:34 > Para: axis-user@ws.apache.org > Assunto: Re: Installing Axis2 in Tomcat > > > Try this... > http://people.apache.org/dist/axis2/nightly/axis2.war > > ~Thilina > > > On 9/19/06, Silvio dos Passos Neto <[EMAIL PROTECTED]> wrote: > > > Hi everyone, > > I downloaded the last version of axis2 war... I followed de > instructions of installation guide, droping this in the webapps folder > (renaming the .zip to .war). But it doen't work: I get an > NullPointerException in the home page (http://localhost/axis2, yes, I > do use 80 port): > > java.lang.NullPointerException > at org.apache.jsp.httpbase$jsp.jspInit(httpbase$jsp.java:24) > at > org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:90) > at > org.apache.jasper.servlet.JspServlet$JspServletWrapper.load > (JspServlet.java:142) > at > org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary > (JspSe > rvlet.java:178) > at > org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServ > let.ja > va:188) > at org.apache.jasper.servlet.JspServlet.serviceJspFile > (JspServlet.java:381) > at > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473) > at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at org.apache.catalina.core.ApplicationDispatcher.invoke > (ApplicationDispatcher.java:683) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDi > spatch > er.java:574) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDisp > atcher > .java:497) > > at > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary. > java:8 > 19) > at org.apache.jsp.index$jsp._jspService(index$jsp.java:91) > at > org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) > > at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServ > let.ja > va:201) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java > :381) > at > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473) > at > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appli > cation > FilterChain.java > :247) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFi > lterCh > ain.java:193) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVa > lve.ja > va:243) > at org.apache.catalina.core.StandardPipeline.invokeNext > (StandardPipeline.java:566) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at org.apache.catalina.core.StandardContextValve.invoke > (StandardContextValve.java:190) > at > org.apache.cata
RE: CodeGeneration error while using commandline batch file WSDL2Java
Hi,
I have attached new wsdl file, which is validated with XMLSPY. Still
WSDL2Java gives error. Any thoughs!!
C:\apache\axis2v1night\bin>wsdl2Java -uri
D:\sbaronia\workspace\test\corporateac
tion.wsdl -o c:\test1 -l java -d adb -a -s -t -ss -sd -g -u -ssi
Using AXIS2_HOME: C:\apache\axis2v1night
Using JAVA_HOME:C:\j2sdk1.4.2_12
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeAndSymbolResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByExDateResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsBySymbolResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsBySymbolAndExDateResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeAndSymbolAndExDate
Resp
onse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeResponse'
Sep 21, 2006 10:51:15 AM org.apache.axis2.schema.SchemaCompiler writeElement
WARNING: Could not find any schema type associated with the Element
'{http://www
.nexa.com/corporateaction/}GetCorporateActionsByActionTypeAndExDateResponse'
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException
: org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.RuntimeExcept
ion: Element QName is null for CorporateActionExceptionFault!
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:224)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
Caused by: org.apache.axis2.wsdl.codegen.CodeGenerationException:
java.lang.Runt
imeException: Element QName is null for CorporateActionExceptionFault!
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:769)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:206)
... 2 more
Caused by: java.lang.RuntimeException: Element QName is null for
CorporateAction
ExceptionFault!
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.getFaultParamElements(AxisServiceBasedMultiLanguageEmitter.java:1763)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.getFaultElement(AxisServiceBasedMultiLanguageEmitter.java:1713)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:1430)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.createDOMDocumentForSkeletonInterface(AxisServiceBasedMultiLanguageEmi
tter
.java:1352)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.writeSkeletonInterface(AxisServiceBasedMultiLanguageEmitter.java:1297)
at
org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm
itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:733)
... 3 more
Thanks,
/Sharad
-Original Message-
From: Spies, Brennan [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 21, 2006 8:54 AM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: RE: CodeGeneration error while using commandline batch file
WSDL2Java
Darn, this "delegation" thing never works for me... ;)
Will do.
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 20, 2006 6:25 PM
To: axis-user@ws.apache.org
Subject: Re: CodeGeneration error while using commandline batch file
WSDL2Java
Brennan,
Please file a JIRA bug with *your* wsdl :)
-- dims
On 9/20/06, Spies, Brennan <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Sharad,
>
>
>
> This is definitely a bug (I can reproduce using similar WSDL on the latest
> nightly). It throws a RuntimeException complaining that "Element QName is
> null for [/message/name/text()]!"
>
>
>
> You should file a JIRA issue on this:
> https://issues.apache.org/jira/browse/AXIS2.
>
>
>
>
>
> -Original Message-
> From: Sharad Baronia [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 20, 2
Re: Axis2 is ignoring my WSDL
services.xml Robert On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: > With a nightly or recent build try: > > true Is this to go into the axis2.xml or the services.xml? I'm guessing the latter, but hoping to save myself some time (and more beating my head against the wall). Thanks. -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 is ignoring my WSDL
On 9/21/06, robert lazarski <[EMAIL PROTECTED]> wrote: With a nightly or recent build try: true Is this to go into the axis2.xml or the services.xml? I'm guessing the latter, but hoping to save myself some time (and more beating my head against the wall). Thanks. -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: CodeGeneration error while using commandline batch file WSDL2Java
My mistake... Sharad, your WSDL is probably missing a nested in your ...hence Axis is complaining about it. Look at the example here: http://www.gridlab.org/WorkPackages/wp-5/guide/faults.html -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 6:25 PM To: axis-user@ws.apache.org Subject: Re: CodeGeneration error while using commandline batch file WSDL2Java Brennan, Please file a JIRA bug with *your* wsdl :) -- dims On 9/20/06, Spies, Brennan <[EMAIL PROTECTED]> wrote: > > > > > Sharad, > > > > This is definitely a bug (I can reproduce using similar WSDL on the latest > nightly). It throws a RuntimeException complaining that "Element QName is > null for [/message/name/text()]!" > > > > You should file a JIRA issue on this: > https://issues.apache.org/jira/browse/AXIS2. > > > > > > -Original Message- > From: Sharad Baronia [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 20, 2006 5:32 PM > To: axis-user@ws.apache.org > Subject: RE: CodeGeneration error while using commandline batch file > WSDL2Java > > > > > > > Hi, > > > > After removed the Fault Exception, and then it generates the classes. But it > doesn't generate classes for each operation, and classes for input, & output > of an operation. > > I thing I am missing something. ! It misses the objective of code > generation. > > > > Can anyone help me > > > > /Sharad > > > > > > > From: Sharad Baronia [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 20, 2006 4:40 PM > To: axis-user@ws.apache.org > Subject: RE: CodeGeneration error while using commandline batch file > WSDL2Java > > > > Hi All, > > > > Sorry for causing confusion in my previous. This is my first to email to > this user group. > > > > I am using Axis2 nightly build (Sept-20) > > > > When using WSDL2Java, it generates runtime error : java.lang.RuntimeExcept > > ion: Element QName is null for CorporateActionExceptionFault [ name="CorporateActionExceptionFault"> > > type="tns:CorporateActionException"/> > > ]. > > > > I have attached wsdl file in my previous email. > > > > /Sharad > > > > > > > From: Sharad Baronia [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 20, 2006 4:13 PM > To: axis-user@ws.apache.org > Subject: CodeGeneration error while using commandline batch file WSDL2Java > > > > Hi, > > > > I was using Axis2 1.0 WS2DL2Java was working fine, but I was getting some > runtime error. So I decided to download nightly build which is giving me > runtime error. > > I have attached the wsdl file for reference. > > Help need!! > > > > > > Thanks, > > > > /Sharad > > > > > > C:\apache\axis2v1night\bin>wsdl2Java -uri c:\ > test1\corporateaction.wsdl -o c:\test1 -l java -a -s -t -ss -sd -g -u -ssi > > Using AXIS2_HOME: C:\apache\axis2v1night > > Using JAVA_HOME:C:\j2sdk1.4.2_12 > > Exception in thread "main" > org.apache.axis2.wsdl.codegen.CodeGenerationException > > : org.apache.axis2.wsdl.codegen.CodeGenerationException: > java.lang.RuntimeExcept > > ion: Element QName is null for CorporateActionExceptionFault! > > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener > > ationEngine.java:224) > > at > org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) > > at > org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) > > Caused by: > org.apache.axis2.wsdl.codegen.CodeGenerationException: > java.lang.Runt > > imeException: Element QName is null for CorporateActionExceptionFault! > > at > org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm > > itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:769) > > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener > > ationEngine.java:206) > > ... 2 more > > Caused by: java.lang.RuntimeException: Element QName is null for > CorporateAction > > ExceptionFault! > > at > org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm > > itter.getFaultParamElements(AxisServiceBasedMultiLanguageEmitter.java:1763) > > at > org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm > > itter.getFaultElement(AxisServiceBasedMultiLanguageEmitter.java:1713) > > at > org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm > > itter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:1430) > > at > org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm > > itter.createDOMDocumentForSkeletonInterface(AxisServiceBasedMultiLanguageEmit ter > > .java:1352) > > at > org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm > > itter.writeSkeletonInterface(AxisServiceBasedMultiLanguageEmitter.java:1297) > > at > org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm > > itter.emitSkeleton(AxisServiceBasedMultiLanguageE
Re: Axis2 is ignoring my WSDL
With a nightly or recent build try: true Or wait for the upcomming release in about a week or so. HTH, Robert On 9/21/06, D. Kreft <[EMAIL PROTECTED]> wrote: I'm a bit stumped here. I've been scouring documentation, articles, commentaries and the like for two days, so now I'm going to pester you fine folks. :-) I am generating a wsdl at build time and inserting into the WEB-INF directory in my .aar file like so: $ jar -tf services/pbqs.aar | grep wsdl META-INF/PBQS.wsdl (On a side-note, isn't there an 'axis2-java2wsdl' Ant target? I couldn't find one.) But when I issue the "?wsdl" command against my service (running under Tomcat, in case it matters), the WSDL I get back is most definitely *not* the one I had generated. Any ideas on why this might be? This worked fine under Axis1.x, but I cannot for the life of me get it to work under Axis2. In case you're inclined to respond with "Just use the automagically-generated WSDL", well, I'd rather not at this point. For reasons I'd rather not go into, having a WSDL that describes the service *as it was built* would be beneficial to me (and the developers at my company who may need to deploy an older version of the service for some reason). I'd also much prefer to *not* go from WSDL->Java--starting with Java and generating a WSDL is far less tedious. -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 is ignoring my WSDL
I'm a bit stumped here. I've been scouring documentation, articles, commentaries and the like for two days, so now I'm going to pester you fine folks. :-) I am generating a wsdl at build time and inserting into the WEB-INF directory in my .aar file like so: $ jar -tf services/pbqs.aar | grep wsdl META-INF/PBQS.wsdl (On a side-note, isn't there an 'axis2-java2wsdl' Ant target? I couldn't find one.) But when I issue the "?wsdl" command against my service (running under Tomcat, in case it matters), the WSDL I get back is most definitely *not* the one I had generated. Any ideas on why this might be? This worked fine under Axis1.x, but I cannot for the life of me get it to work under Axis2. In case you're inclined to respond with "Just use the automagically-generated WSDL", well, I'd rather not at this point. For reasons I'd rather not go into, having a WSDL that describes the service *as it was built* would be beneficial to me (and the developers at my company who may need to deploy an older version of the service for some reason). I'd also much prefer to *not* go from WSDL->Java--starting with Java and generating a WSDL is far less tedious. -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] context lookup issue
Can you do the same lookup successfully via a non-axis2 class inside
WEB-INF/classes ?
Robert
On 9/21/06, Johan Lundberg <[EMAIL PROTECTED]> wrote:
I am using Axis2 nightly build from 31 August and cannot lookup the
java:comp/env context from a created InitialContext created inside a
class in the aar-file
When I do this:
Context initContext = new InitialContext();
Context envContext = (Context)initContext.lookup("java:comp/env");
I get a NameNotFoundException.
By the way, I am using the distributed axis2.war in tomcat 5.5.17
Any ideas?
johan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: CodeGeneration error while using commandline batch file WSDL2Java
Darn, this "delegation" thing never works for me... ;) Will do. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 6:25 PM To: axis-user@ws.apache.org Subject: Re: CodeGeneration error while using commandline batch file WSDL2Java Brennan, Please file a JIRA bug with *your* wsdl :) -- dims On 9/20/06, Spies, Brennan <[EMAIL PROTECTED]> wrote: > > > > > Sharad, > > > > This is definitely a bug (I can reproduce using similar WSDL on the latest > nightly). It throws a RuntimeException complaining that "Element QName is > null for [/message/name/text()]!" > > > > You should file a JIRA issue on this: > https://issues.apache.org/jira/browse/AXIS2. > > > > > > -Original Message- > From: Sharad Baronia [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 20, 2006 5:32 PM > To: axis-user@ws.apache.org > Subject: RE: CodeGeneration error while using commandline batch file > WSDL2Java > > > > > > > Hi, > > > > After removed the Fault Exception, and then it generates the classes. But it > doesn't generate classes for each operation, and classes for input, & output > of an operation. > > I thing I am missing something. ! It misses the objective of code > generation. > > > > Can anyone help me > > > > /Sharad > > > > > > > From: Sharad Baronia [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 20, 2006 4:40 PM > To: axis-user@ws.apache.org > Subject: RE: CodeGeneration error while using commandline batch file > WSDL2Java > > > > Hi All, > > > > Sorry for causing confusion in my previous. This is my first to email to > this user group. > > > > I am using Axis2 nightly build (Sept-20) > > > > When using WSDL2Java, it generates runtime error : java.lang.RuntimeExcept > > ion: Element QName is null for CorporateActionExceptionFault [ name="CorporateActionExceptionFault"> > > type="tns:CorporateActionException"/> > > ]. > > > > I have attached wsdl file in my previous email. > > > > /Sharad > > > > > > > From: Sharad Baronia [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 20, 2006 4:13 PM > To: axis-user@ws.apache.org > Subject: CodeGeneration error while using commandline batch file WSDL2Java > > > > Hi, > > > > I was using Axis2 1.0 WS2DL2Java was working fine, but I was getting some > runtime error. So I decided to download nightly build which is giving me > runtime error. > > I have attached the wsdl file for reference. > > Help need!! > > > > > > Thanks, > > > > /Sharad > > > > > > C:\apache\axis2v1night\bin>wsdl2Java -uri c:\ > test1\corporateaction.wsdl -o c:\test1 -l java -a -s -t -ss -sd -g -u -ssi > > Using AXIS2_HOME: C:\apache\axis2v1night > > Using JAVA_HOME:C:\j2sdk1.4.2_12 > > Exception in thread "main" > org.apache.axis2.wsdl.codegen.CodeGenerationException > > : org.apache.axis2.wsdl.codegen.CodeGenerationException: > java.lang.RuntimeExcept > > ion: Element QName is null for CorporateActionExceptionFault! > > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener > > ationEngine.java:224) > > at > org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) > > at > org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) > > Caused by: > org.apache.axis2.wsdl.codegen.CodeGenerationException: > java.lang.Runt > > imeException: Element QName is null for CorporateActionExceptionFault! > > at > org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm > > itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:769) > > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener > > ationEngine.java:206) > > ... 2 more > > Caused by: java.lang.RuntimeException: Element QName is null for > CorporateAction > > ExceptionFault! > > at > org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm > > itter.getFaultParamElements(AxisServiceBasedMultiLanguageEmitter.java:1763) > > at > org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm > > itter.getFaultElement(AxisServiceBasedMultiLanguageEmitter.java:1713) > > at > org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm > > itter.loadOperations(AxisServiceBasedMultiLanguageEmitter.java:1430) > > at > org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm > > itter.createDOMDocumentForSkeletonInterface(AxisServiceBasedMultiLanguageEmit ter > > .java:1352) > > at > org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm > > itter.writeSkeletonInterface(AxisServiceBasedMultiLanguageEmitter.java:1297) > > at > org.apache.axis2.wsdl.codegen.emitter.AxisServiceBasedMultiLanguageEm > > itter.emitSkeleton(AxisServiceBasedMultiLanguageEmitter.java:733) > > ... 3 more > > > ___ > > All o
Axis2: xmlns="" in toEnvelope() method
Hi, I have problems when validating the incoming soap call which has been generated with the Axis2-generated stub ( I am using the latest nightly build). The problem is that the namespace is not recognized anymore. This is the error message: The element 'MessageTag' in namespace 'http://www.stockholm.se/xml/namespace/sgis/messageTag.xsd' has invalid child element 'IdTag'. List of possible elements expected: 'IdTag' in namespace 'http://www.stockholm.se/xml/namespace/sgis/messageTag.xsd'. This is the generated call before it has been packed into the SOAP envelope: What I found out is that the toEnvelope method in my Stub adds this xmlns=”” in the IdTag element. That’s the call after it has been packed into the Soap envelope: /> xmlns="http://www.stockholm.se/xml/namespace/sgis/messageTag.xsd"> /> Where does that come from? How can I avoid that? I have attached the xsd files for your attention! Thanks a lot for your help, Felix MessageTag.xsd Description: Binary data Belagenhetsadresser.xsd Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] context lookup issue
I am using Axis2 nightly build from 31 August and cannot lookup the
java:comp/env context from a created InitialContext created inside a
class in the aar-file
When I do this:
Context initContext = new InitialContext();
Context envContext = (Context)initContext.lookup("java:comp/env");
I get a NameNotFoundException.
By the way, I am using the distributed axis2.war in tomcat 5.5.17
Any ideas?
johan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis documentation
Anne Thomas Manes wrote:
The value of the SOAPAction HTTP header is a URI.
It may be (and often is) different from the endpoint URL (i.e.,
targetEndpointAddress).
The value of the SOAPAction URI is specified in the
definitions/binding/operation element in the WSDL in this line:
The SOAPAction URI does not need to resolve to a physical location. It
is simply a name used to indicate what action the service should
perform.
The value of the endpoint URL is specified in the
definitions/service/port element in the WSDL in this line:
http://company.com:8080/axis2/services/service-name"/>
The endpoint URL must resolve to a physical location.
Thanks, I haven't had my brain wrapped inside out yet, and programming
Java in anything but Java just seems quite unnatural to me.
I did try to generate the java stub from a wsdl file, but this just
generated a huge bunch of files without any hint as to what to do with
them, none of the file's name corresponds to the SOAP Action or the
"portName" (the later still confuses me because I think of a port as a
tcp port which is also in play).
I'm trying to find documentation that
a) makes sense to me
b) is verbose enough to allow me to do stuff
The example in the user-guide does not make it clear to me how to
construct a soap request message, set the soap action, send the request
to the web service and receive the result. The API documentation does
not it anything clearer.
I've spent two weeks searching for documentation and trying to figure
out what this is all about, and yet I find myself unable to write a
single line of code that does stuff.
I would expect to do something like
SOAPMessage requestSoap = new SOAPMessage();
SOAPMessage responseSoap = new SOAPMessage();
requestSoap.readXMLFile("requestfile");
HttpClient socket = new HttpClient(URL
"http://localhost:8080/ws/service";);
socket.connect();
socket.setHttpMethod("POST");
socket.addHttpHeader("SOAPAction","DoThis");
socket.addHttpBody(soapRequest);
socket.sendRequest();
socket.getResponse(responseSoap);
responseSoap.writeXMLFile("responsefile");
This pretty much corresponds to the flow of a RPC call, but I find it
immensely difficult to reduce the problem to anything like that from the
documentation at hand.
Is there some source of documentation that is actually consistent,
sufficient and selfcontained? - or do I need brain surgery to use Axis?
Thanks, Erik
--
Ph: +34.666334818 web: http://www.locolomo.org
X.509 Certificate: http://www.locolomo.org/crt/8D03551FFCE04F0C.crt
Key ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis - .NET Interop
Thanks Anne. I too thought wrapped doc/literal would be my best bet for interoperability. Attached are my WSDL, and some SOAP messages. The file javaSOAPMessages.txt contains the request and response messages captured when calling the Axis service from the Java client (which works beautifully). The file dotNetSOAPMessages.txt contains the request message captured when calling the Axis service from my .NET client. Unfortunately, for whatever reason, the TCP/IP monitor I'm using isn't capturing the SOAP response in this scenario. I'm working on figuring this out. However I know something is coming back because, like I said, I get back an array of two objects (as expected). They just don't have any values on any of their attributes. The one thing that jumps out at me is in the request messages, the Java version uses "soapenv" where the .NET version uses "soap". Aside from that the request messages appear to be identical so one would assume that the response messages coming back would be identical too. Note that this is just some test stuff for a presentation I'm doing for my group, but if we can get something like this working for .NET - Java interop, we want to look into using WS for some "real" stuff within our group. Any further ideas about what might be my problem are greatly appreciated. Brian --- Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > Wrapped doc/literal should work -- although you will > probably do > better using Axis 1.4 rather than Axis 1.3. There > still are some > problems with arrays, but you shouldn't have a > problem with the bean. > Please post some sample WSDLs and SOAP messages. > > Anne > > On 9/20/06, Brian Moffatt <[EMAIL PROTECTED]> > wrote: > > I've seen this exact problem addressed in the > archives > > but never with any clear solution. I was > wondering if > > this was something for which there is a known > solution > > and I'm just not finding it. > > > > Basically, I have an Axis based web service with 5 > > available methods. One returns a simple Java bean > > (made up of three Strings and an int) and one > returns > > an array of said beans. The others return > nothing. I > > am using Axis 1.3 and Apache Tomcat 5.0. I used > the > > document/literal wrapped mode. I got the service > > deployed fine and can call it successfully from > the > > generated Java client proxy code. > > > > My problem is when I try to call it from .NET. I > ran > > the WSDL through the wsdl.exe tool included with > > Visual Studio 2005 and wrote a simple driver > console > > app to call the generated code. It works. . . > sort > > of. The method that returns a bean, returns a > bean > > but all the fields are nulled out or zero. The > method > > that returns an array of beans, returns an array > of > > beans of the appropriate length, but all the > > attributes of the beans in the array are null / > zero. > > I did some testing and can get a method that just > > returns a String or primitive to interoperate > > correctly using Doc/Literal wrapped. > > > > One last thing. I did get the Axis -.NET > > communication to work completely with the complex > > types / arrays of complex types but had to use > > RPC/Encoded when creating my service with Axis to > > achieve success. Ironically, this is the only way > > that makes .NET yell at me for being WS-I > > non-compliant when I run wsdl.exe. > > > > > > Does this sound familiar to anyone? Is it a > common > > problem? Is there a known solution? I've read > that > > Doc/Literal wrapped is THE way to go if you want > Axis > > - .NET interop, but my experience has been that > > RPC/Encoded is the only way that works. I'd > rather > > use whatever is WS-I compliant. Any feedback is > > greatly appreciated. I'll gladly supply a WSDL, > SOAP > > messages, or other data from my test case anyone > > wishes to see. > > > > Thanks, > > > > Brian > > > > > - > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > LibraryDAO.wsdl Description: 3322443414-LibraryDAO.wsdl Request coming in from Java client: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://oracle.dao.tooltime.sete.stl.mo.boeing.com"/> Response going back to Java client: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://oracle.dao.tooltime.sete.stl.mo.boeing.com";> Stephen King 2 350 Gerald's Game Stephen King 1 500 The Shining Request coming in from .NET client: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.or
Re: No content length
nope. On 9/21/06, Doolittle, Todd <[EMAIL PROTECTED]> wrote: That would imply there was something in the WSDL that specified not to use chunked. I'm no web services expert. Can that be specified in the WSDL? -Original Message- From: Anthony Bull [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 6:37 PM To: axis-user@ws.apache.org Cc: Doolittle, Todd Subject: Re: No content length The HTTP spec says that if you are using chunked encoding type, then content-length can not be used, so yes. Its interesting because I used a generated client recently with a .NET service and by default the chunked encoding was turned off when I generated the client stub. Doolittle, Todd wrote: I think I figured it out. In the client stub's contstructor I turned off "CHUNKED" for the HTTP transport which now gives me a Content-Length header. _serviceClient.getOptions.setProperty(HTTPConstants.CHUNKED, false); Was that the right way to do it? -Original Message- From: Doolittle, Todd Sent: Wednesday, September 20, 2006 9:51 AM To: axis-user@ws.apache.org Subject: No content length I am trying to hit a public service (TerraService) with a client generated from last night's Axis 2 build. I believe the service is a ...NET service. I created the client from the WSDL2JAVA tool based on the WSDL. When I send a request, I get a fault back from the server stating that the Content-Length header is missing. Using tcpmon, I checked and it does look like it is missing. Is there some way to get Axis 2 to put the Content-Length header on the request? Here is the output from tcpmon: POST /TerraService2.asmx HTTP/1.1 SOAPAction: http://terraservice-usa.com/ConvertPlaceToLonLatPt User-Agent: Axis2 Host: terraservice-usa.com Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 183 http://schemas.xmlsoap...org/soap/envelope/";>http://terraservice-usa.com/";>TroyMichiganUSA 0 Here is the fault that was returned… Exception in thread "main" org.apache.axis2.AxisFault: HTTP Transport error : '411' - 'Length Required'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error : '411' - 'Length Required'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error : '411' - 'Length Required'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error : '411' - 'Length Required' at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:231) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:641) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:355) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:285) at com.terraservice_usa.TerraServiceStub.ConvertPlaceToLonLatPt(TerraServiceStub.java:814) at GetLonLat.main(GetLonLat.java:25) Caused by: org.apache.axis2.AxisFault: HTTP Transport error : '411' - 'Length Required'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error : '411' - 'Length Required' at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:335) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:210) ... 5 more Caused by: org.apache.axis2.AxisFault: HTTP Transport error : '411' - 'Length Required' at org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:141) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:329) ... 6 more This message, including any attachments, is the property of Sears Holdings Corporation and/or one of its subsidiaries. It is confidential and may contain proprietary or legally privileged information. If you are not the intended recipient, please delete it without reading the contents. Thank you. -- - Anthony Bull Senior Developer Black Coffee Software Ltd Level 13, Compudigm House, 49 Boulcott Street PO Box 10-192 The Terrace Wellington, New Zealand [EMAIL PROTECTED] Ph +64 4 472 8818 Fax +64 4 472 8811 Mob +64 021 303 692 - www.bcsoft.co.nz --- This email may contain confidential or privileged information, and is intended for use only by the addressee, or addressees. If you are not the intended recipient please advise the sender immediately and do not copy, use or disclose the contents to any other person or organisation. Black Coffee Software Ltd accepts no responsibility for viruses received with this email, or to any changes made to the original content. Any views or opinions expressed in this email may be personal to the sender and are not n
RE: No content length
Title: RE: No content length That would imply there was something in the WSDL that specified not to use chunked. I’m no web services expert. Can that be specified in the WSDL? -Original Message- From: Anthony Bull [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 6:37 PM To: axis-user@ws.apache.org Cc: Doolittle, Todd Subject: Re: No content length The HTTP spec says that if you are using chunked encoding type, then content-length can not be used, so yes. Its interesting because I used a generated client recently with a .NET service and by default the chunked encoding was turned off when I generated the client stub. Doolittle, Todd wrote: I think I figured it out. In the client stub’s contstructor I turned off “CHUNKED” for the HTTP transport which now gives me a Content-Length header. _serviceClient.getOptions.setProperty(HTTPConstants.CHUNKED, false); Was that the right way to do it? -Original Message- From: Doolittle, Todd Sent: Wednesday, September 20, 2006 9:51 AM To: axis-user@ws.apache.org Subject: No content length I am trying to hit a public service (TerraService) with a client generated from last night’s Axis 2 build. I believe the service is a ...NET service. I created the client from the WSDL2JAVA tool based on the WSDL. When I send a request, I get a fault back from the server stating that the Content-Length header is missing. Using tcpmon, I checked and it does look like it is missing. Is there some way to get Axis 2 to put the Content-Length header on the request? Here is the output from tcpmon: POST /TerraService2.asmx HTTP/1.1 SOAPAction: http://terraservice-usa.com/ConvertPlaceToLonLatPt User-Agent: Axis2 Host: terraservice-usa.com Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 183 http://schemas.xmlsoap...org/soap/envelope/">http://terraservice-usa.com/">TroyMichiganUSA 0 Here is the fault that was returned… Exception in thread "main" org.apache.axis2.AxisFault: HTTP Transport error : '411' - 'Length Required'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error : '411' - 'Length Required'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error : '411' - 'Length Required'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error : '411' - 'Length Required' at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:231) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:641) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:355) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:285) at com.terraservice_usa.TerraServiceStub.ConvertPlaceToLonLatPt(TerraServiceStub.java:814) at GetLonLat.main(GetLonLat.java:25) Caused by: org.apache.axis2.AxisFault: HTTP Transport error : '411' - 'Length Required'; nested exception is: org.apache.axis2.AxisFault: HTTP Transport error : '411' - 'Length Required' at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:335) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:210) ... 5 more Caused by: org.apache.axis2.AxisFault: HTTP Transport error : '411' - 'Length Required' at org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:141) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:329) ... 6 more This message, including any attachments, is the property of Sears Holdings Corporation and/or one of its subsidiaries. It is confidential and may contain proprietary or legally privileged information. If you are not the intended recipient, please delete it without reading the contents. Thank you. -- - Anthony BullSenior DeveloperBlack Coffee Software LtdLevel 13, Compudigm House,49 Boulcott StreetPO Box 10-192 The TerraceWellington, New Zealand [EMAIL PROTECTED]Ph +64 4 472 8818Fax +64 4 472 8811Mob +64 021 303 692- www.bcsoft.co.nz--- This email may contain confidential or privileged information, and is intended for use only by the addressee, or addressees. If you are not the intended recipient please advise the sender immediately and do not copy, use or disclose the contents to any other person or organisation.Black Coffee Software Ltd accepts no responsibility for viruses received with this email, or to any changes made to the original content. A
Re: [Axis2] Undeploying a web service
Latest nightly should not have the locking problem. Can you please test and confirm? thanks, dims On 9/21/06, Kedar, Shahar <[EMAIL PROTECTED]> wrote: Hi All, Let say I want to undeploy a web service while Axis is running. What is the best way of doing that? Is it simply deleting the service folder (structured as an aar file)? The reason I'm asking is that sometimes when trying to delete a folder or even a single file, I am denied by the operating system. I presume that Axis2 needs to lock the folder (or aar file) once in a while when poling the repository for new or updated services, but it makes it very difficult to undeploy service dynamically. Is there any other way of programmatically undeploying a web service? Regards, Shahar Kedar -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] jar conflicts
Hi when i deploy axis web service in WAS5.0 te following error i used to get in server log files.? log4j:WARN No appenders could be found for logger (com.awpl.ws.servicebean.WsUtil). log4j:WARN Please initialize the log4j system properly. java.lang.SecurityException: class "org.apache.log4j.PropertyConfigurator"'s signer information does not match signer information of other classes in the same package at java.lang.ClassLoader.checkCerts(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.defineClass(ClassLoader.java(Compiled Code)) regards Giri babu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Issue with SOAP response
Yes build of Sep-18 -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 12:50 PM To: axis-user@ws.apache.org Subject: Re: [Axis2] Issue with SOAP response Are you using the latest nightly build? On 9/18/06, Charak, Vikas <[EMAIL PROTECTED]> wrote: > > My > WSDL as displayed by Axis2 in the web page has the following part > > > > > > When the service is invoked I get the following response. > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> > > > > xmlns:ns="http://SimpleService.webservices.wammis.com";> > Service Invocation was successful > > > > > > > > Why I do not see element name "impl:getCodeReturn" or "getCodeReturn" > anywhere in the response. By not having this, my external client Siebel > and XmlSpy complaints about the response. > Is Axis2 implementation of Ws-I basic profile correct? > > Any help is appreciated. > > Thanks. > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: unreachable statement
I'm getting some validation warnings - please try validating your wsdl - xml spy has a validator. Nevertheless, I was able to compile the code using a recent axis2 build . I recommend using ant to do your build ... you seem to be putting jars on your classpath which is the hard way: http://ws.apache.org/axis2/tools/1_0/CodegenToolReference.html#invoking HTH, Robert On 9/20/06, Fabio Alves de Araujo Ebner - DNA Solution <[EMAIL PROTECTED]> wrote: my wsdl - http://ws.apache.org/axis2"; xmlns:ns1="http://org.apache.axis2/xsd"; xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:ns0="http://agenteservidor/xsd"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; targetNamespace="http://ws.apache.org/axis2";> - - http://agenteservidor/xsd";> - - - - - - - - - - http://www.w3.org/2006/05/addressing/wsdl"; message="axis2:isLoginMessage" wsaw:Action="urn:isLogin" /> - http://schemas.xmlsoap.org/soap/http"; style="document" /> - - - - http://schemas.xmlsoap.org/soap/http"; style="document" /> - - - - - - - - - http://10.0.0.111:8080/axis2/services/VerificaLogin"; /> - http://10.0.0.111:8080/axis2/services/VerificaLogin"; /> - http://10.0.0.111:8080/axis2/rest/VerificaLogin"; /> and the command : java org.apache.axis2.wsdl.WSDL2Java -uri http://localhost:8080/axis2/services/VerificaLogin?wsdl -p br.com.dnasolution she return: log4j:WARN No appenders could be found for logger (org.apache.axis2.i18n.Project ResourceBundle). log4j:WARN Please initialize the log4j system properly. CLASSPATH component C:\tomcat\webapps\axis2\WEB-INF\classes\log4j.properties: ja va.util.zip.ZipException: error in opening zip file but create the .java, i put im netbeans, import ALL axis2\lib\*.jar and run.. then netbeans return that erro:: tks Caraio meu como e complicado mexer com o axis2 heim.. o 1.4 eu ja tava craque.. esse 2 so veio pra complicar.. tu conhece o tal deo XFire?? - Original Message - From: "robert lazarski" <[EMAIL PROTECTED]> To: Sent: Wednesday, September 20, 2006 3:51 PM Subject: Re: unreachable statement > Show us your wsdl please , and the options you pass to wsdl2java . > > Robert > > On 9/20/06, Fabio Alves de Araujo Ebner - DNA Solution > <[EMAIL PROTECTED]> wrote: > > > > > > why when i try compile my class create by WSDL2Java i got the erro: > > > > D:\Java\desenvolvimento\netbeans\AgenteServidor\src\src\br\com\dnasolution\c liente\VerificaLoginStub.java:121: > > unreachable statement > > org.apache.axis2.context.MessageContext > > _messageContext = new > > org.apache.axis2.context.MessageContext() ; > > D:\Java\desenvolvimento\netbeans\AgenteServidor\src\src\br\com\dnasolution\c liente\VerificaLoginStub.java:212: > > unreachable statement > > org.apache.axis2.context.MessageContext > > _messageContext = new > > org.apache.axis2.context.MessageContext() ; > > > > i put the axis2-kernel > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 and dotNet interoperateability
Looks to me like you need to engage the addressing module in the axis2 server so that there are addressing headers in the response. See the Axis2 documentaton for how to do this. David On 21/09/06, scott ken <[EMAIL PROTECTED]> wrote: My C# client (.dotNet 2.0 and WSE 3.0) generated the following SOAP message. http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xop="http://www.w3.org/2004/08/xop/include"; xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";> urn:uuid:8a8309c1-a21d-48ff-aa52-2647bb377cfc http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous http://localhost:8080/axis2/services/CMBWebService 2006-09-20T23:12:21Z 2006-09-20T23:17:21Z The reply message from Axis2 server is http://schemas.xmlsoap.org/soap/envelope/";> The C# client encountered this exception Unhandled Exception: Microsoft.Web.Services3.Addressing.AddressingFault: Message Information Header Required ---> Micros oft.Web.Services3.Addressing.AddressingFormatException: WSE202: The Action header is required when other address headers are present. --- End of inner exception stack trace --- at Microsoft.Web.Services3.Addressing.AddressingHeaders.CheckValid() at Microsoft.Web.Services3.Addressing.AddressingHeaders.Load(SoapEnvelope envelope) at Microsoft.Web.Services3.SoapEnvelope.PostLoad(Boolean loadAddressing) at Microsoft.Web.Services3.SoapEnvelope.PostLoad() at Microsoft.Web.Services3.SoapEnvelope.Load(XmlReader reader) at Microsoft.Web.Services3.Mime.XopDocument.LoadStartPart(MimePart startPart) at Microsoft.Web.Services3.Mime.XopDocument.LoadFromXopPackage(String contentType, Stream stream) at Microsoft.Web.Services3.Xml.SoapEnvelopeReaderWrapper..ctor(SoapClientMessage message, String messageContentType) at Microsoft.Web.Services3.WebServicesClientProtocol.GetReaderForMessage(SoapClientMessage message, Int32 bufferSize) at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) I guess it's about some configuration on client side or server side. Can someone tell me what the fix is? Thanks in advance, vick Stay in the know. Pulse on the new Yahoo.com. Check it out. -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WS-Addressing Interoperability Problem
Off the top of my head, if you'd prefer not to modify the generated classes so you can regenerate them easily, you can do: stub._getServiceClient().getOptions().setProperty(...) David On 18/09/06, Anthony Bull <[EMAIL PROTECTED]> wrote: Thanks, that worked awesome. I was using a code generated client, so I had to go in to the client Stub class and add that line of code to its constructor. Thanks for the quick response. Anthony. David Illsley wrote: > You need to do the following to the Options object you use to > comfigure your client: > options.setProperty(org.apache.axis2.addressing.AddressingConstants.WS_ADDRESSING_VERSION, > > org.apache.axis2.addressing.AddressingConstants.Submission.WSA_NAMESPACE); > > > Which will tell the addressing module to add 2004/08 headers rather > than 2005/08 headers. > Hope this helps, > David > > On 18/09/06, Anthony Bull <[EMAIL PROTECTED]> wrote: > >> Hi, I have been working on a proof of concept interoperability project >> between .NET WSE 3.0 and Axis2 web services for a client. >> >> For this I have a .NET WSE 3.0 client and service (written by another >> vendor) and corresponding Java Axis2 client and service (written by >> me). Everything is running nearly fine, in all combinations of these >> apps, including encrypted messages over HTTPS. >> >> The one issue I came across that I could not resolve nicely is that the >> WSE 3.0 service only recognises soap messages with WS-Addressing >> namespaces of August-2004. Any SOAP messages sent from my Axis 2 Java >> client to both the Axis 2 service and WSE 3.0 service have a >> WS-addressing namespace of August-2005 (which if I understand correctly >> is also the namespace for May-2006 WS-Addressing). >> >> The .NET service does not accept these messages, and returns an error. >> The vendor that wrote the client/server says that WSE 3.0 cannot be >> upgraded to use the new addressing spec, and that WSE will not >> officially be updated anytime soon to support it. This leaves the ball >> in my court only, in order to fix this. >> >> The Axis2 service recognises the older addressing specification that the >> .NET client is sending to it (2004/08), but I have not been able to >> configure it so I can send Axis2 messages with this older addressing >> specification. Looking at the Axis2 code, the 2005/08 specification >> namespace is hard-coded into the Java classes. The only way I could get >> it to work is to do my own build of the Axis2 addressing module and >> change the hardcoded namespace to be 2004/08. While this works, it is >> dodgy and probably won't work correctly when other modules that are >> built on top of addressing are added. >> >> The addressing module page for Axis 2 states that "This is an >> implementation of WS-Addressing submission version (2004-08) and >> WS-Addressing 2005-08 versions.". My question is, how do I get my Axis2 >> code to generate messages that use the 2004-08 specification? >> >> cheers, >> Anthony Bull. >> >> -- >> - >> Anthony Bull >> Senior Developer >> Black Coffee Software Ltd >> Level 13, Compudigm House, >> 49 Boulcott Street >> PO Box 10-192 The Terrace >> Wellington, New Zealand >> >> [EMAIL PROTECTED] >> Ph +64 4 472 8818 >> Fax +64 4 472 8811 >> Mob +64 021 303 692 >> - >> www.bcsoft.co.nz >> --- >> This email may contain confidential or privileged information, >> and is intended for use only by the addressee, or addressees. >> If you are not the intended recipient please advise the sender >> immediately and do not copy, use or disclose the contents to >> any other person or organisation. >> Black Coffee Software Ltd accepts no responsibility for viruses >> received with this email, or to any changes made to the original >> content. Any views or opinions expressed in this email may be >> personal to the sender and are not necessarily those of Black >> Coffee Software Ltd. >> --- >> >> >> >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- - Anthony Bull Senior Developer Black Coffee Software Ltd Level 13, Compudigm House, 49 Boulcott Street PO Box 10-192 The Terrace Wellington, New Zealand [EMAIL PROTECTED] Ph +64 4 472 8818 Fax +64 4 472 8811 Mob +64 021 303 692 - www.bcsoft.co.nz --- This email may contain confidential or privileged information, and is intended for use only by the addressee, or addressees. If you are not the intended recipient please advise the sender immediately and do not copy, use or disclose the contents to any other person or organisation. Black Coffee Software Ltd accepts no res
Re: Integration of AXIS in Spring
If you are using Axis2, you can follow this document: http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/1_1/spring.html Provided you use the axis2 nightlies or wait a week or so for the next release. If using Axis 1.x , seach the spring forums as IIRC they use a class from the old jax-rpc spec to wire the two together. HTH, Robert On 9/21/06, Reddy, Sanket (US - Hyderabad) <[EMAIL PROTECTED]> wrote: HI All I have my project based on spring framework. And now I want to show some module of my code using the Webservices.I have chosen AXIS as a Soap engine framework. And now I want to integrate AXIS in Spring. How can I do that? How can I show some module of my code as WS? Regards Sanket This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Can't access my Axis 2 admin page after installing rampart module
Hello, i followed your rules from Axis 1 bin distribution readme: Please follow each of the following steps: Note - These instructions assume that the Axis2.war is already deployed in Tomcat 1.) Download the rampart-1.0.mar and addressing-1.0.mar from http://ws.apache.org/axis2/modules/ 2.) To engage the rampart (WSS4J) module add the following line to axis2.xml in axis2/WEB-INF/conf/ 3.) Copy samples/security/SecureService.aar to axis2/WEB-INF/services/ directory 4.) Copy all jars other than the secUtil.jar in the samples/security/lib directory to axis2/WEB-INF/lib/ 5.) Copy the downloaded rampart-1.0.mar to Axis2/WEB-INF/modules/ directory 6.) Start Tomcat If you are using JDK 1.5, please download and copy xalan-2.7.0.jar to axis2/WEB-INF/lib/ and samples/security/lib. xalan-2.7.0 - http://www.apache.org/dist/java-repository/xalan/jars/xalan-2.7.0.jar But at 6. i get this jsp error now(before installing rampart all was fine): HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause org.apache.jasper.JasperException org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966) org.apache.jsp.axis2_002dweb.index_jsp._jspService(index_jsp.java:73) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause java.lang.NullPointerException org.apache.jsp.axis2_002dweb.include.httpbase_jsp.jspInit(httpbase_jsp.java:22) org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:78) org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:155) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:315) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966) org.apache.jsp.axis2_002dweb.index_jsp._jspService(index_jsp.java:73) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) I am currwently using -Java 1.5.0_08 -Axis 2 Version 1 -Tomcat 5.5 Thanks for any suggestions/help anyways. _ Die neue MSN Suche Toolbar mit Windows-Desktopsuche. Suchen Sie gleichzeitig im Web, Ihren E-Mails und auf Ihrem PC! Jetzt neu! http://desktop.msn.de/ Jetzt gratis downloaden! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Using 'type' attribute for the message part
Hi Anne, Thank you. Much appreciated. Shahar -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Thursday, September 21, 2006 8:27 AM To: axis-user@ws.apache.org Subject: Re: [Axis2] Using 'type' attribute for the message part Yes -- that is correct. If you are using document style, your message part MUST reference an element. Anne On 9/21/06, Kedar, Shahar <[EMAIL PROTECTED]> wrote: > Hi Anne, > > Does this mean that if I'm using the Doc style, and my operation has an > input of native type (let say integer), then I'm required to have an > element tag in the schema with @type xsd:integer, and in the message tag > have a wsdl:part tag with @element and not @type? > > Regards, > Shahar Kedar > > -Original Message- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 20, 2006 7:48 PM > To: axis-user@ws.apache.org > Subject: Re: [Axis2] Using 'type' attribute for the message part > > Brennan, > > The semantics of type vs element in is defined in the WS-I > Basic Profile, Section 4.4.1 [1]. > > You must use @type when using RPC style; you must use @element when > using document style. > > With document style, you specify the literal schema of the element > contained in the SOAP Body; therefore, the message may contain at most > one body part, and that part must reference an element definition. It > must not reference a type definition. > > With RPC style, you specify the types of the parameters that must be > passed in the SOAP Body, but not the literal schema. The message > definition must contain a part for each parameter, and those parts > must reference a type definition. At runtime, the SOAP engine is > responsible for dynamically constructing the element contained in the > SOAP Body as follows: > - It generates a wrapper element that has the same local name as the > operation, and which is qualified by the namespace specified in the > definition in the binding. This wrapper element has no > formally specified type or schema. > - It generates an accessor element for each parameter. The accessor > elements are non-qualified, and they get their local name from the > @name in the . The type of each accessor element is the > type specified in the WSDL part definition. > > For example, if you have: > > > > > > ... > > > >... > > > > ... > > > > The message on the wire would look like: > > > > some string > some string > > > > [1] > http://www.ws-i.org/Profiles/BasicProfile-1.1.html#Bindings_and_Parts > > On 9/18/06, Spies, Brennan <[EMAIL PROTECTED]> wrote: > > Yes, I am using the most recent nightly build. The input and output is > > Doc/literal... > > > > > > > > > transport="http://schemas.xmlsoap.org/soap/http"; /> > > > > > > > soapAction="urn:ejgallo:workflow:service:action/Action" /> > > > > > > > > > > > > > > > > > > > > > > I can file a bug (no problem) since it's clear the lack of a return > doc is a > > bug, but I also wanted to know what is meant when a 'type' is > specified in > > the WSDL, i.e., what SHOULD be the result of such a configuration in > terms of > > what is generated in the SOAP, and more specifically to Axis2, the > generated > > classes? > > > > Brennan > > > > -Original Message- > > From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] > > Sent: Monday, September 18, 2006 11:42 AM > > To: axis-user@ws.apache.org; [EMAIL PROTECTED] > > Subject: Re: [Axis2] Using 'type' attribute for the message part > > > > Hi, > > What kind of binding do you have ? > > > > Ajith > > > > On 9/18/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > > > Are u using the nightly build? If so, please open a issue/bug. > > > > > > thanks, > > > dims > > > > > > On 9/18/06, Spies, Brennan <[EMAIL PROTECTED]> wrote: > > > > Axis devs, > > > > > > > > Got a question regarding the use of types for message parts rather > than > > > > elements...specifically, what are the semantics of it? Reading the > WSDL > > spec > > > > does not clarify this for me. > > > > > > > > For example, suppose you have an output message defined as > > > > > > > > > > > > > > > > > > > > > > > > Using the Axis code generator with XMLBeans databinding, the > ResponseType > > > > class will be generated, but there is no corresponding *Document > class. > > Also, > > > > the methods in the generated code look more like an IN ONLY MEP > rather > > than > > > > IN-OUT--i.e., the skeleton has no return value, hence no > meaningful SOAP > > > > response is generated. > > > > > > > > Brennan > > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAI
Problem with WSDL2Java generation
Hello, When I try to generate Java code of a WSDL-file (using the eclipse plugin, newest release of axis2), I get an error message telling me "SchemaCompilationException: Unsupported content Complex Content !". Is there any known workaround (e.g. newer jar files of a nightly build) or have I to do a redesign of my schemas? best regards, Kai Huener - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Axis2] Action mappings
Hello, I have this problem with every wsdl I try to “publish” a webservice for. Help would be very much appreciated :-) Thanks, Brecht From: Brecht Yperman [mailto:[EMAIL PROTECTED] Sent: woensdag 20 september 2006 17:09 To: axis-user@ws.apache.org Subject: [Axis2] Action mappings Hi, I have a question about action mappings. So it finds the wrong operation, I guess because all the input-action-mappings are the same. What am I doing wrong? Thanks, Brecht
Re: [Spam] Re: classpath
Fabio, to prevent the log4j warning, you may create a "config" directory, add it to your classpath, and put inside a log4j.properties file with the following contents: # Start of log4j.properties log4j.rootCategory=INFO, CONSOLE log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender log4j.appender.CONSOLE.Threshold=DEBUG log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout log4j.appender.CONSOLE.layout.ConversionPattern=%d %5p [%c] %m%n # End of log4j.properties If you have further questions regarding log4j configuration, you will find better answers in the log4j newsgroup, as Marting points. Regards Fabio Alves de Araujo Ebner - DNA Solution wrote: > ok.. i put but all there but she still return the error: > > C:\exemplo1>java org.apache.axis2.wsdl.WSDL2Java -uri > http://localhost:8080/axis > 2/services/VerificaLogin?wsdl -p br.com.dnasolution > log4j:WARN No appenders could be found for logger > (org.apache.axis2.i18n.Project > ResourceBundle). > log4j:WARN Please initialize the log4j system properly. > Exception in thread "main" java.lang.NoClassDefFoundError > at > org.apache.axis2.schema.typemap.JavaTypeMap.class$(JavaTypeMap.java:7 > 1) > at > org.apache.axis2.schema.typemap.JavaTypeMap.(JavaTypeMap.java > :99) > at > org.apache.axis2.schema.writer.JavaBeanWriter.(JavaBeanWriter.j > ava:78) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > > at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown > Source) > > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown > Sou > rce) > at java.lang.reflect.Constructor.newInstance(Unknown Source) > at java.lang.Class.newInstance0(Unknown Source) > at java.lang.Class.newInstance(Unknown Source) > at > org.apache.axis2.schema.util.SchemaPropertyLoader.(SchemaProp > ertyLoader.java:42) > at > org.apache.axis2.schema.SchemaCompiler.(SchemaCompiler.java:159 > ) > at > org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(Simp > leDBExtension.java:68) > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener > ationEngine.java:140) > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) > at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) > Caused by: java.lang.ClassNotFoundException: > org.apache.axis2.databinding.types. > Time > at java.net.URLClassLoader$1.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(Unknown Source) > at java.lang.ClassLoader.loadClass(Unknown Source) > at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) > at java.lang.ClassLoader.loadClass(Unknown Source) > at java.lang.ClassLoader.loadClassInternal(Unknown Source) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Unknown Source) > ... 15 more > - Original Message - > From: "Martin Gainty" <[EMAIL PROTECTED]> > To: > Sent: Wednesday, September 20, 2006 1:20 PM > Subject: Re: [Spam] Re: classpath > > >> whenever you call your PrettyPrint routines in Jalopy you will need > Log4J*.jar ON YOUR CLASSPATH >> and because Log4j reads Log4j.properties to initialise itself you will > need Log4j.properties ON YOUR CLASSPATH >> the proper configuration of which is the developer's responsibility > (ie.you need to properly configure the properties file) >> M- >> * >> This email message and any files transmitted with it contain confidential >> information intended only for the person(s) to whom this email message is >> addressed. If you have received this email message in error, please > notify >> the sender immediately by telephone or email and destroy the original >> message without making a copy. Thank you. >> >> >> >> - Original Message - >> From: "Fabio Alves de Araujo Ebner - DNA Solution" > <[EMAIL PROTECTED]> >> To: ; "Martin Gainty" <[EMAIL PROTECTED]> >> Sent: Wednesday, September 20, 2006 11:47 AM >> Subject: Re: [Spam] Re: classpath >> >> >>> i remove the %AXIS2_LIB%\log4j-1.2.13.jar; >>> >>> and got that erro: >>> >>> C:\exemplo1>java org.apache.axis2.wsdl.WSDL2Java -uri >>> http://localhost:8080/axis >>> 2/services/VerificaLogin?wsdl -p br.com >>> Exception in thread "main" java.lang.NoClassDefFoundError >>>at >>> org.apache.axis2.schema.typemap.JavaTypeMap.class$(JavaTypeMap.java:7 >>> 1) >>>at >>> org.apache.axis2.schema.typemap.JavaTypeMap.(JavaTypeMap.java >>> :99) >>>at >>> org.apache.axis2.schema.writer.JavaBeanWriter.(JavaBeanWriter.j >>> ava:78) >>>at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native >>> Method) >>> >>>at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown >>> Source) >>> >>>at > sun.reflect.Deleg
