This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line!
See this thread for details.
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

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

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

Gary Dux

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"?>

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");

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=""
urn:iiop jboss-ejb-iiop_1_0.xsd"


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 would be in this case?

I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link:
subject: Jboss5.1 Migration to JBoss7.1 Custom-JNDI-Handling
It's not a secret anymore!