- This topic has 5 replies, 3 voices, and was last updated 13 years, 5 months ago by
.
-
Posts
-
First post…so Hi everyone….I just upgraded from myeclipse 8.6 to 9.1 and am enjoying so far. I’m trying to make use of the In-Workspace deployment so I don’t have to keep redeploying my EJB’s, but when I select my EJB project and execute EJB Deploy from the MyEclipse context menu I get the following:
EJB deploy failed
Error while processing project PROFILE_PersistanceEJB: There were validation errors:
– CHKJ2470E: This method must return boolean (EJB 2.0: 7.10.5).
– CHKJ2470E: This method must return boolean (EJB 2.0: 7.10.7).
– CHKJ2470E: This method must return java.util.Collection (EJB 2.0: 7.10.7).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeRoleMenuBO (EJB 2.0: 7.10.5).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeRoleFunctionBO (EJB 2.0: 7.10.5).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeRoleFunctionBO (EJB 2.0: 7.10.5).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeRoleFunctionBO (EJB 2.0: 7.10.5).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeRoleFunctionBO (EJB 2.0: 7.10.7).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeRoleFunctionBO (EJB 2.0: 7.10.7).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeRoleFunctionBO (EJB 2.0: 7.10.7).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeMenuBO (EJB 2.0: 7.10.5).
– CHKJ2017E: This interface must extend javax.ejb.EJBHome (EJB 2.0: 6.3, 7.10.6).
There were validation errors:
– CHKJ2470E: This method must return boolean (EJB 2.0: 7.10.5).
– CHKJ2470E: This method must return boolean (EJB 2.0: 7.10.7).
– CHKJ2470E: This method must return java.util.Collection (EJB 2.0: 7.10.7).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeRoleMenuBO (EJB 2.0: 7.10.5).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeRoleFunctionBO (EJB 2.0: 7.10.5).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeRoleFunctionBO (EJB 2.0: 7.10.5).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeRoleFunctionBO (EJB 2.0: 7.10.5).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeRoleFunctionBO (EJB 2.0: 7.10.7).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeRoleFunctionBO (EJB 2.0: 7.10.7).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeRoleFunctionBO (EJB 2.0: 7.10.7).
– CHKJ2470E: This method must return com.checkfree.profile.bo.CompositeMenuBO (EJB 2.0: 7.10.5).
– CHKJ2017E: This interface must extend javax.ejb.EJBHome (EJB 2.0: 6.3, 7.10.6).Now…based on the above, it does not tell me which class and which method have the problem. I have done a check on all EJB’s that have methods that return boolean in the interfaces (Remote’s and/or Local’s) and they all jive just great.
Any suggestions on how to dive deeper? I don’t know where else to look.
thunderman74 ,
Sorry that you are seeing this issue with MyEclipse.
Can you answer some more questions for me?
1) Can you check if the regular Classic/Enhanced mode of deployment works fine ?
2) WAS 6.1 does not support Java 5 natively and requires additional feature packs for JEE 5 support – do you have these installed? Else you may need to go back to using Java 1.4. I suggest using the JDK that comes with Websphere.
3) Are you able to successfully deploy your project with any other tools to this same profile?
4) Can you also send us contents of the log located at ${Workspace}\.metadata\.plugins\com.genuitec.eclipse.blue.ejbdeploy \was61\workspace\.metadata\.log (WAS61 or WAS6 for WAS 6.1 server) for further investigation ?
I took a project that deploys just fine in classic and exploded on MyEclipse 8.6 and brought it up in MyEclipse 9.1.
I then allowed it to convert my projects to 9.1 via the prompter. I then deployed via classic and it worked fine. I then removed that deployment and deployed via exploded and it did not work. With exploded I opened the directory where it deploys it (F:\WebSphere\AppServer\profiles\AppSrv01\installedApps\mmacmillanpcNode01Cell) and watched the directory while the exploded deploy was occurring. I saw it create the EAR directory….and then at the end (before the exploding process), I saw the directory get removed. Then the console said it was exploding and that it exploded just fine, but there was no EAR directory (very weird)…then I tried to start the server and it said it could not fine the EAR directory. Don’t know why the directory was removed before the explode part of the exploded deploy.
Now…The classic deployed just fine and ran just fine as well, but when I try to do the DeployEJB from the MyEclipse context menu of my EJB project I still get the errors that I listed above. So the ejb deploy of the classic deployment worked fine, but the EJBDeploy from MyEclipse…did not.
The JDK that comes with Websphere 6.1 latest fixpack is JDK 5 not 1.4. So it is running with JDK 5…I am sure of that.
I did notice that I have the EJB 2.1 facet selected on the EJB project but the violations state EJB 2.0.
THanks
thunderman74,
Sorry for the delay. We’ve been trying to replicate the problem here but it takes a while to set up a similar environment to the one you have.
Could you describe your application in more detail (in terms of the projects involved and what each project type is), or send your application to us, if that is possible? If you can send a set of project but don’t want to attach them here, you can send an attachment to an email to [email protected] with Subject: “ATTN Tony” with a link to this forum topic.
Matthew,
As well as providing more details on the structure of you project, could you also confirm your operating system and version, please?
I can’t replicate the error on Windows XP (SP3), with WAS 6.1 and a project containing an EJB and a web module. I created the project on release 8.6 of Blue and opened the workspace in 9.1 Blue. It deployed and ran fine in both cases.
