[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1736) WS and seam:conversationId

Shane Bryzak (JIRA) jira-events at lists.jboss.org
Sun Jul 29 18:17:48 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBSEAM-1736?page=all ]

Shane Bryzak closed JBSEAM-1736.
--------------------------------

    Resolution: Won't Fix
      Assignee: Shane Bryzak

Closing this issue for now.

> 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
>         Assigned To: Shane Bryzak
>             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

        



More information about the seam-issues mailing list