search

javaee / metro-wsit

https://javaee.github.io/metro-wsit/
Other
9 stars 24 forks source link

Policy does not set webservice features until WSDL generation #793

Open glassfishrobot opened 16 years ago

glassfishrobot commented 16 years ago

Filing this issue for tracking purposes. This is the excerpt from he past discussions.

When policy reads the WSIT configuration during generation, the AddressingWSDLGeneratorExtension does not get to know about it and cannot generate WSDL addressing extensions accordingly. This is not really a problem right now because we still have the policy assertions. However, there might be similar conflicts in other domains sooner or later. A solution would be to invoke the policy processing code before WSDL is being generated (see also WSIT configuration for providers).

https://wsit.dev.java.net/issues/show_bug.cgi?id=487 has dependency on this fix.

Environment

Operating System: All Platform: All

Affected Versions

[1.0]

glassfishrobot commented 16 years ago

Reported by ramapulavarthi@java.net

glassfishrobot commented 16 years ago

ramapulavarthi@java.net said: changing the silly summary.

glassfishrobot commented 16 years ago

ritzmann@java.net said: Target milestone 1.3.

glassfishrobot commented 16 years ago

ritzmann@java.net said: Wave for Metro 1.1.1.

glassfishrobot commented 16 years ago

ritzmann@java.net said: New target milestone. Needs JAX-WS 2.2.

glassfishrobot commented 15 years ago

ritzmann@java.net said: Still no JAX-WS 2.2.

glassfishrobot commented 15 years ago

ritzmann@java.net said: .

glassfishrobot commented 15 years ago

ritzmann@java.net said: waiving for 2.0

glassfishrobot commented 15 years ago

ritzmann@java.net said: Setting to started to satisfy evaluation criteria.

glassfishrobot commented 15 years ago

ritzmann@java.net said: .

glassfishrobot commented 16 years ago

Was assigned to snajper

glassfishrobot commented 7 years ago

This issue was imported from java.net JIRA WSIT-793