please try dropping latest xerces jars into your JRE/lib/endorsed directories. it should work with both JDK1.4 and JDK1.5 (see http://java.sun.com/j2se/1.4.2/docs/guide/standards/)
thanks, dims On 11/15/05, Stefan Freyr Stefansson <[EMAIL PROTECTED]> wrote: > Hello again. > > I'm sorry for the long delay but it took a while for me to a) create a mockup > of the WSDL and b) get it approved to be sent out ;o) > > So here's the WSDL if anybody could find some time to look it over. Please > keep in mind that I had to do some search&replace on it so if there's any > mistake relating to words like "mycompany", "foo", "bar" or "smu", then it's > probably because of that. > > Any ideas would be greatly appreciated. > > One more thing though. My colleague over here had a weird problem with some > SOAP code that he had done a while ago. All of a sudden it turned out that > code that works when it's run with JDK 1.4.2 generates extra namespace stuff > when run from JDK 1.5. The difference looks something like this: > > JDK 1.4 would generate a SOAP messages similar to this (within the soap body): > <mytag>some text</mytag> > > While JDK 1.5 would generate something like this: > <mytag xmlns="">some text</mytag> > > (or something almost like that.. I don't have it exactly in front of me, maybe > there was a colon after xmlns but I'm not sure). > > Anyways... this difference resulted in a very similar error that I had with > Axis 1.3 and JWSDP, the runtime XML parsing exception. > > The weirdest thing is though that his code worked on my setup (with JDK 1.5) > but it didn't work with JDK 1.4 (exactly the opposite of my colleagues > environment). It looked like it had something to do with the interaction > between some of the neccessary libraries and the JDK. > > Does anybody know anything about this? If this is a known > "feature/bug/sillyness" it might help me get JWSDP and/or Axis 1.3 up and > running. > > Regarding the Axis2 problem (with TypeSystemHolder not being found). I think > that's very questionable behavior to have to put a generated source directory > into your runtime classpath... why isn't the compiled class put into the > output directory instead of the source directory? Anyways, I haven't verified > that putting it into the classpath works but I might do that when I manage to > find some time. > > Thanks for your answers so far. > > Kind regards, Stefan. > > On Thursday 10 November 2005 05:53, Ajith Ranabahu wrote: > > Hi, > > The error (regarding the Axis2 problem) tells me that the generated > > XMLBeans stuff is not correctly in the classpath. The > > schema_xxxxxxxxx_xmlbeans folder needs to be in the classpath rather than > > the source path. In the latest code I've added some enhancements , > > particularly the feature of generating an ant build script that neatly > > wraps up the xmlbeans stuff, moves things around and so on. > > Just as Anne suggests, having a bit more info about the WSDL will be useful > > also. > > > > On 11/9/05, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > > Does the service use rpc/encoded? Axis2 doesn't support SOAP Encoding > > > yet. > > > > > > A mock-up of the WSDL would certainly help us help you. At least tell us > > > a little bit about the WSDL: > > > - does it validate? (using Cape Clear SOA Editor, SOAPScope, xmlspy, etc) > > > - what's its style and use? > > > - if it's doc/lit, is it wrapped or unwrapped? > > > - does it have any unusual schema structures? > > > - are there any particular structures that generate the errors? > > > - can you at least give us a mock-up of the structures that cause the > > > errors? > > > > > > Anne > > > > > > On 11/9/05, Stefan Freyr Stefansson < [EMAIL PROTECTED]> wrote: > > > > Hello. > > > > > > > > First off, sorry for the long subject! > > > > > > > > I've been having a terrible time creating a web service client in Java > > > > that > > > > communicates with a .NET webservice. > > > > > > > > For the record, unfortunately I can't show you the WSDL that I'm using > > > > to > > > > generate code due to general paranoia. I do understand that this will > > > > make it > > > > that much more difficult to answer my questions :o( I'll try to make > > > > some > > > > sort of a mockup of it but that is a lot of work so I want to ask this > > > > first > > > > to see if anyone can figure this out without the WSDL. > > > > > > > > So the idea is basically to generate Java client code using one of > > > > Axis, Axis2 > > > > or JWSDP and use that code to communicate with the web service. > > > > > > > > I've tried this with Axis 1.2.1, Axis 1.3, JWSDP 1.6 and Axis2. In > > > > short, Axis > > > > 1.2.1 is the only thing that works! Axis 1.3 and JWSDP 1.6 both have > > > > some > > > > sort of a runtime exception when parsing XML. But what surprised me the > > > > most > > > > was Axis2. I realize that it's not final yet but the fact that it > > > > produced > > > > non-compilable code was a little more than I expected. Following is the > > > > error > > > > I get (I get the same error in more than one place): > > > > /home/stefan/hugsmidjan/test/consumer/src/axis2-generated/codegen/datab > > > >inding/org/xmlsoap/schemas/ArrayTypeAttribute.java > > > > > > > > Error: Error: line (19)package > > > > > > > > schemaorg_apache_xmlbeans.system.sB0E21F2812E326300081920E02D527F9.Type > > > >SystemHolder does not exist > > > > > > > > Anybody have any idea about what might be going on with these things? > > > > Are > > > > there any major differences betwene Axis 1.2.1 and 1.3 that might > > > > result in > > > > the fact that one works and the other one doesn't? Anybody have a clue > > > > as to > > > > why Axis2 is producing code that doesn't compile? > > > > > > > > I know this is all very vague and light on the details and for that I > > > > apologise. I just thought maybe someone has had a similar experience > > > > whent > > > > evaluating the different wsdl2java generators and might have some good > > > > pointers to share. > > > > > > > > Kind regards, Stefan Freyr. > > > > -- > > Ajith Ranabahu > > > -- Davanum Srinivas : http://wso2.com/blogs/
