[JBoss JIRA] Created: (JBWS-1320) CTS: Refactor WrappedParameters to use accessors
by Jason T. Greene (JIRA)
CTS: Refactor WrappedParameters to use accessors
-------------------------------------------------
Key: JBWS-1320
URL: http://jira.jboss.com/jira/browse/JBWS-1320
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jaxws
Reporter: Jason T. Greene
Assigned To: Jason T. Greene
Priority: Blocker
Fix For: jbossws-2.0.0
The document/literal wrapped request/response objects in the CTS are not consitent, and are not always JavaBean conformant.
The only way to fix this is to either replicate the JAXB annotation parsing logic, and use injection instead, or to delegate to the JAXB accessor API. Regardless we will need an accessor API, since JAX-RPC still needs to use JavaBean / reflection access.
--
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
17 years, 5 months
[JBoss JIRA] Created: (JBWS-1322) CTS: Anonymous document/literal bare types fail
by Jason T. Greene (JIRA)
CTS: Anonymous document/literal bare types fail
-----------------------------------------------
Key: JBWS-1322
URL: http://jira.jboss.com/jira/browse/JBWS-1322
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Jason T. Greene
Priority: Blocker
Fix For: jbossws-2.0.0
Several tests in the CTS use anonymous bare types:
<element name="GetTrackerDataAction">
<complexType>
<sequence>
<element name="action" type="xsd:string"/>
<element name="harnessloghost" type="xsd:string"/>
<element name="harnesslogport" type="xsd:string"/>
<element name="harnesslogtraceflag" type="xsd:string"/>
</sequence>
</complexType>
</element>
This causes jaxbCtx.getTypeName() to return null, which is correct. However. the underlying problem is that our entire code-base is built around everything having an xml type. So we either need to refactor the system to allow for a null xml type, or alternatively generate a fake xml type like the JSR109 system.
The latter is probably the easiest to implement.
--
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
17 years, 5 months
[JBoss JIRA] Updated: (JBWS-1223) Conformance Requirements: Annotations
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1223?page=all ]
Thomas Diesler updated JBWS-1223:
---------------------------------
Fix Version/s: jbossws-2.0.0.CR1
(was: jbossws-2.0.0)
> Conformance Requirements: Annotations
> -------------------------------------
>
> Key: JBWS-1223
> URL: http://jira.jboss.com/jira/browse/JBWS-1223
> Project: JBoss Web Services
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: jaxws
> Reporter: Thomas Diesler
> Assigned To: Thomas Diesler
> Fix For: jbossws-2.0.0.CR1
>
>
> Please make sure jbossws conforms to these requirements.
> Resolving this issue means we do conform unless you create new issues that are linked to this one and are beeing dealt with seperately.
> 7.1 Correctness of annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
> 7.2 Handling incorrect annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
> 7.3 WebServiceProvider and WebService . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
> 7.4 JSR-181 conformance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
--
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
17 years, 5 months