Using JAX-WS 2.1.3 reference implementation on NetWeaver CE 7.1 SP3

[Former Member]

I’ve deployed the reference implementation of JAX-WS 2.1.3 into the “heavy” loader of my ear. Checking with “llr” the content of the “heavy” loader was OK.

If I deploy a JAX-WS web service inside of my ear, then the NetWeaver’s JAX-WS runtime is chosen and not the JAX-WS runtime deployed inside of “heavy” loader.

Is this a deployment issue for NetWeaver?

On JBoss, using a different runtime implementation for JAX-WS as that of JBoss is not a problem. You can correctly use the class loader hierarchy to solve this problem.

I need JAX-WS 2.1.3 because I’m using its streaming implementation for MTOM.

Thanks,

Radu

[Former Member]

did you use developer studio? because ear which deploy into NWCE has difererent deployment description.

I have tried JPA and JAXWS but didn't run well.

[Former Member]

Hi,

check the runtime you're using in dev Studio. SAP uses an own J2EE Runtime.

Regards,

Daniel

[Former Member]

Hi,

The problem is that SAP's runtime implementation for JAX-WS doesn't support streaming MTOM. This is only provided by the last release (2.1.3) of SUN's JAX-WS reference implementation.

Regards,

Radu