[prev in list] [next in list] [prev in thread] [next in thread] 

List:       juddi-dev
Subject:    Re: javax.xml.ws.Holder not serializable
From:       Kurt T Stam <kurt.stam () gmail ! com>
Date:       2009-06-24 15:16:57
Message-ID: 4A424369.6020701 () gmail ! com
[Download RAW message or body]

Genius. And it's final so I can't extend it to implement Serializable, 
and it's part of the Java SE, so recompiling and adding our version is 
asking for trouble.


Jeff Faath wrote:
> The use of this class is determined by the JAX-WS generation code.  When the
> port type interfaces were created, the methods that use Holder were
> determined to have in-out arguments.  This Holder class is used so you can
> modify the object it "holds" and output it.  If you change the method
> signature by getting rid of this class, you will also affect the associated
> web service call - probably breaking it.
>
> -----Original Message-----
> From: Kurt T Stam [mailto:kurt.stam@gmail.com] 
> Sent: Tuesday, June 23, 2009 11:25 PM
> To: juddi-dev@ws.apache.org
> Subject: javax.xml.ws.Holder not serializable
>
> Is not serializable. So it is causing issues with RMI Transport.
> http://issues.apache.org/jira/browse/JUDDI-252
> Can we avoid using this class all together?
>
> It is used like
>
> public void saveSubscription(String authInfo,
>             Holder<List<Subscription>> subscription)
>             throws DispositionReportFaultMessage, RemoteException {
>         this.saveSubscription(authInfo, subscription);
>        
>     }
>
> Seems to me that it should be possible just to use List?
>
> --Kurt
>
>
>   

[prev in list] [next in list] [prev in thread] [next in thread]