struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marsh-Bourdon, Christopher" <>
Subject RE: [OT] package naming nonsense
Date Fri, 17 Jun 2005 13:02:24 GMT
I favour using org.apache.* or com.sun.*, but never*.   It
gives a certain gravitas to one's coding! ;-) 

-----Original Message-----
Sent: 17 June 2005 13:59
To: Struts Users Mailing List
Subject: Re: [OT] package naming nonsense

1. Well, no one suggested that you need to search some archive.
2. It would be difficult (if not impossible) to name an example of an
application that has a namespace collision that is publicly available.  I
hope you understand why.

Finally, naming conventions are not enforced by compilers.  Name your
packages as you wish.


Adam Hardy <>
06/17/2005 08:48 AM
Please respond to
"Struts Users Mailing List" <>

Struts Users Mailing List <>

Re: [OT] package naming nonsense

OK, silly me, I started using java with 1.2, rather than 1.0, but it's 
friday, so please don't tell me to go read the archives!!!!

I admit, in theory it's easy to say, you're using and 
so am I, a disaster in the making, but when is that going to happen? I 
challenge you to name me an example. Take eBay for example. They just 
went off and bought up all the top level domains for ebay.

What bugs me is that the low correlation between java programs and the 
top level domains.

Oh hell, I just wish I had 5 grand to buy :-(

On 17/06/05 13:17&nbsp; wrote:
> Why, just the other day, I contemplated the same thing.  In fact, I TOO 
> named my OSS package blah.blah.blah.  But wait, what would've happened 
> you and I had not only the same package structure, but also 2 classes 
> the same name e.g., and you decided to use my OSS?
> I'm guessing that you haven't been using Java very long, because the 
> of namespace collision was well discussed when 1.0 came out.  Hopefully, 

> you understand why you're suggestion is, not feasible.
> -Dennis
> Adam Hardy <> 
> 06/17/2005 07:46 AM
> Please respond to
> "Struts Users Mailing List" <>
> To
> Struts Users Mailing List <>
> cc
> Subject
> [OT] package naming nonsense
> Since it's Friday and I'm just about to start a new project, I thought 
> I'd ask everyone what they think about something that's always bugged 
> Package names in Java. Why do we all have com.blah.blah or 
> instead of just plain blah.blah.blah and 
> What really got me on my last project was changing from one organisation 

> to another, the project packages had to be renamed from to 
> com.siemans and we actually made it all the more pointless by discussing 

> whether it should be com.siemenz or de.siemenz.
> I'd love to drop the whole top-level domain but why on earth is it there 

> in the first place?
> My new project is for a charity ecoworks with the top-level domain .eu 
> and they might even purchase too, and I don't want to mess 
> around, so why can't I just have my packages like this:
> ecoworks.newsfeed.etc
> instead of eu.ecoworks or eu.ecoworks or whatever.
> And why isn't it just plain apache.struts or apache.tomcat? It's not as 
> though there's ever going to be a mix up with code like com.apache. - or 

> is there?
> And even if there is, why is the mix-up possibility so important when it 

> comes to package names, when it's not considered when it comes to jar 
> naming conventions. If there ever was a com.apache.struts, what would 
> they call their jar? Would they have to use com_struts-1.2.7.jar

To unsubscribe, e-mail:
For additional commands, e-mail:


The information contained herein is confidential and is intended solely for the
addressee. Access by any other party is unauthorised without the express 
written permission of the sender. If you are not the intended recipient, please 
contact the sender either via the company switchboard on +44 (0)20 7623 8000, or
via e-mail return. If you have received this e-mail in error or wish to read our
e-mail disclaimer statement and monitoring policy, please refer to or contact the sender. 3166

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message