ws-kandula-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dasarath Weeratunge <>
Subject Re: Kandula1
Date Wed, 19 Dec 2007 18:21:01 GMT
Quoting Dominik Heller <>:


Thank you very much for putting time into testing Kandula with JBoss. 

To the best of my knowledge, the transaction identifier is not required in the
register message. However, the reference parameters in the header MUST be
included in the header of the register message and this has not been done. Most
likely as a result, JBoss is unable to correlate the register message with an
active transaction and thus responds with an error. Hence the
RegisterResponseType is NULL! I suspect the reason for reference parameters not
been included in the header is because Kandula uses the reference properties
element instead of reference parameters element. I will fix this problem today.

However, this is just one half of the problem. I hope JBoss handles reference
properties correctly for otherwise, you may come across a similar problem at
their end.

Do you have a JBoss endpoint that I may access?

When we first developed Kandula, we checked the status of JBoss ws-at
implementation but there was none. Since then no one has tried to use Kandula
with JBoss. The only other implementation that we have had at least some success
is that of IBM. Even there we have not tested against what they have in
WebSphere but one of their interop endpoints. We tried to test Kandula against
Microsoft code but that too ran into some problems. I do not know the details
since it was Thilina (another committer) who attended the interop.

-- Dasarath

> The NullPointerException occurs in the RegistrationStub
> --> return new
> EndpointReference(registerOperation(params).getCoordinatorProtocolService());
> the problem is that the registerOperation(params) doesn't return a
> registerResponseType and because of that there is the nullPointerException.
> >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)
> so although I am not completely sure what you mean I have checked the
> coordinationContext and the epr in the register method of the
> AbstractParticipant. The ctx seems to be ok and contains all the information
> send by the JBoss client. 
> the following soapMessage was sent from the JBoss client to the kandula Web
> Service:
> <env:Envelope xmlns:env="">
> <env:Header>
> <wscoor:CoordinationContext
> xmlns:wscoor=""
> env:mustUnderstand="1">
> <wscoor:Identifier>urn:-3f57fe6f:553:47694c80:2</wscoor:Identifier>
> <wscoor:RegistrationService>
> <wsa:Address
> <wsa:ReferenceParameters
> xmlns:wsa="">
> <wsarj:InstanceIdentifier
> </wsa:ReferenceParameters>
> </wscoor:RegistrationService>
> </wscoor:CoordinationContext>
> </env:Header>
> <env:Body>
> <ns1:checkForExistence xmlns:ns1="">
> <in0>rollback@test</in0>
> <in1>passwort</in1>
> </ns1:checkForExistence>
> </env:Body>
> </env:Envelope>
> after receiving the following message was sent to the registrationCoordinator
> by the kandula ws:
> <soapenv:Envelope xmlns:soapenv=""
> xmlns:wsa=""
> xmlns:xsd=""
> xmlns:xsi="">
> <soapenv:Header>
> <wsa:MessageID
> <wsa:To
> <wsa:Action
> <wsa:From soapenv:mustUnderstand="0">
> </wsa:From>
> </soapenv:Header>
> <soapenv:Body>
> <Register xmlns="">
> <ParticipantProtocolService>
> <wsa:Address xmlns:ns1=""
> absoluteURI="true" genericURI="true" host="localhost"
> path="/ND_NEW/services/participant" port="8081" scheme="http"
> schemeSpecificPart="//localhost:8081/ND_NEW/services/participant"
> <wsa:ReferenceProperties>
> <ns2:CallbackRef
> </wsa:ReferenceProperties>
> <wsa:ReferenceParameters/>
> </ParticipantProtocolService>
> </Register>
> </soapenv:Body>
> </soapenv:Envelope>
> The element that is missing is the callbackRef in the header which usually
> contains, but I might be wrong, the transactionIdentifier needed by the
> coordinator, right?
> So it seems that the cause for the nullPointerException is not the missing
> referenceProperties element in the first message, but the participant can't
> be registered by the coordinator anyways.
> has anyone ever tried to use jboss and kandula? So from my point of view it
> shouldn't be a problem for jboss and kandula to work together because they
> both are based on the same protocol, right?
> Thanks
> Dominik
> -- 
> GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
> Alle Infos und kostenlose Anmeldung:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message