[ http://issues.apache.org/jira/browse/MUSE-32?page=all ]
Dan Jemiolo updated MUSE-32:
----------------------------
Component/s: Deployment - Axis2
Fix Version/s: 2.0.0 M2
Description:
The JAX-WS spec defines a means of publishing web services that is similar to
Axis2's OMElement service signatures - you can get the raw SOAP request and
return the raw SOAP response. Given a JAX-WS implementation in Axis2, we should
be able to create an isolation layer for JAX-WS very easily by copying/tweaking
the Axis2 isolation layer and using the new javax.xml.ws interfaces in a few
spots. This small addition would be good for our "standards-based" project.
Ideally, JAX-WS will become popular and will remove the need to even have an
isolation layer (since the two things are essentially aiming at the same goal).
However, until JAX-WS has significant adoption in the J2EE and OSGi
communities, we must continue to have engine-specific isolation layers.
was:
The JAX-WS spec defines a means of publishing web services that is similar to
Axis2's OMElement service signatures - you can get the raw SOAP request and
return the raw SOAP response. Given a JAX-WS implementation, we should be able
to create an isolation layer for JAX-WS very easily by copying/tweaking the
Axis2 isolation layer and using the new javax.xml.ws interfaces in a few spots.
This small addition would be good for our "standards-based" project.
Ideally, JAX-WS will become popular and will remove the need to even have an
isolation layer (since the two things are essentially aiming at the same goal).
However, until JAX-WS has significant adoption in the J2EE and OSGi
communities, we must continue to have engine-specific isolation layers.
Affects Version/s: 2.0.0 M1
Due Date: 28/Jul/06
Assignee: Dan Jemiolo
Priority: Major (was: Minor)
Given the recent work on JAX-WS in Axis2, I think we can have this for M2 - we
will need to use the nightly snapshots for testing.
> Isolation layer to support JAX-WS
> ---------------------------------
>
> Key: MUSE-32
> URL: http://issues.apache.org/jira/browse/MUSE-32
> Project: Muse
> Issue Type: New Feature
> Components: Deployment - Axis2
> Affects Versions: 2.0.0 M1
> Environment: Any app server or platform that supports JAX-WS
> Reporter: Dan Jemiolo
> Assigned To: Dan Jemiolo
> Fix For: 2.0.0 M2
>
>
> The JAX-WS spec defines a means of publishing web services that is similar to
> Axis2's OMElement service signatures - you can get the raw SOAP request and
> return the raw SOAP response. Given a JAX-WS implementation in Axis2, we
> should be able to create an isolation layer for JAX-WS very easily by
> copying/tweaking the Axis2 isolation layer and using the new javax.xml.ws
> interfaces in a few spots. This small addition would be good for our
> "standards-based" project.
> Ideally, JAX-WS will become popular and will remove the need to even have an
> isolation layer (since the two things are essentially aiming at the same
> goal). However, until JAX-WS has significant adoption in the J2EE and OSGi
> communities, we must continue to have engine-specific isolation layers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
