gusdev-gusdev

[Gusdev-gusdev] the nasty java package question

[Steve F. <st...@pc...>]

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.

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?

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

[Angel P. <an...@pc...>]

my feelings about "gusdev" as the project named are thumbs down. Makes 
it look like a hack project. What about collapsing "gusdev.gus" into "gus"?

org.gus.wdk.
org.gus.db.* or org,gus.model.*
org.gus.rad.*
org.gus.dots.*
etc.

Angel

Steve Fischer wrote:

> 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.
>
> 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?

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

[Dave B. <db...@pc...>]

Right now, java classes in the GUS project have a package structure like 
the following:

org.gusdb.<componentName>.

Steve, before you said that you wanted to change this to

org.gusdb.<projectName>.<componentName>, which would make the package name 
more like the one you originally proposed.

> my feelings about "gusdev" as the project named are thumbs down. Makes 
> it look like a hack project. 

We are currently using 'gusdb' instead of 'gusdev' in the GUS build 
system, although I don't know if there's a reason for that.  'gusdb' looks 
a lot less like a hack project though.  

I don't think there's too much wrong with long package names.  Right now, 
the typical java GUS object looks like this:

org.gusdb.model.schema.tableName

and it will eventually have 'gus' in between 'gusdb' and 'model.'  And 
don't even get me started on what the Annotators Interface package 
structure looks like.

dave


> 
> org.gus.wdk.
> org.gus.db.* or org,gus.model.*
> org.gus.rad.*
> org.gus.dots.*
> etc.
> 
> Angel
> 
> Steve Fischer wrote:
> 
> > 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.
> >
> > 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?
> 
> 

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

[Steve F. <sfi...@pc...>]

oops.   i meant gusdb instead of gusdev.  

so, again:
   org_type, org, project, component, subcomponent, subsubcomponent, etc

org.gusdb.gus.wdk.model.query.QuerySet;
org.gusdb.rad.studannot.whatever.WhyNot;

steve

Dave Barkan wrote:

>Right now, java classes in the GUS project have a package structure like 
>the following:
>
>org.gusdb.<componentName>.
>
>Steve, before you said that you wanted to change this to
>
>org.gusdb.<projectName>.<componentName>, which would make the package name 
>more like the one you originally proposed.
>
>  
>
>>my feelings about "gusdev" as the project named are thumbs down. Makes 
>>it look like a hack project. 
>>    
>>
>
>We are currently using 'gusdb' instead of 'gusdev' in the GUS build 
>system, although I don't know if there's a reason for that.  'gusdb' looks 
>a lot less like a hack project though.  
>
>I don't think there's too much wrong with long package names.  Right now, 
>the typical java GUS object looks like this:
>
>org.gusdb.model.schema.tableName
>
>and it will eventually have 'gus' in between 'gusdb' and 'model.'  And 
>don't even get me started on what the Annotators Interface package 
>structure looks like.
>
>dave
>
>
>  
>
>>org.gus.wdk.
>>org.gus.db.* or org,gus.model.*
>>org.gus.rad.*
>>org.gus.dots.*
>>etc.
>>
>>Angel
>>
>>Steve Fischer wrote:
>>
>>    
>>
>>>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.
>>>
>>>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?
>>>      
>>>
>>    
>>
>
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by EclipseCon 2004
>Premiere Conference on Open Tools Development and Integration
>See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
>http://www.eclipsecon.org/osdn
>_______________________________________________
>Gusdev-gusdev mailing list
>Gus...@li...
>https://lists.sourceforge.net/lists/listinfo/gusdev-gusdev
>  
>

[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?
>