aspose file tools*
The moose likes JBoss/WildFly and the fly likes Jboss5.1 Migration to JBoss7.1 Custom-JNDI-Handling 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 "Jboss5.1 Migration to JBoss7.1 Custom-JNDI-Handling" Watch "Jboss5.1 Migration to JBoss7.1 Custom-JNDI-Handling" New topic
Author

Jboss5.1 Migration to JBoss7.1 Custom-JNDI-Handling

Gary Dux
Greenhorn

Joined: Aug 14, 2008
Posts: 5
Hello together,

in our applications we used to define jndi-mappings in jboss.xml:
<?xml version="1.0" encoding="UTF-8"?>
<jboss>
<enterprise-beans>
<session>
<ejb-name>ContractPortfolioProcessServiceBean</ejb-name>
<jndi-name>com/fja/ipl/customer/ilis/contractportfolio/ContractPortfolioProcessService</jndi-name>
</session>
</enterprise-beans>
</jboss>

ithis jboss.xml was placed then in META-INF of that ejb-jar

So it was easy to lookup for that bean like:

public static ContractPortfolioProcessService lookupContractPortfolioProcessService()
throws NamingException {
final Context context = new InitialContext();
return (ContractPortfolioProcessService ) context.lookup("com/fja/ipl/customer/ilis/contractportfolio/ContractPortfolioProcessService");
}
jndi.properties{
#JBoss
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=jnp://localhost:1099
java.naming.factory.url.pkgs=org.jboss.namingrg.jnp.interfaces
}

How can it be made on JBOSS7?

Due ejb3-spec in JBOSS7 they can also define jboss-ejb3.xml like this:
<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:iiop="urn:iiop"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd
urn:iiop jboss-ejb-iiop_1_0.xsd"
version="3.1"
impl-version="2.0">
<enterprise-beans>
<session>
<ejb-name>CounterBean</ejb-name>
<mapped-name>org/jboss/as/quickstarts/ejb/remote/stateful/CounterBean</mapped-name>
</session>
</enterprise-beans>

<assembly-descriptor>
<iiop:iiop>
<ejb-name>CounterBean</ejb-name>
<iiop:binding-name>org/jboss/as/quickstarts/ejb/remote/stateful/CounterBean</iiop:binding-name>
</iiop:iiop>
</assembly-descriptor>
</jboss:ejb-jar>

It deploys also errorless. But i did not find any dokumentation to lookup my ejb like in example above.

Who can help me giving a hint in this case?

How is the jndi.properties-Configuration would be in this case?




 
Don't get me started about those stupid light bulbs.
 
subject: Jboss5.1 Migration to JBoss7.1 Custom-JNDI-Handling