About Question enthuware.ocejws.v6.2.123 :

[himaiMinh]

In javax.xml.ws.Service's API, I don't see any getXXXPort methods.
But in your generated class annotated with @WebServiceClient, there is a@WebEndpoint method, getXXXPort() method and a getXXXPort(WebServiceFeature ... feature) method.

I have this:

Code: Select all

//Only relevant part shown
@WebServiceClient(name = "MathServiceImplService"....)
public class MathServiceImplService extends Service
{
   @WebEndpoint(name = "MathServiceImplPort")
    public MathService getMathServiceImplPort() {
      ....
     }
   @WebEndpoint(name = "MathServiceImplPort")
    public MathService getMathServiceImplPort(WebServiceFeature... features) {
     ...
    }
}

[fjwalraven]

Then you are both using an old version of JAX-WS.

Check the generated client source and verify the version

/**
* This class was generated by the JAX-WS RI.
* JAX-WS RI 2.1.6 in JDK 6
* Generated source version: 2.1
*
*/

Als verify the version of wsimport

wsimport -version
JAX-WS RI 2.1.6 in JDK 6

Regards,
Frits

[victor2016]

Hi,

As I understand declarative security is done using deployment descriptor (i.e. web.xml). But it is impossible to define a role in web.xml that allows/denies access to a method. So could the answer be also that it cannot be done using declarative security?

Thanks,
Victor.

[fjwalraven]

Hi Victor!

You can use Declarative Security and Programmatic Security.

Declarative Security can be done by using deployment descriptors and/or annotations.

Programmatic Security is only useful when the standard EE-security framework does not fulfil all your security constraints.

Check:
http://docs.oracle.com/javaee/5/tutorial/doc/bnbxe.html

Regards,
Frits