MyEclipse :: View topic - Redeploy problem on WebSphere 6.1

MyEclipse: Redeploy problem on WebSphere 6.1

striebhz - Mar 30, 2012 - 12:21 PM
Post subject: Redeploy problem on WebSphere 6.1

Hi

I'm currently evaluating MyEclipse Blue 10 (10.0.2) as a replacement for RSA / RAD.
The project we're working on is based on RSA 7.5 and WebSphere 6.1 (J2EE 1.4, EJB 2.1).

Unfortunately I'm not able to deploy the ear file in WebSphere. It worked for some time but after a while a deployment went wrong and now I'm unable to redeploy the application again.

In the "Add and Remove Project Deployments" dialog I'm selecting my ear project.
If I remove and re-add it it says "Error during deployment: Exception deploying bin".
If I click on "Redeploy" it tries to uninstall the application in WebSphere, but the application is already uninstalled and the error is misinterpreted as uninstall failure.

Is there a way out of that?

support-swapna - Mar 30, 2012 - 01:19 PM
Post subject:

striebhz,

Sorry that you are seeing this issue.

1.We released version 10.1 last week. Can you please update to it ? Go to MyEclipse Configuration Center > Software > Software Updates Available. Select the 10.1 , Apply the changes, follow the wizard and restart the IDE when it prompts. Check if the issue persists.

2.Could you paste here deployment log? It is located under directory .myeclipse/logs in EAR project. Before sending, please delete that file, perform deployment.

striebhz - Mar 30, 2012 - 03:19 PM
Post subject:

I would like to update but the extended trail does not allow to use the new version.
The license would be valid until 05/17/2012 but obviously without updates.

support-swapna - Apr 02, 2012 - 07:18 AM
Post subject:

striebhz ,

You can go ahead and extend the trail. You will be able to use the extended key on MyEclipse 10 too.

Let us know if you see any issues.

striebhz - Apr 03, 2012 - 05:40 PM
Post subject:

After upgrading MyEclipse the error seems to be gone.
But there is another issue - I get a bunch of errors like these:
Syntax error, annotations are only available if source level is 5.0
Syntax error, parameterized types are only available if source level is 5.0

-> I set the Java compliance level to 1.5 in Preferences -> Java -> Compiler and I am using the JDK shipped with the WebSphere / RAD installation which is 1.5 compliant.
-> The EJB projects have a "Java 1.5"-Facet configured.

What am I missing?

support-swapna - Apr 05, 2012 - 08:20 AM
Post subject:

striebhz ,

Sorry that you are seeing this issue.

1.Can you also clarify if its an error in the project or an error you only see when you deploy it on WAS 6.1 ?

2. Can you also check if you can deploy the project to WAS 6.1 outside the MyEclipse IDE?

3. Go to Project Properties > Java Compiler and check the JDK compliance level you have over there, it is probably set to 1.4 or lower. Also go to the Project Facets properties page and adjust the version of the Java Facet to match the compiler compliance level chosen on the compiler page.

Let us know how it works for you.

striebhz - Apr 13, 2012 - 12:26 PM
Post subject:

I checked these things, but I'm not able to find an error in my configuration.
After trying different things I noticed that the error does not occur with WAS 7. So I installed WAS 7 (developer editions) and moved on with the evaluation.
It seems like there is a problem deploying a J2EE 1.4 application with Java 5.0 source in WAS 6.1.

But I still have no luck in deploying the application. It works for smaller projects but in the main application I'm facing various errors:
1. Running EJBDeploy on the projects results in an error message (I don't know what it is in English, it means "no matching type found for attribute 'id' - check the classpath"):

Code:

EJB deploy failed
Error while processing project XXX: Es wurde keine Typzuordnung für das Attribut 'id' gefunden. (Typ nicht gefunden - Klassenpfad prüfen)
Es wurde keine Typzuordnung für das Attribut 'id' gefunden. (Typ nicht gefunden - Klassenpfad prüfen)

2. When deploying the project on the fresh installed WAS with MyEclipse there are problems with EJB-Queries:

Code:

Deploying jar XXX
Top-down-Zuordnung wird erstellt
Implementierungscode wird generiert
com.ibm.etools.ejbdeploy.plugin.UserCorrectableGenerationException: Fehler beim Generieren von ejbSelectByKey(java.lang.Long,int,java.util.Date) Abfrage f?r die Bean XXX (Name des abstrakten Schemas =XXX). Fehler=query cannot be pushed down
Abfrage='SELECT OBJECT(b) FROM XXX b WHERE b.ZZZ = ?1 AND b.YYY = ?2 AND b.BBB = (SELECT MAX(b1.BBB) FROM XXX b1 WHERE b1.BBB <= ?3 AND b1.ZZZ = ?1 AND b1.YYY = ?2)'

Why does this error not occur when I'm deploying with RAD?

3. There are 3rd-party jars which have been developed with RAD >= 7.5.5.1. The backend dbm files contain data about 'CharacterStringDataType' which is not compatible to a WAS <= 7.0.0.9 (or WAS 6.1).
Although the jars already contain the ejbdeploy information an ejbdeploy task is executing for that jars on deploying the application resulting in an error:

Code:

org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature 'CharacterStringDataType' not found.

What's wrong with the projects?
Are there restrictions in MyEclipse which cause the problems?

striebhz - Apr 13, 2012 - 12:30 PM
Post subject:

support-swapna wrote:

1.Can you also clarify if its an error in the project or an error you only see when you deploy it on WAS 6.1 ?

Only when I'm deploying. So it seems to be WAS which throws the error, but only when deploying with MyEclipse.

Quote:

2. Can you also check if you can deploy the project to WAS 6.1 outside the MyEclipse IDE?

Yes, RAD and WAS Admin Console are working fine.

Quote:

3. Go to Project Properties > Java Compiler and check the JDK compliance level you have over there, it is probably set to 1.4 or lower. Also go to the Project Facets properties page and adjust the version of the Java Facet to match the compiler compliance level chosen on the compiler page.

I already checked that - everything seems to be configured correctly.
But since there is a workaround by installing WAS 7 that's not the main problem (see last post).

Support-Brian - Apr 17, 2012 - 11:59 PM
Post subject:

striebhz,

1) Could you please confirm what deployment mode you are using right now? i.e. if you go to the profile configuration - what deployment mode have you chosen?

For the classic and enhanced modes, it is possible to prevent the EJBDeploy process from running during deployment - since you mention that EJBDeploy information is already in the JARs - check the MyEclipse > EAR property page on the EAR project for the setting.

For the in-workspace mode, EJBDeploy will not run during deployment and your application will be deployed as-is in the workspace.

2) I'm afraid that your problems appear to be application specific and something we cannot reproduce locally. There is something in your application that prevents us from being able to deploy it correct, but without your application itself, we cannot debug this further. Would it be possible for you to send your application to us? Please write to support@myeclipseide.com ATTN Brian with a link to this thread for details on how the application can be transferred.

striebhz - Apr 24, 2012 - 09:39 AM
Post subject:

I have been able to resolve some issues:
- The WAS has not been set as J2EE runtime (in MyEclipse -> Project Facet). That seems to be missing in the docs and howtos.
- Running the EJBDeploy tool can be deactivated in the project settings, correct.

But this error won't go away:

striebhz wrote:

2. When deploying the project on the fresh installed WAS with MyEclipse there are problems with EJB-Queries:

Code:

Why does this error not occur when I'm deploying with RAD?

I'm sorry but I'm not able to send you the project code.
I think the project is not ready for an IDE migration yet, but we will check that again in some weeks.

Thanks for your help.