Siddharth Naik

What are some of the best options for organizing packages in a J2EE application?

I did some googling to find the answer but most of the pages talked about over all directory structure of J2EE applications and not how specific packages within src directory should be organized. Here are a few options I am aware of based on my work experience at a few organizations.

----------------------------------------------------------------------------------------

Option 1: organize based on technical artifacts

com.mycompany.bo (includes files like: Customer.java, CreaditCard.java, Account.java, Promotion.java)
com.mycompany.services (includes files like: UserManaer.java, Authorization.java, Accounting.java, DiscountManager.java)
com.mycompany.actions (includes files like: Login.java, Authorize.java, AccountLookup.java, CalculateDiscount.java)
com.mycompany.dto
com.mycompany.assemblers

Pros: intuitive package structure; I know how the code would look like in each package
Cons: If I am debugging a business issue then it's hard to find out which packages might be involved

----------------------------------------------------------------------------------------

Option 2: organize based on business concerns

com.mycompany.customer (includes files like: Customer.java,UserManaer.java,LoginAction.java)
com.mycompany.payment (includes files like: CreaditCard.java, Authorization.java,Authorize.java)
com.mycompany.account (includes files like: Account.java,Accounting.java,AccountLookupAction.java)
com.mycompany.promotion (includes files like: Promotion.java,DiscountManager.java,CalculateDiscount.java)

Pros: everything related to customer is in one package so it's easy to figure out business dependency
Cons: My technical artifacts are divided across packages and I don't know what each file might contain without opening it

----------------------------------------------------------------------------------------

Option 3: Organize based on both - the business concerns and the technical artifacts

com.mycompany.beans.customer
com.mycompany.services.customer
com.mycompany.actions.customer
com.mycompany.beans.account
com.mycompany.services.accounts
com.mycompany.actions.accounts
...
...


Pros: clear separation both business wise and tech wise
Cons: too many packages and sometimes only one file in each package


How's it organized at your company and how do you like it? What would you recommend as the best option?

Thanks,
Sid

Hi,
I'm trying to create a wsdl from a simple java interface using Maven2 plugin axis2-java2wsdl. I get the following IOException. Any ideas?

D:\Projects\crm>mvn axis2-java2wsdl:java2wsdl -e + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Building crm [INFO] task-segment: [axis2-java2wsdl:java2wsdl] [INFO] ------------------------------------------------------------------------ [WARNING] While downloading jaf:activation:1.0.2 This artifact has been relocated to javax.activation:activation:1.0.2. [INFO] [axis2-java2wsdl:java2wsdl {execution: default-cli}] java.lang.Exception: java.io.IOException: The filename, directory name, or volume label syntax is incorrect at org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.resolveOutputStream(Java2WSDLCodegenEngine.java:93) at org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.<init>(Java2WSDLCodegenEngine.java:47) at org.apache.axis2.maven2.java2wsdl.Java2WSDLMojo.execute(Java2WSDLMojo.java:146) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.io.IOException: The filename, directory name, or volume label syntax is incorrect at java.io.WinNTFileSystem.createFileExclusively(Native Method) at java.io.File.createNewFile(File.java:850) at org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.resolveOutputStream(Java2WSDLCodegenEngine.java:89) ... 21 more [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] java.io.IOException: The filename, directory name, or volume label syntax is incorrect [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: java.io.IOException: The filename, directory name, or volume lab el syntax is incorrect at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: java.io.IOException: The filename, directory name, or volume label syntax is incorrect at org.apache.axis2.maven2.java2wsdl.Java2WSDLMojo.execute(Java2WSDLMojo.java:149) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more Caused by: java.lang.Exception: java.io.IOException: The filename, directory name, or volume label syntax is incorrect at org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.resolveOutputStream(Java2WSDLCodegenEngine.java:93) at org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.<init>(Java2WSDLCodegenEngine.java:47) at org.apache.axis2.maven2.java2wsdl.Java2WSDLMojo.execute(Java2WSDLMojo.java:146) ... 19 more Caused by: java.io.IOException: The filename, directory name, or volume label syntax is incorrect at java.io.WinNTFileSystem.createFileExclusively(Native Method) at java.io.File.createNewFile(File.java:850) at org.apache.ws.java2wsdl.Java2WSDLCodegenEngine.resolveOutputStream(Java2WSDLCodegenEngine.java:89) ... 21 more [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6 seconds [INFO] Finished at: Fri Jan 22 10:14:22 EST 2010 [INFO] Final Memory: 4M/9M [INFO] ------------------------------------------------------------------------

Here is the POM file.

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.se</groupId> <artifactId>crm</artifactId> <packaging>jar</packaging> <version>1.0-SNAPSHOT</version> <name>crm</name> <url>http://maven.apache.org</url> <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>3.8.1</version> <scope>test</scope> </dependency> <dependency> <groupId>axis</groupId> <artifactId>axis</artifactId> <version>1.4</version> </dependency> <dependency> <groupId>org.apache.axis</groupId> <artifactId>axis-jaxrpc</artifactId> <version>1.4</version> </dependency> <dependency> <groupId>axis</groupId> <artifactId>axis-wsdl4j</artifactId> <version>1.5.1</version> </dependency> <dependency> <groupId>commons-discovery</groupId> <artifactId>commons-discovery</artifactId> <version>0.4</version> </dependency> <dependency> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> <version>1.1.1</version> </dependency> <dependency> <groupId>org.apache.axis</groupId> <artifactId>axis-saaj</artifactId> <version>1.4</version> </dependency> <dependency> <groupId>jaf</groupId> <artifactId>activation</artifactId> <version>1.0.2</version> </dependency> <dependency> <groupId>geronimo</groupId> <artifactId>geronimo-activation</artifactId> <version>1.1.1</version> </dependency> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>1.2.8</version> </dependency> <dependency> <groupId>org.apache.geronimo.specs</groupId> <artifactId>geronimo-javamail_1.4_spec</artifactId> <version>1.6</version> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.apache.axis2.maven2</groupId> <artifactId>axis2-java2wsdl-maven-plugin</artifactId> <configuration> <className>com.se.crm.Contact</className> </configuration> <executions> <execution> <goals> <goal>java2wsdl</goal> </goals> </execution> </executions> </plugin> </plugins> </build> </project>


Here is a simple java interface.

package com.se.crm; public interface Contact { public String getContact(int contactId); }


Any help is appreciated.

Thanks,
Sid

I have Spring In Action (Manning Publications) and love it! It provides good conceptual understanding and code examples to work with.

Any recommendations on a good freeware Eclipse plugin for HTML development? It would be nice if it can show browser view - at least for plain HTML. Support for CSS, Java Script will also be helpful.

I searched http://www.eclipseplugincentral.com and found 118 solutions. So I'd like to learn from your experiences.
[ December 17, 2008: Message edited by: Siddharth Naik ]

If you have copy-pasted the code then there is typo in both cases:

(1) In the first case timeout is spelled wrong
<session-timoeout>1</session-timoeout>


(2) In the second case "m" in max needs to be capital
session.setmaxInactiveInterval(60);
[ July 14, 2008: Message edited by: Siddharth Naik ]

html select tag has all attributes you have used in the code above. Please refer to Taglib Doc.

http://struts.apache.org/1.x/struts-taglib/tlddoc/index.html

You will also find an example in this discussion:

https://coderanch.com/t/59022/Struts/decreasing-width-drop-down-box

Sounds like your problem is related to the following thread:

https://coderanch.com/t/58954/Struts/TILES-include-action-as-body

In the above-mentioned thread, action is used as body in a tiles definition. This way tiles will always call an action first to render JSP. You can define the variable and get required value in action to arrive at desired JSP dynamically.

You might be able to use attribute styleClass of struts html:select tag. This styleClass is similar to class attribute in html select tag and can be customized in CSS file.

For example in CSS you can use code like this:

SELECT.FormBox50 { width:50px; font-size: 100%; line-height:normal; margin: 0px; padding: 0px; height:19; font-family: Arial, Helvetica, sans-serif; color: #333333; background-color: #DDDDDD; font-weight: bold; font-style: normal; border-top:1px solid #cccccc ; border-right:1px solid #999999 ; border-bottom:1px solid #999999; border-left: 1px solid #cccccc; }

You can then use styleClass="FormBox50" in html:select tag.

Hope this works out for you.

java:comp/env is the standard J2EE prefix used to lookup resources via JNDI.

There is a link to one free book on Struts Category FAQ:

http://www.infoq.com/minibooks/starting-struts2

(1) Put JDBC driver to appropriate server directory. For Tomcat put it under: Tomcat/commons/lib directory

(2) Create context.xml under META-INF directory of your project with following code. Replace values specific to your environment including driverClassName of your database.

<Context path="/myapplicationroot"> <Resource name="jdbc/mydatabasename" auth="Container" type="javax.sql.DataSource" driverClassName="com.mysql.jdbc.Driver" username="myusername" password="mypassword" url="jdbc:mysql://localhost:3306/mydatabasename"/> </Context>

You can also add other parameters like maxActive, maxWait etc. Do google search for context.xml and you will find details.

(3) Use the following code for JNDI lookup

Context initCtx = new InitialContext(); DataSource ds = (DataSource)initCtx.lookup("java:comp/env/jdbc/mydatbasename"); Connection conn = ds.getConnection();

Use conn object from above code for creating Statement or preferably PreparedStatement to execute the query.
[ July 07, 2008: Message edited by: Siddharth Naik ]

Because URL rewriting doesn't use client side cookies.

[ July 07, 2008: Message edited by: Siddharth Naik ]
[ July 07, 2008: Message edited by: Siddharth Naik ]

Please see Struts category FAQs:

http://faq.javaranch.com/java/StrutsFaq#learning

URL rewriting is used while sending response and not while setting session attributes. So set and get session attributes as usual and call encodeURL method on response object.

response.encodeURL("/NextServlet.do");

Oh and don't forget to register your listener in web.xml

<listener> <listener-class> sys.MyContextListener </listener-class> </listener>