[psssystems]

This message has not been recovered.

[psssystems]

This message has not been recovered.

[arapps]

We face the same error.
To overcome this, tried to export the EAR file as EAR (myeclipse) option. THis ear failed to get deployed on WebSphere 6.1 through admin console. – The problem was that
compilation failed during deployment with the error – annotations are not available if source level is not 5.0
One EJB project uses annotations with JAXB and also uses Java 5 generics.

all projects have Websphere 6.1 JRE as the jre system library. The Websphere connector uses the server JDK.
The same issue comes up when myeclipse tries to deploy through wsadmin scripting client. Please help resolve.

[bgreen]

Did anyone ever find a solution to this issue? I’m experiencing the exact same problem with WAS 6.1 and EJB 2.1. We migrated this project to MyEclipse Blue from RAD, and we did not experience this issue in RAD.

Thanks.

[tennisbum79]

Have tried this?

1. Windows–>Preferences–>Java–>Compiler
For Compiler Compliance Level, select 1.5 from dropdown

2. Windows–>Preferences–>Java–>Installed JREs
Point to JRE that is 1.5 ( in the case of WebLogic, it would have been Sun JDK 1.5 or JRockit_150_12)
By default thi would point to MyEclipse’S JDK 1.6

3. Windows–>Preferences–>Servers–>WebSphere–>JDK
Under WebSphere JDK Name, Add JDK 1.5X from WebSphere installation

4. Right-Click on each project
Properties–>Java Compiler
Make sure that “Enable Project Specific settings” is NOT checked.
This way, it will inherit Windows Preference settings of 1.5

Hope this helps

[bgreen]

I really appreciate the reply, but I’m afraid these settings were already configured properly (as described).

Our issue only occurs during deployment. All projects build cleanly in the workspace, but experience compilation errors during deployment. I can intentionally create this issue in my workspace by compiling at a 1.4 compliance level.

I’m at a loss as to why the projects are being built at a 1.5 compliance level in the workspace, but being built at a lower level during deployment. Anyone have any ideas?

[tennisbum79]

@bgreen wrote:

I really appreciate the reply, but I’m afraid these settings were already configured properly (as described).

Our issue only occurs during deployment. All projects build cleanly in the workspace, but experience compilation errors during deployment. I can intentionally create this issue in my workspace by compiling at a 1.4 compliance level.

I’m at a loss as to why the projects are being built at a 1.5 compliance level in the workspace, but being built at a lower level during deployment. Anyone have any ideas?

Have you checked to see whether WebSphere has a deployment setting set at 1.4?

What you describe seems to point to that possiblity…

[bgreen]

I resolved the issue by changing my output folder in the ejb’s classpath. I created a new EJB project and found that MyEclipse defaults the output folder to “classes”. The output folder in my ejb project was defined as “ejbModule”. I added a classes directory beneath the ejb’s main folder and modified the ejb’s .classpath file by changing:

<classpathentry kind=”output” path=”ejbModule”/>
to
<classpathentry kind=”output” path=”classes”/>

I don’t understand how the output directory could possibly impact the deployment’s java compliance level. I thoroughly tested this solution to ensure that this was the true issue. The project was originally built in RAD and converted to MyEclipse Blue via MEB’s project enhancement. RAD had no problem deploying the ejb to WAS.

[bgreen]

Is there anyone on the MyEclipse support team that can reproduce this issue or provide an explanation for this bizzare behavior? I’m receptive to the idea that I’ve done something peculiar which caused this problem, but it’d be great if anyone from MyEclipse can explain or at least confirm this behavior.

Thanks,
Blaine

[Brian Fernandes]

Blaine,

I’ll ask my team to take a look at this problem and get back to you. Ideally projects should continue to work in RAD after enhancement too, so the change in the classpathentry should have not been necessary.I’m not sure atm whether different output folders can have different compliance settings, but we will know soon enough.

[Author]

Posts