[
http://jira.jboss.com/jira/browse/JBWS-844?page=all ]
Thomas Diesler updated JBWS-844:
--------------------------------
Fix Version/s: jbossws-1.0.5
(was: jbossws-1.0.4)
Rescheduled due to inactivity. Code freeze was on 17-Oct-2006.
Please communicate your intentions so we can act appropriately in a timely manner.
Past jira freeze, issues that are scheduled for a particular release past jira freeze
should be fixed and not allowed to be sliped. Jira freeze was on 18-Sep-2006.
If this is not possible for unforseen reason this must be escalated to the release
manageer in a timely manner.
If we don't stick to these simple rules, our release planing becomes meaningless.
Add support for a fully defined schema with a message endpoint
--------------------------------------------------------------
Key: JBWS-844
URL:
http://jira.jboss.com/jira/browse/JBWS-844
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jaxrpc
Reporter: Jason T. Greene
Assigned To: Darran Lofthouse
Fix For: jbossws-1.0.5
Currently a SOAPElement can only be mapped to a xsd:any type. We should add support for
mapping SOAPElement to a message that has been fully specified. This would allow for the
WSDL to represent a fully defined contract, and yet still allow the endpoint to have
flexible parsing.
-Jason
--
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