Could you provide some more detail on how you are running wsdl2java
(command line used, what the artifacts are, etc.)? Even better would be if
you opened a JIRA item and attached your files so we could recreate the
test ourselves; if you can't post the exact files, perhaps try to narrow
down the parts causing a problem and send examples files that illustrate
the behavior.
Thanks,
Dan
Mario Macías <[EMAIL PROTECTED]> wrote on 05/23/2007 08:13:54 AM:
> Hi everybody,
>
> After using wsdl2java, here are explained some bugs which I have found:
>
> - Generated build.xml is incomplete and doesn't put all the needed files
on
> the WAR file.
> - When you describe a capability in muse.xml:
> <capability>
>
<capability-uri>http://ws.sorma.eu/eerm/MyCapability</capability-uri>
> <java-capability-class>eu.sorma.ws.eerm.MyCapability</java-
> capability-class>
> </capability>
> When classes are generated, it creates one based on <capability-uri>,
then
> another from <java-capability>. The first is completed, and the second
don't.
> It should create only one (the completed). If URI and CLASS descriptions
are
> equivalent, it creates first the good class, then overwrite it with the
wrong
> class.
> - It generates the class
> org.apache.muse.ws.metadata.impl.SimpleMetadataExchange, which is void
and
> must be deleted, because this class is implemented in Muse libraries and,
if
> you don't do it, will try to execute the void class and the service won't
> work.
>
> Regards,
> --
> Mario Macías Lloret
> Barcelona Supercomputing Center research staff
> Autonomic Computing and e-Business Platforms
> [EMAIL PROTECTED]
> Phone: +34 - 934134049
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
