For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 4 replies, 2 voices, and was last updated 15 years, 2 months ago by
.
-
Posts
-
In case we need to generate binding files or override the existing binding files, there is an option in Websphere console to do so. How can this be achieved using MyEclipse?
We are using MyEclipse Blue 8.6.1 and WAS 6.0.2.42
Parag,
Some binding files are generated if you are using XDoclet with EJB 2.1, though otherwise we don’t have support for generating these in MyEclipse nor do we have special editors for the same. Could you tell me which binding files you are interested in? I will file an enhancement request accordingly.
Thanks for asking,
In case of RAD, for every ejb-jar.xml, the following 2 files are created: ibm_ejbext.properties and ibm-ejb-jar-bnd.xmi. In case we deploy a normal EAR on Websphere, we check a checkbox “Generate Default Binding” in the admin console in order to generate these files. Is there a way to select these options when we are deploying the application using MyEclipse.
Parag,
These files should be generated automatically on deployment with Blue – they will not be in your workspace, but in the deployed location in your WebSphere profile folder. Are you not noticing them?Brian,
We added our ear using “Add Deployment” feature through my eclipse. As suggested by it should generate the bindings file “ibm-ejb-jar-bnd.xmi”.However it failed with the following validation error and failed the deployment. Could you please let us know if there is some configuration that we need to do to have my eclipse blue generate these bindings file.
WASX7017E: Exception received while running file “C:\Genuitec\Common\plugins\com.genuitec.eclipse.blue.websphere7_8.6.1.me201011161536\installEAR.jacl”; exception information: com.ibm.ws.scripting.ScriptingException: WASX7109E: Insufficient data for install task “BindJndiForEJBNonMessageBinding
ADMA0002E: A validation error occurred in task Binding enterprise Bean to JNDI names. The Java Naming and Directory Interface (JNDI) name is not specified for enterprise bean LaunchPadEJB in module Erapids.
ADMA0002E: A validation error occurred in task Binding enterprise Bean to JNDI names. The Java Naming and Directory Interface (JNDI) name is not specified for enterprise bean HelpScreenEJB in module Erapids.
