Hi,

No there are no error messages, that's why I thought it works. I used the
following command:
wsdl2java.bat -j2ee axis2 -wsdl NotificationServiceGroupEntry.wsdl -output
../../../target/entry

As I can see, the tool generates everything but the muse.xml file and the
router-entries. The WEB-INF/classes directory has the following structure
after generation.

classes
- wsdl
  --ServiceGroupEntry.wsdl
- commons-logging.properties
- log4j.properties

The services.xml file is generated correctly.
I noticed another "problem" with a different wsdl-file, but I don't know if
its intended. The wsdl2java-tool renames the rmd-file according to the
service name, but does not update the desciptor entry in the porttype
attribute of the new wsdl-file. Does the rmd-file-has to be the same as the
service-name?

Thanks,
Christian


Samstag, 10. März 2007 21:51
To: [email protected]
cc:
From: Andrew Eberbach <[EMAIL PROTECTED]>
Subject: Re: wsdl2java error for wsn-consumer


Ok, so there are no error messages generated? What are the command line
arguments that you are using? Also, are you saying that the consumer
capability is not being added to your muse.xml or that no muse.xml is
generated?

Thanks,
Andrew

Andrew Eberbach
Autonomic Computing
(919) 254-2645
T/L: 444-2645
[EMAIL PROTECTED]



Christian Ewers <[EMAIL PROTECTED]>
03/10/2007 03:43 PM
Please respond to
[email protected]


To
[email protected]
cc

Subject
Re: wsdl2java error for wsn-consumer







Hi,
sorry but I sent my latest mail too early...
The error message is gone, but the tool still doesn't generate the
muse.xml
and the router-entries.

Thanks,
Christian


Samstag, 10. März 2007 17:29
To: [email protected]
cc:
From: Andrew Eberbach <[EMAIL PROTECTED]>
Subject: Re: wsdl2java error for wsn-consumer


Hi,

This was a problem with the array parameter logic. The fix is checked in.

Thanks,
Andrew

Andrew Eberbach
Autonomic Computing
(919) 254-2645
T/L: 444-2645
[EMAIL PROTECTED]



Christian Ewers <[EMAIL PROTECTED]>
03/10/2007 11:11 AM
Please respond to
[email protected]


To
[email protected]
cc

Subject
wsdl2java error for wsn-consumer







Hi,
I want to add the wsn-comsumer apability to the WS-ServiceGroupEntry.wsdl.
Just adding the needed elements and edit the muse.xml works,  but I want
to
get the wsdl file "accepted" by the wsdl2java tool to stay compatible.

When I apply wsdl2java to the wsdl I get the following error:

#####

java.lang.NullPointerException
at
org.apache.muse.util.ReflectUtils.getArrayClassFromClass(ReflectUtils.java:131)
at
org.apache.muse.tools.inspector.ResourceInspector.getJavaType(ResourceInspector.java:509)
at
org.apache.muse.tools.inspector.ResourceInspector.createJavaMethod(ResourceInspector.java:374)
at
org.apache.muse.tools.inspector.ResourceInspector.getOperations(ResourceInspector.java:562)
at
org.apache.muse.tools.inspector.ResourceInspector.run(ResourceInspector.java:880)
at
org.apache.muse.tools.generator.analyzer.SimpleAnalyzer.inspect(SimpleAnalyzer.java:403)
at
org.apache.muse.tools.generator.analyzer.SimpleAnalyzer.analyze(SimpleAnalyzer.java:342)
at
org.apache.muse.tools.generator.Wsdl2Java.run(Wsdl2Java.java:173)
at
org.apache.muse.tools.generator.Wsdl2Java.main(Wsdl2Java.java:265)

SEVERE: [ID = 'CodeGenFailed'] Code generation failed, see the exception
information below.

An exception was caught: null

######

I added the following imports and elements to the wsdl-file

##definitions
xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2";

##import
<xsd:schema
     elementFormDefault="qualified"
     targetNamespace="http://docs.oasis-open.org/wsn/b-2";>
     <xsd:include schemaLocation="WS-BaseNotification-1_3.xsd" />
</xsd:schema>
##messages
<wsdl:message name="Notify">
      <wsdl:part name="Notify" element="wsnt:Notify"/>
      </wsdl:message>

##portType
<wsdl:operation name="Notify">
      <wsdl:input
      wsa:Action="

http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/NotifyRequest";

        message="tns:Notify"/>
        </wsdl:operation>


Any ideas what's wrong?
Thanks,
Christian



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to