Bug 779278 (SOA-1667)

Summary:	jUDDI v3 - RMI broken for Subscription API
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Len DiMaggio <ldimaggi>
Component:	jUDDI - within SOA	Assignee:	Nobody <nobody>
Status:	ASSIGNED ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.0.0 ER4	CC:	atangrin, kevin.conner, ldimaggi
Target Milestone:	---
Target Release:	FUTURE
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1667
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-04-08 20:04:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Len DiMaggio 2009-12-03 20:03:01 UTC

Date of First Response: 2009-12-16 13:57:29
project_key: SOA

See this JIRA:  http://issues.apache.org/jira/browse/JUDDI-252

Comment 1 Kurt Stam 2009-12-16 18:57:29 UTC

This is now fixed in the JAX-WS spec, and released in the 2.2 API.  https://jax-ws.dev.java.net/issues/show_bug.cgi?id=776
Do we know what version of JAX-WS SOA-P is going to ship with?

Comment 2 trev 2009-12-17 10:24:41 UTC

Current version is 2.1.3.2, this is unlikely to change. 
Is there a workaround?

Comment 3 Kurt Stam 2010-01-20 16:46:10 UTC

This issue should fix itself when JBossWS moves to the JAX-WS 2.2 API. Then the Holder object will become Serializable. Until then the workaround is to use inVM or JAX-WS Transport. FYI JBossESB is not using the Subscription API at the moment.

Comment 4 Kurt Stam 2010-01-22 20:53:17 UTC

I think JBossWS is not going to the JAX-WS 2.2 API until JBAS-6. So we'll have to wait till then, it's not going to be fixed for SOA-P 5

Comment 5 Kurt Stam 2011-01-21 18:51:01 UTC

jUDDI 3.1 ugraded to use JAX-WS 2.0, which fixed this issue: https://issues.apache.org/jira/browse/JUDDI-252
Note that likely we will only use JAX-WS 2.0 in JBoss AS 6 and up.

Comment 6 John Graham 2011-04-08 20:04:10 UTC

Test with jUDDI 3.1 update

Comment 7 David Le Sage 2011-09-27 04:13:27 UTC

Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-1667

The javax.ws.xml.Holder Object was not serializable causing saveSubscription calls to fails.  An upgrade to JAX-WS has fixed this issue meaning that this call now works without error.

Comment 8 Kurt Stam 2011-10-31 15:46:11 UTC

This is fixed, however it depends on the JAX-WS API version used; you will need version 2.2 which ships with AS6 and up.

Comment 11 Kurt Stam 2011-11-03 12:55:13 UTC

So yes, they will still see the issue then.