- This topic has 3 replies, 3 voices, and was last updated 16 years, 9 months ago by
Riyad Kalla.
-
AuthorPosts
-
Matthew MacMillanParticipantHi All,
I am new to blue so bear with me.
Here is the issue: I am moving over from RAD 7 to MyEclipse Blue (have already purchased the license). I have all my projects built and all is well so far. I am looking for how to generate the stubs and ties in MyEclipse Blue but don’t see a right click menu option for generating deployment using RMIC.
Anyone know how I generate these. I have pasted my deployment log below just in case it is a different issue.
Replies are very much appreciated.
———————————————————————————————————————-
MyEclipse: deployment START explodedproject: ResolverEAR server: websphere61Server time: Sun Apr 27 16:50:46 EDT 2008
———————————————————————————————————————-
WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: “[C:\\WAS\\AppServer\\profiles\\AppSrv01\\installableApps\\ResolverEAR.ear, mmacmillanpcNode01Cell, mmacmillanpcNode01, server1, ResolverEAR, {{“ResolverWeb.war” “ResolverWeb.war,WEB-INF/web.xml” default_host}}, {{“null” “ResolverWeb.war,WEB-INF/ibm-web-ext.xmi”AppDeploymentOption.Yes 1}}, false, true, true, C:/WebExpress/MyEclipseBlue/myeclipse/eclipse/plugins/com.genuitec.eclipse.blue.websphere_6.1.0.zmyeclipse610200803/scriptutil/scriptutil.jar, C:/WAS/AppServer/profiles/AppSrv01/installedApps/mmacmillanpcNode01Cell/ResolverEAR.ear/ResolverEJB.jar]”
C:\WAS\AppServer\profiles\AppSrv01\installableApps\ResolverEAR.ear
mmacmillanpcNode01Cell
mmacmillanpcNode01
server1
ResolverEAR
{“ResolverWeb.war” “ResolverWeb.war,WEB-INF/web.xml” default_host}
{“null” “ResolverWeb.war,WEB-INF/ibm-web-ext.xmi”AppDeploymentOption.Yes 1}
-nopreCompileJSPs -distributeApp -useMetaDataFromBinary -deployejb -appname “ResolverEAR” -createMBeansForResources -reloadEnabled -reloadInterval 1 -deployws -validateinstall off -noprocessEmbeddedConfig -filepermission .*.dll=755#.*.so=755#.*.a=755#.*.sl=755 -buildVersion Unknown -noallowDispatchRemoteInclude -noallowServiceRemoteInclude -MapWebModToVH {{“ResolverWeb.war” “ResolverWeb.war,WEB-INF/web.xml” default_host}} -JSPReloadForWebMod {{“null” “ResolverWeb.war,WEB-INF/ibm-web-ext.xmi”AppDeploymentOption.Yes 1}}
false
true
true
C:/WebExpress/MyEclipseBlue/myeclipse/eclipse/plugins/com.genuitec.eclipse.blue.websphere_6.1.0.zmyeclipse610200803/scriptutil/scriptutil.jar
C:/WAS/AppServer/profiles/AppSrv01/installedApps/mmacmillanpcNode01Cell/ResolverEAR.ear/ResolverEJB.jar
-deployejb
WASX7017E: Exception received while running file “C:/WebExpress/MyEclipseBlue/myeclipse/eclipse/plugins/com.genuitec.eclipse.blue.websphere61_6.1.0.zmyeclipse610200803/installEAR.jacl”; exception information: com.ibm.ws.scripting.ScriptingException: WASX7109E: Insufficient data for install task “BindJndiForEJBNonMessageBindingADMA0002E: 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 com_checkfree_resolver_TransactionExceptionSessionHome in module ResolverEJB.jar.
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 com_checkfree_resolver_UserFieldsSessionHome in module ResolverEJB.jar.
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 com_checkfree_resolver_DataAcquisitionServiceSessionHome in module ResolverEJB.jar.
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 com_checkfree_resolver_DataExtractionServiceSessionHome in module ResolverEJB.jar.
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 com_checkfree_resolver_DataRetrievalServiceSessionHome in module ResolverEJB.jar.
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 com_checkfree_resolver_DecisionSessionHome in module ResolverEJB.jar.
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 com_checkfree_resolver_UOWSessionHome in module ResolverEJB.jar.”Thanks!!
Matt
Loyal WaterMemberMatt,
Can have you taken a look at these quickstart docs:-
http://www.myeclipseide.com/documentation/quickstarts/blueedition/blue_connectors/
http://www.myeclipseide.com/documentation/quickstarts/blueedition/blue_rad_overview/
Matthew MacMillanParticipantI have already read those. They do not explain the replacement for generating stubs and ties and even generating the ibm-ejb-jar-bnd.xmi, ibm-web-bnd.xmi, and ejb-jar.xml files.
Do I have to use RAD to generate these and then copy them over to MyEclipse blue? Doesn’t that kinda defeat the purpose?
Thanks,
Matt
Riyad KallaMemberMatt,
First let me thank you for the support (of MyEclipse Blue). Right now the descriptor generation you are asking about needs to be handled by XDoclet and is something we are considering for a future release of Blue (But it won’t be in the upcoming 6.5 release which is due at the beginning of June). -
AuthorPosts