You can't reuse the classes that axis generated. You will need to generate them yourself. And JAXB probably won't generate vectors, it will probably generate a List<Foo> or something.

And yes there is a java class to generate stubs. We need to add docs for it yet, but you can the usage in the source here:

http://svn.xfire.codehaus.org/viewrep/xfire/trunk/xfire/xfire-generator/src/main/org/codehaus/xfire/gen/WsGen.java?r=1437

- Dan

Robert Nicholson wrote:
I'm consfused by your last statement. I have control of the implementation but I need to be compatible with the existing WSDL which was derived from Axis. ie. we currently serialize Vectors the same way Axis does and no doubt that will need to remain the same.

Is there any way I can continue with xfire and still remain compatible then? I've got jetty working in my server right now and it seems to be a much nicer solution than relying on an external servlet engine with soap implementation like Axis.

The POJO I'm already using I wrote myself so I can easily write another one if need be.

I just need to be compatible with the existing WSDL.

Also, is there any way thru shell scripts to generated stubs? ie. are there main methods on the ant tasks at all or can this currently only be done in Ant or Maven?

I would very much like to ween ourselves off of Axis, especially as it's causing me a lot of problems right now just trying to expose a simple service. But I think there's a lot of value in being able to embed the SOAP implementation in our server.

So if I'm not mistaken JAXB or XMLBeans give you total control of the schema so that sounds like it should be possible to remain compatible with what Axis/Websphere was currently generating then?

I will try generics but can I get anything like this for a java.util.Vector if I use Vector <Object> in Java 5.0?

<complexType name="Vector">
    <sequence>
<element maxOccurs="unbounded" minOccurs="0" name="item" type="xsd:anyType"/>
    </sequence>
   </complexType>

Presumably I can also use the mapping file with Java 5.0 so I would haven't have to use generics but I see no reason why I cannot.


On May 10, 2006, at 6:52 AM, Dan Diephouse wrote:

Hi Robert,
We didn't add Vector support until just recently. Look for it in the next release! You will be able to use generics or mapping files with the Vector. Also, the WSDL first approach won't help you because it generates POJOs and the service interface for you.
Cheers,
- Dan

Robert Nicholson wrote:
I'm not sure about componentTypes.

I am just exposing a POJO. ie. not generating stubs from WSDL must I strongly type my collections?

If I have a method like

public Vector buildMeAListOfSomething();

do I have to use generics to type the Vector?

do I need mapping files for this to work?

...

Also,

If I use WSDL that defines the sequence and what's inside it and generate stubs from that will that allow me to use the above signature?

I do see the newly added support for Vectors in the CollectionType in SVN.




--Dan Diephouse
Envoi Solutions
http://envoisolutions.com
http://netzooid.com/blog



--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com
http://netzooid.com/blog

Reply via email to