[
http://jira.codehaus.org/browse/XFIRE-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94677
]
Ivo van Dongen commented on XFIRE-969:
--------------------------------------
Well, I've tried some more things and it seems that one solution si to replace:
<xs:element name="stopSessionRequest"/>
with:
<xs:element name="stopSessionRequest">
<xs:complexType/>
</xs:element>
> java.lang.StackOverflowError in
> org.codehaus.xfire.aegis.type.basic.ObjectType.readObject
> -----------------------------------------------------------------------------------------
>
> Key: XFIRE-969
> URL: http://jira.codehaus.org/browse/XFIRE-969
> Project: XFire
> Issue Type: Bug
> Affects Versions: 1.2.4, 1.2.5
> Environment: Linux (Ubuntu Dapper), java 5, tomcat 5.5.17
> Reporter: Ivo van Dongen
> Assignee: Dan Diephouse
> Attachments: attachments.tar.gz
>
>
> After upgrading from XFire 1.2.2 to 1.2.5 (or 1.2.4) one of our services is
> broken. The service throws an StackOverflowError before ever reaching our
> code. The operation is a bit odd as it doesn't take parameters, this is
> because it uses the header information to invalidate a session. I've attached
> a wsdl with the troublesome operation (stopSession), the request/response and
> the stacktrace.
> We use Jaxb2 for the bindings.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
