Quoting Dominik Heller <[EMAIL PROTECTED]>:
The source for,
org.apache.kandula.wscoor.RegistrationPortTypeRPCBindingStub
should be in build/src/ after you build kandula with Maven. These generated
files are not in SVN. Please try to identify where exactly you are getting this
NullPointerException.
java.lang.NullPointerException
at
org.apache.kandula.coordinator.RegistrationStub.registerOperation(RegistrationStub.java:56)
at
org.apache.kandula.coordinator.CoordinationContext.register(CoordinationContext.java:145)
at
org.apache.kandula.coordinator.at.AbstractParticipant.register(AbstractParticipant.java:72)
I also noticed that JBoss uses ReferenceParameters element while Kandula uses
ReferenceProperties element. Yet, I'm not sure whether this is the cause of the
problem. Please check whether the coordination context in AbstractParticipant
has the correct epr for the registration service given in the JBoss coordination
context (this is not the epr passed to the register method).
You can use the TCP monitor to repeatedly send messages to an endpoint or send
messages after manually editing them.
Thanks,
-- Dasarath
> >The Context from JBoss contains an XML element as content of the reference
> >property element. Though this is perfectly legal, when testing Kandula I
> >don't remember using XML elements as properties. Could you send the same
> >message to the Kandula participant service with the reference property
> >element having some URI instead and see whether it still coughs?
>
> The context from Kandula also contains a XML Element as far as I can tell
> named callbackRef. The following context was created by Kandula and send out
> from the client by invoking a web service.
>
> <soapenv:Header>
> <wsa:MessageID
>
soapenv:mustUnderstand="0">uuid:6db2c950-a709-11dc-ae3c-c0fda6681cc2</wsa:MessageID>
> <wsa:To
> soapenv:mustUnderstand="0">http://localhost:11865/ND_NEW/services/ND_NEW</wsa:To>
> <wsa:Action
>
soapenv:mustUnderstand="0">http://test.seitenbau.com/kandula/dominik/ND_NEW#saveCustomer</wsa:Action>
>
> <wsa:From soapenv:mustUnderstand="0">
>
<wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
> </wsa:From>
>
> <wscoor:CoordinationContext
> xmlns:wscoor="http://schemas.xmlsoap.org/ws/2004/10/wscoor";
> soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next";
> soapenv:mustUnderstand="0">
>
> <wscoor:Identifier>uuid:6d9afb90-a709-11dc-ae3c-c0fda6681cc2</wscoor:Identifier>
>
>
<wscoor:CoordinationType>http://schemas.xmlsoap.org/ws/2004/10/wsat</wscoor:CoordinationType>
>
> <wscoor:RegistrationService>
>
<wsa:Address>http://localhost:11865/BankingClient/services/registrationCoordinator</wsa:Address>
>
> <wsa:ReferenceProperties>
> <ns4:CallbackRef
>
xmlns:ns4="http://ws.apache.org/kandula";>uuid:6d9afb90-a709-11dc-ae3c-c0fda6681cc2</ns4:CallbackRef>
> </wsa:ReferenceProperties>
>
> </wscoor:RegistrationService>
> </wscoor:CoordinationContext>
> </soapenv:Header>
>
> My problem right now is that it is a little bit more complicated to change
> the context information in JBoss than I thought, so is there any easy way to
> change the context maybe in the server side handler? Because the context from
> JBoss and the context from Knadula aren't that different, I think a
> communication between JBoss and Kandula might be possible by inserting the
> referenceProperties Element into the JBoss conext. What do you think?
>
> thx
> -Dominik
> --
> GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
> Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail
>
> ---------------------------------------------------------------------
> 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]
