File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Servlets and the fly likes webapps/package naming and path convention Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Servlets
Bookmark "webapps/package naming and path convention" Watch "webapps/package naming and path convention" New topic
Author

webapps/package naming and path convention

Angus Comber
Ranch Hand

Joined: Jul 16, 2011
Posts: 90
I just can't get started writing my servlet... because I can't think of what to call it

But seriously, I want to get the naming right up-front.

For the sake of an example, my url is inspiredgarden.com and I want to develop a product called Garden Designer which allows someone to design their garden layout on-screen.


Let me know if you think this sounds like a good package name and webapps naming convention.

In Tomcat_root/webapps I create my webapps name which is GardenDesigner.

My package path is:

com.inspiredgarden.gardendesigner

I am a bit concerned that I have GardenDesigner - with mixed case and also gardendesigner (all lowercase) in the package name. Should I use different names here or do something different? Any suggestions?

I might later on bring out a different design type package, eg industrialdesigner, so need the 3 level package name.
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 61608
    
  67

Angus Comber wrote:For the sake of an example, my url is inspiredgarden.com

Terminology first: that's your domain, not the URL. A URL is the full path to a resource.

and I want to develop a product called Garden Designer which allows someone to design their garden layout on-screen.

Sounds cool, and something I'd like to use.

I am a bit concerned that I have GardenDesigner - with mixed case and also gardendesigner (all lowercase) in the package name.

As package names aren't visible to anyone but the developer there s no problem whatsoever. I do not recommend using anything but lowercase for package names.

Should I use different names here or do something different?

Seems fine to me.


[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: webapps/package naming and path convention