vijay r ha scritto:
That's fine. I know why packages are for. But why is it necessary to create packages to keep our ActionForm classes, Action classes. Name collision is the problem which the development team has to tackle. What if the development team decides to name classes starting with their Employee ID, probability of name collision decreases considerably. Is it strictly enforced by Struts to use packages.
In my experience I had sometimes tried to write some servlet-based applications with classes with no packages, just to make a test and without using Struts. It may seem strange but I got a lot of strange errors, such as classes not found. When I modified the code simply adding a package everything went fine. But the question is: why don't you want to use packages? I think it is a Java convention since 1.0 that you have to name your packages reversing your domain URL (com.hello.etc.). I think that not using packages is only a question of lazyness.
Ciao Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
