aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes Separating Deployment for Home/Component Interfaces and Bean Class Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Separating Deployment for Home/Component Interfaces and Bean Class" Watch "Separating Deployment for Home/Component Interfaces and Bean Class" New topic
Author

Separating Deployment for Home/Component Interfaces and Bean Class

Stanley Walker
Ranch Hand

Joined: Sep 23, 2009
Posts: 87
Hi Everyone,

I was just wondering if it is possible to separate home/component interfaces for EJB.

Up until now, when ever I was writing an EJB i was always maintaining my bean class, home and component interface in the same project. I used to build it and deploy it as a jar file along with the deployment descriptors.
Since my client only requires references to home and component interfaces, I was just wondering if i can separate the two.
eg:
Bean class ABC in project com.org.bean.impl
and interfaces ABCEJBObject and ABCEJBHome in project com.org.bean.interface

In which case, i may only deploy com.org.bean.interface in the client environment.

question: in the case the above is possible, how do i deploy the two projects in my server?

Any help would be appreciated

thank you
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Separating Deployment for Home/Component Interfaces and Bean Class