[Gusdev-gusdev] Re: the nasty java package question

[Adrian R. T. <ar...@sa...>]

As probably the third largest sponsor of Java, I guess Oracle are allowed to
break the rules sometimes!

The only place it really makes a difference is in imports, ie not very often.
(When I come across packages that don't obey the JLS package naming rules it
always rings a little alarm bell in the back of my head.) For the sake of 4
letters I'd keep the org. 

A related question - why org.gusdev rather than org.gusdb?


> folks-
> 
> i am gearing up to right my first WDK java code (xml parser using 
> digester).  this is also my first java code for GUS.
> 
> and so, i am confronted with the nasty package name question.
> 
> officially, this is kind of what i think the package name should be, 
> but, its so darn long:
>    org.gusdev.gus.wdk.model.config.Parser;
> 
> ie, organization_type.organization.project.component.subcomponent.package
> 
> note that while we don't yet, we do expect to have other projects, such 
> as rad, be under the gusdev umbrella.

But presumably the web interface will want to talk to rad etc. Will there be a
org.gusdev.rad.wdk... etc or something else?

Adrian

> 
> i did a quick surf to see if others are having this problem.  here is 
> the first package name i stumbled on:
> 
> oracle.security.rdbms.server.AppCtx.AppCtxManager
> 
> I suppose we could drop the leading org:
> 
>   gusdev.gus.wdk.model.config.Parser
> 
> any ideas?
>