It's not a secret anymore!*
The moose likes JBoss/WildFly and the fly likes Incomplete Deployment Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "Incomplete Deployment" Watch "Incomplete Deployment" New topic
Author

Incomplete Deployment

Abhijith Prabhakar
Ranch Hand

Joined: Dec 29, 2006
Posts: 56
Hi,

I am trying to run the example codes of Oreilly EJB 3.0 book. When I deploy my ejb3mockproject.jar in JBOSS, it gives this message.



Persistence.xml:



Can anyone please tell me what I need to do to solve this?
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10210
    
166

<jta-data-source>java: /DefaultDS</jta-data-source>


There's a space between java: and the /. Remove that space and start JBoss. This entry should look like:



[My Blog] [JavaRanch Journal]
Abhijith Prabhakar
Ranch Hand

Joined: Dec 29, 2006
Posts: 56
Thanks Jai, that solved the deployment issue.

But after been deployed also it was giving NotBoundException for TavelAgentRemote. It started working when I added

@org.jboss.annotation.ejb.RemoteBinding(jndiBinding = "TravelAgentRemote")

Any specific reason behind this? I am curious as Oreilly book doesn't state any such annotation to be added
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10210
    
166

Originally posted by Abhijith Prabhakar:
Any specific reason behind this? I am curious as Oreilly book doesn't state any such annotation to be added


By default, if you are deploying the bean in an ear file, then JBoss binds the beans to a jndi-name which is like "earName/BeanImplementationClassName/remote" (for local it is earName/BeanImplementationClassName/local). Ex: myApp/TestBean/remote. If you are deploying the bean in a jar file then the default jndi-name is BeanImplementationClassName/remote (and BeanImplementationClassName/local for local interface). Ex: TestBean/remote.

You can use these default jndi-names to do the lookup or else specify your own jndi-names for the beans. You followed the latter approach by using the @RemoteBinding annotation
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Incomplete Deployment