Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for WebServiceFeature's to JaxWsPortProxyFactoryBean [SPR-5712] #10382

Closed
spring-projects-issues opened this issue May 3, 2009 · 3 comments
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Rustam Abdullaev opened SPR-5712 and commented

The current implementation of JaxWsPortProxyFactoryBean does not support specifying any WebServiceFeature's for the client proxy. A Web Service Feature is another way of extending functionality of web services, similar to SOAP handlers (but different).

It seems like JaxWsPortClientInterceptor.prepare() always invokes Service.getPort(QName portName, Class serviceEndpointInterface), there is no way to invoke Service.getPort(QName portName, Class serviceEndpointInterface, WebServiceFeature... features) using Spring at this time.

There should be a way to specify additional web service features while configuring JaxWsPortProxyFactoryBean similar to the way handlers are specified.


Affects: 2.5.6

Referenced from: commits 4955a73

@spring-projects-issues
Copy link
Collaborator Author

Stefan Reich commented

I have an implementation of this feature, that I use to enable the XML schema validation of the JAX-WS RI from SUN. Only problem is the WebServiceFeature is a jax-ws 2.1 feature, which is available in JSE 6, but not J2se 5. Does Spring 3 require jse 6?

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

Spring does not require Java SE 6 yet, and won't be able to do so any time soon: primarily for Java EE 5 compatibility (since EE 5 servers usually ship with SE 5 underneath) as well as for WebSphere 6.1 compatibility (a J2EE 1.4 server on Java SE 5).

That said - we do compile against Java SE 6 and hence may support JAX-WS 2.1 features when available. There are ways to support WebServiceFeatures that way, while at the same time preserving compatibility with JAX-WS 2.0. I'll see what we can do for Spring 3.0.3 still.

Juergen

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

Added for Spring 3.0.3, in the form of a "webServiceFeatures" bean property on JaxWsPortClientInterceptor/PortProxyFactoryBean: accepting an array of WebServiceFeature objects (e.g. specified as inner <bean> elements) or WebServiceFeature class name Strings (with feature objects to be constructed through their default constructor).

Juergen

@spring-projects-issues spring-projects-issues added type: enhancement A general enhancement in: web Issues in web modules (web, webmvc, webflux, websocket) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 3.0.3 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants