We are using eclipse version 3.4.0 for EJB 2.0 application development ( which has ready plug-in for jboss server 4.2.1GA) and jboss server 4.2.1GA for the deployment. and Jboss is configured for database MS SQLSERVER 2005 which is working fine. we migrated the application from weblogic 9.1 to the Jboss.
During the deployment some of the entityJNDI were not getting bonded with the server if the entity bean is local, when we change the entity bean into remote it is getting bonded with the server. Is it a real problem with JBOSS 4.2 or are we going wrong somewhere?
Please provide your valuable suggestions regarding this issue.
1) I am not sure what you are asking here. Could you provide a specific example, showing configuration file and code excerpts?
2) For a web app you could place the JSTL-related jar files in WEB-INF/lib. JBossAS does not provide the standard JSTL taglib jars - you have to provide them yourself. BossAS does, however, provide the JSF taglibs.
this issue has been resolved somehow.....even i couldnt able to figure out what was wrong...later stage i disabled the EJB2.x spec. verification by commenting attribute in ejb-deployer.xml. things are working smoothly now......