Daniel

I've been working with Mario, who discovered this issue. Well,
problem is if you take the muse.xml file for the wsrf sample and re-generate
the project, it doesn't work. Then, either the muse.xml file in the sample is wrong, or the wsdl2java tool is broken. Either case, this is an issue and I don't believe we
should just ignore it.

What I'm personally worried about is that the tool could be broken and therefore
I will have to generate all by hand in my project.

By the way, maybe you remember that I reported some problems
trying to generate the code for the WsResource.wsdl

Now I think it has to do with the issue Mario is reporting. I'll explain why.
I first issued the same command you suggested and tried to test it with the
WsrfTestClient class, but  the ServiceGroup stuff didn't work.

I tried to follow the guide to include the ServiceGroup capability
updating the muse.xml file and copying all the wsdl files, but it
still didn't work. Now I think that it didn't work because the project
generated by the wsdl2java tool  was broken, as Mario says.

Pablo

Daniel Jemiolo wrote:





well, in this case, the samples are already built, you don't need to
recreate them - just run 'ant' from the /wsrf directory and it will make
the proper WAR. if you want to re-generate the skeleton code for the
project (w/ no implementation code), you should run wsdl2java on the WSDL
file:

wsdl2java -j2ee axis2 -wsdl WsResource.wsdl


Dan



Mario Macías <[EMAIL PROTECTED]> wrote on 05/24/2007 04:28:29 AM:

It happens with the $MUSE_HOME/samples/j2ee/wsrf example which comeswith
the
muse binary distribution. The command that I use is:
wsdl2java -descriptor muse.xml -j2ee axis2
What I obtain is:
 - generated build.xml is incomplete
 - it generates some void classes which belongs to the muse API (so the
generated classes are used in the execution instead of the library
classes).
Regards,


On Wednesday 23 May 2007 19:37:56 Daniel Jemiolo wrote:
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]

--
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]



--

========================================================================
0 0 0  Pablo Chacin               | Dept. d'Arquitectura de Computadors
0 0 0  e-mail: [EMAIL PROTECTED] | UPC-Campus Nord. Modul D6-212
0 0 0 phone: +34 +93 405 4059 | Jordi Girona, 1-3 U P C fax: +34 +93 401 7055 | 08034 Barcelona - SPAIN www: http://personals.ac.upc.es/pchacin
========================================================================

Reply via email to