Hi,
2) The capability class is given a default package and class name
which
matches the capability's URI. You can rename the package and class to
fit your needs. Just make sure you update its reference in the
muse.xml.
is it somehow possible to rename the MyCapability and MyService class
automatically? Since we're changing the WSDLs quite often we generate
the classes every day and we've to use perl scripts to change some
details in the classes every time, this is not very convenient from
my point of view.
I've changed the name of the class in the descriptor file for
example, but the name remains the same.
Once you know the pattern, you will probably get to the
point where you don't need wsdl2java and can create the capability
classes yourself, and add the configuration to muse.xml:)
Do you means we should write our own wsdl2java (actually we've
modified it already a lot) to parse the WSDLs and to generate
appropriate classes with reasonable names?
Regards, Alex
-----Original Message-----
From: Alexander Willner [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 02, 2007 12:26 PM
To: [email protected]
Subject: Re: WSDL2Java, Capabilities - Newbie
Hi Nelson,
I would like to know if it's a default behavior that when I run
wsdl2java, it always generate IMyCapability.java and
MyCapability.java
yes I think it is the default behavior.
When I run wsdl2java -j2ee axis2 -wsdl SimpleResource.wsdl, it
generates the correct directories, but still java files are
IMyCapability.java and MyCapability.java.
I think you should use "-descriptor FILE The Muse descriptor to
use" but anyway we were not able to change to name of the MyCapability
and MyService class. Have you found a solution already?
Regards, Alex
Am 31.08.2007 um 00:51 schrieb Nelson Kotowski:
Hi everyone,
How're you doing?
I'm working on Muse Tutorial and i would like to know if it's a
default behavior that when i run wsdl2java, it always generate
IMyCapability.javaand MyCapability.java, with such names, and how to
proceed if i want to change it. I mean, in the samples directory
(eg.,
\muse- 2.2.0-bin\samples\j2ee\simple\src\org\apache\muse\test\simple
\second) there
are pairs of capabilities files, but their names are strictly related
to the each operation defined. How come that happened :) ? Was it a
simple rename file operation? :)
Another thing: When you define the Capability concept, in the
Programming Model, do you mean that one capability stand for an
entire
Java Class? Or does a capability stand for methods that a Java Class
provides (i mean, a java class with 10 methods would be said to have
10 capabilities?)?
Best regards,
Nelson Kotowski.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
