[
http://jira.jboss.com/jira/browse/JBSEAM-1736?page=comments#action_12370358 ]
Shane Bryzak commented on JBSEAM-1736:
--------------------------------------
As far as I understand, it is not necessary to explicitly define header elements like
this. See the following notes:
http://www.w3.org/TR/wsdl#_soap:header
However, the following section of the spec does describe how to add optional elements to a
header:
http://www.w3.org/TR/2007/REC-wsdl20-primer-20070626/#id2301217
I recommend that you bring this up on the JBossWS forum and see what they say. Maybe
gSOAP is just being too strict.
WS and seam:conversationId
--------------------------
Key: JBSEAM-1736
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1736
Project: JBoss Seam
Issue Type: Bug
Components: WS
Affects Versions: 2.0.0.BETA1
Environment: Windows Vista, JBOSS 4.2.0 and SEAM 2.0.0.BETA1
Reporter: Stefano Zaccaria
Fix For: 2.0.0.CR1
After had worked with JBSEAM-1714 issue, now I'm trying the web service with gSOAP
client.
Of that thanks still Shane e Gavin!
It work well until I trying to read the "conversationId" from the header
message SOAP.
In fact the gSOAP reject the tag "seam:conversationId" at runtime so I
couldn't read it.
I create the gSOAP webservice client through the WSDL generate from JBOSSWS, and I've
noticed that there isn't a description about header.
Maybe this could be the problem.
In the seam reference in the chapter 20 is wrote:
"Unfortunately, because web services may be consumed
by a variety of web service clients written in a variety of languages, it is up to the
developer to implement
conversation ID propagation between individual web services that are intended to be used
within the
scope of a single conversation.
JBoss"
Now I understand that I duty management my self this parameter, but I want to know how
to describe it in the WDSL generated. Thanks!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira