river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike McGrady <mmcgr...@topiatechnology.com>
Subject Re: Namespace change
Date Sun, 16 Jan 2011 17:05:57 GMT
I hope this is right!

Sent from my iPhone

Michael McGrady
Principal investigator AF081_028 SBIR
Chief Architect
Topia Technology, Inc
Work 1.253.572.9712
Cel 1.253.720.3365

On Jan 15, 2011, at 1:37 PM, Greg Trasuk <trasukg@stratuscom.com> wrote:

> 
> On Sat, 2011-01-15 at 16:11, Peter Firmstone wrote:
>> With the namespace change, some proxy's may not find the 
>> org.apache.river.* classes they need in existing deployed clients, 
>> rather than increase the size of jsk-dl.jar (river-dl.jar in the modular 
>> build), we could create another jar, perhaps called namespace-compat-dl.jar?
>> 
>> Something like this would be required regardless of the build 
>> environment, but to avoid conflicts with existing deployed codebases, 
>> jsk-dl.jar should also be renamed.
>> 
>> Thoughts?
>> 
>> Peter.
> 
> I would think that one would deploy the appropriate downloadable jars
> with their service.  Perhaps I'm missing something, but I don't see a
> problem.  If a client is running and you deploy a new version of the
> service (with associated downloadable jars), the old proxy should fail,
> the client downloads a new proxy and continues on.  That's the Jini way.
> 
> Or do I misunderstand the question?
> 
> 
> Cheers,
> 
> Greg.
> -- 
> Greg Trasuk, President
> StratusCom Manufacturing Systems Inc. - We use information technology to
> solve business problems on your plant floor.
> http://stratuscom.com
> 

Mime
View raw message