You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Tom Hobbs <to...@sucfin.com> on 2010/01/06 10:45:51 UTC
Namespace Considerations (Was: RE: Apache River Release)
Hi Greg,
In regards to;
"I hope there's no intention of changing the net.jini.** package
namespaces to org.apache.**."
I was under the impression that it /was/ the intention to change all the
Jini/River code to be under the org.apache namespace. I also thought
that doing so was a requirement for the eventual promotion of River out
of the incubator.
I know that this would break third party code (my own included) but I
personally feel that it's a desirable step that should be taken.
Am I rehashing an old discussion here that has already been decided?
Cheers,
Tom
-----Original Message-----
From: Greg Trasuk [mailto:trasukg@stratuscom.com]
Sent: 05 January 2010 17:46
To: river-dev@incubator.apache.org
Subject: RE: Apache River Release
On Tue, 2010-01-05 at 12:15, Tom Hobbs wrote:
> I figured most of the core information is the same, so all I've done
is
> a bit of tidying up..
>
> - Replaced all* references to "Jini" with "River"
Perhaps I'm wrong, but isn't it still Jini? As in "the Jini dynamic
networking infrastructure". I've always understood that River was the
project name for the reference implementation, in the same way that
Tomcat is the name of an implementation of the servlet specification.
More specifically, I hope there's no intention of changing the
net.jini.** package namespaces to org.apache.**. com.sun.jini is fair
game, but changes away from net.jini will break existing code, across a
couple of vendors, I suspect.
Cheers,
Greg.
--
Greg Trasuk, President
StratusCom Manufacturing Systems Inc. - We use information technology to
solve business problems on your plant floor.
http://stratuscom.com
www.sucdenfinancial.com
Sucden Financial Limited, Plantation Place South, 60 Great Tower Street, London EC3R 5AZ
Telephone +44 203 207 5000
Registered in England no. 1095841
VAT registration no. GB 446 9061 33
Authorised and Regulated by the Financial Services Authority (FSA) and entered in the FSA register under no. 114239
This email, including any files transmitted with it, is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you are not the intended recipient of this message, please notify postmaster@sucfin.com immediately and delete it from your computer system.
We believe, but do not warrant, that this email and its attachments are virus-free, but you should check.
Sucden Financial Limited may monitor traffic data of both business and personal emails. By replying to this email, you consent to Sucden Financial 's monitoring the content of any emails you send to or receive from Sucden Financial . Sucden Financial is not liable for any opinions expressed by the sender where this is a non-business email.
The contents of this e-mail do not constitute advice and should not be regarded as a recommendation to buy, sell or otherwise deal with any particular investment.
This message has been scanned for viruses by Mimecast.
RE: Namespace Considerations (Was: RE: Apache River Release)
Posted by Tom Hobbs <to...@sucfin.com>.
Thanks guys, I stand corrected.
Cheers.
-----Original Message-----
From: Jonathan Costers [mailto:jonathan.costers@googlemail.com]
Sent: 06 January 2010 13:04
To: river-dev@incubator.apache.org
Subject: Re: Namespace Considerations (Was: RE: Apache River Release)
IIRC, the community has decided before that the public interface
net.jini.*
would remain unchanged.
It is only the com.sun.jini.* namespace that would migrate to
org.apache.river.* instead.
So we would only change the namespace for the implementation of the Jini
spec, not for the spec itself.
Hope this makes sense
Jonathan
2010/1/6 Dennis Reedy <de...@gmail.com>
>
> On Jan 6, 2010, at 445AM, Tom Hobbs wrote:
>
> > Hi Greg,
> >
> > In regards to;
> >
> > "I hope there's no intention of changing the net.jini.** package
> > namespaces to org.apache.**."
> >
> > I was under the impression that it /was/ the intention to change all
the
> > Jini/River code to be under the org.apache namespace.
>
> AFAIK this is not the intention at all. The com.sun namespace is to be
> changed not the net.jini namespace.
>
>
www.sucdenfinancial.com
Sucden Financial Limited, Plantation Place South, 60 Great Tower Street, London EC3R 5AZ
Telephone +44 203 207 5000
Registered in England no. 1095841
VAT registration no. GB 446 9061 33
Authorised and Regulated by the Financial Services Authority (FSA) and entered in the FSA register under no. 114239
This email, including any files transmitted with it, is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you are not the intended recipient of this message, please notify postmaster@sucfin.com immediately and delete it from your computer system.
We believe, but do not warrant, that this email and its attachments are virus-free, but you should check.
Sucden Financial Limited may monitor traffic data of both business and personal emails. By replying to this email, you consent to Sucden Financial 's monitoring the content of any emails you send to or receive from Sucden Financial . Sucden Financial is not liable for any opinions expressed by the sender where this is a non-business email.
The contents of this e-mail do not constitute advice and should not be regarded as a recommendation to buy, sell or otherwise deal with any particular investment.
This message has been scanned for viruses by Mimecast.
Re: Namespace Considerations (Was: RE: Apache River Release)
Posted by Jonathan Costers <jo...@googlemail.com>.
IIRC, the community has decided before that the public interface net.jini.*
would remain unchanged.
It is only the com.sun.jini.* namespace that would migrate to
org.apache.river.* instead.
So we would only change the namespace for the implementation of the Jini
spec, not for the spec itself.
Hope this makes sense
Jonathan
2010/1/6 Dennis Reedy <de...@gmail.com>
>
> On Jan 6, 2010, at 445AM, Tom Hobbs wrote:
>
> > Hi Greg,
> >
> > In regards to;
> >
> > "I hope there's no intention of changing the net.jini.** package
> > namespaces to org.apache.**."
> >
> > I was under the impression that it /was/ the intention to change all the
> > Jini/River code to be under the org.apache namespace.
>
> AFAIK this is not the intention at all. The com.sun namespace is to be
> changed not the net.jini namespace.
>
>
Re: Namespace Considerations (Was: RE: Apache River Release)
Posted by Dennis Reedy <de...@gmail.com>.
On Jan 6, 2010, at 445AM, Tom Hobbs wrote:
> Hi Greg,
>
> In regards to;
>
> "I hope there's no intention of changing the net.jini.** package
> namespaces to org.apache.**."
>
> I was under the impression that it /was/ the intention to change all the
> Jini/River code to be under the org.apache namespace.
AFAIK this is not the intention at all. The com.sun namespace is to be changed not the net.jini namespace.
Re: Namespace Considerations (Was: RE: Apache River Release)
Posted by Craig L Russell <Cr...@Sun.COM>.
There's no rule that 100% of the code in Apache projects must be in
the org.apache name space.
But the exceptions to date have been few. Those that I'm aware of are
in the javax name space that is mandated by external specifications.
For example, the Geronimo project ships code in the javax.ejb name
space, and the JDO project ships code in the javax.jdo name space.
I don't know whether net.jini falls into the category of "external
specifications" that would justify preserving the name space.
Cheers,
Craig
On Jan 6, 2010, at 1:45 AM, Tom Hobbs wrote:
> Hi Greg,
>
> In regards to;
>
> "I hope there's no intention of changing the net.jini.** package
> namespaces to org.apache.**."
>
> I was under the impression that it /was/ the intention to change all
> the
> Jini/River code to be under the org.apache namespace. I also thought
> that doing so was a requirement for the eventual promotion of River
> out
> of the incubator.
>
> I know that this would break third party code (my own included) but I
> personally feel that it's a desirable step that should be taken.
>
> Am I rehashing an old discussion here that has already been decided?
>
> Cheers,
>
> Tom
>
> -----Original Message-----
> From: Greg Trasuk [mailto:trasukg@stratuscom.com]
> Sent: 05 January 2010 17:46
> To: river-dev@incubator.apache.org
> Subject: RE: Apache River Release
>
>
> On Tue, 2010-01-05 at 12:15, Tom Hobbs wrote:
>> I figured most of the core information is the same, so all I've done
> is
>> a bit of tidying up..
>>
>> - Replaced all* references to "Jini" with "River"
>
> Perhaps I'm wrong, but isn't it still Jini? As in "the Jini dynamic
> networking infrastructure". I've always understood that River was the
> project name for the reference implementation, in the same way that
> Tomcat is the name of an implementation of the servlet specification.
>
> More specifically, I hope there's no intention of changing the
> net.jini.** package namespaces to org.apache.**. com.sun.jini is fair
> game, but changes away from net.jini will break existing code,
> across a
> couple of vendors, I suspect.
>
> Cheers,
>
> Greg.
>
>
> --
> Greg Trasuk, President
> StratusCom Manufacturing Systems Inc. - We use information
> technology to
> solve business problems on your plant floor.
> http://stratuscom.com
>
> www.sucdenfinancial.com
>
> Sucden Financial Limited, Plantation Place South, 60 Great Tower
> Street, London EC3R 5AZ
> Telephone +44 203 207 5000
>
> Registered in England no. 1095841
> VAT registration no. GB 446 9061 33
>
> Authorised and Regulated by the Financial Services Authority (FSA)
> and entered in the FSA register under no. 114239
>
> This email, including any files transmitted with it, is confidential
> and may be privileged. It may be read, copied and used only by the
> intended recipient. If you are not the intended recipient of this
> message, please notify postmaster@sucfin.com immediately and delete
> it from your computer system.
>
> We believe, but do not warrant, that this email and its attachments
> are virus-free, but you should check.
>
> Sucden Financial Limited may monitor traffic data of both business
> and personal emails. By replying to this email, you consent to
> Sucden Financial 's monitoring the content of any emails you send to
> or receive from Sucden Financial . Sucden Financial is not liable
> for any opinions expressed by the sender where this is a non-
> business email.
>
> The contents of this e-mail do not constitute advice and should not
> be regarded as a recommendation to buy, sell or otherwise deal with
> any particular investment.
>
> This message has been scanned for viruses by Mimecast.
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!