[frankc01a]

If the compliance level in the properties for the project are set to Level 6, MyEclipse Web Service creation will not work. It does if I temporarily change it to 5.0 but that presents problems for my application.

MyEclipse should support compliance level 6. This is preventing us from using JAX-WS as a solution.

I am using ME 6.5 GA (not blue)

[Loyal Water]

I’ll get this tested and get back to you with an update asap.

[frankc01a]

Thank you Nipun

[Brian Fernandes]

Frank,

I created a new J2EE 1.5 web project, changed compiler compliance level to 6 (on the Java Compiler page) and was still able to generate a JAX-WS web service.
Can you explain what you mean by “web service creation will not work”?

Thanks.

[frankc01a]

Each time I select a bean to do bottom up it says that it is an invalid entry. The remaining textboxes and checkboxes remain grayed.

This app started it’s life as a “Web Project”

[Brian Fernandes]

Frank,

I have a feeling you are using a different wizard. Here is the JAX-WS tutorial for MyEclipse, can you confirm that you are using these steps to generate your web service?
http://www.myeclipseide.com/documentation/quickstarts/webservices_jaxws/index.html

Sorry for the inconvenience caused.

[frankc01a]

Information:

Created application as a “Web Application” months ago

ME 6.5
JRE System Library 1.60_05
Jave EE 5 Libraries
Hibernate 3.2
Spring 2.0
JAX-WS 2.1

I select “New Web Service” as per the documentation
Select JAX-WS Framework
Select “Create web service from Java Bean (Bottom-up Scenario)
Click Next
In the next dialog of the wizard, everything is GRAY except “Java Bean”
I specify the Java Bean from the browser
It returns with “Specified bean does not exist”

Frank

[Brian Fernandes]

Frank,

Thanks for following up. I checked the code and you will see this error if for some reason the JDT fails to find a compiled version of the class in your project.
Sanity check: Could you make sure your project is completely built before invoking this wizard? Also, I assume your project has no compile errors when compliance level 6 is selected and you are selecting the class using the Browse button, not typing it in.

I have tried replicating your exact scenario my choosing a class when the compliance level is set to 6 and have faced no issues. We would definitely like to resolve this, is there anyway you can reduce this to small use case project which you can send over to our team for analysis? If you can, please email: support@genuitec.com ATTN Brian.

[frankc01a]

Simple Use Case that fails as well:

Pre-req: Have Java 1.60_05 environment with Compliance Level 6

1. Create a new Web Project without Maven support : JaxWsTest with Jave EE.
2. When dialog pops about about Java Compliance getting reset to Level 5, answer NO
3. Create a package on src: org.fvjc.jaxws.test
4. Create a class in package: JaxWsTest
5. Add a string property
6. Add construct and getters
7. Click on New Web Service
8. Select JaxWS and bottom up
9. Note that the browse dialog for setting the bean has most fields disabled
10. Use “Browse” to select JaxWsTest
11. Get the error noted in this email trail

Is there any file you would care to see the contents of?

Frank

[Brian Fernandes]

Frank,

I followed all your steps exactly, at step #11, I don’t see the error. I specifically tried with 1.6.0_05 with a global compliance setting at 6.0 (which is the only reason you will get the warning at step #2).

Please note that step #9 where all the fields are disabled is by design. Can you try to repeat this in a new test workspace? If you can, can you send us the sample project (export it as a ZIP archive) you create following the above steps to the email address mentioned above?

Thanks.

[Brian Fernandes]

Frank,

I received your project, thanks. The problem most likely is the fact that you are running MyEclipse with JDK 1.5 (this is what our All-in-one installer ships with), not JDK 1.6; this is different from the JREs that may be listed in the Installed JREs preference page.

So, to fix this problem, you need to run MyEclipse with a 1.6 series VM. To do this, edit the shortcut our installer created so that it is something like this:

"D:\MyEclipse 6.5 Blue\eclipse\eclipse.exe" -vm "C:\jdk1.6.0_05\bin\javaw.exe"

Note the -vm argument.

I apologize for not realizing this earlier, I was running a 1.6 series VM myself and could not replicate the issue. Please let us know if you need further assistance.

[frankc01a]

Brian,

This approach made no difference. I’ve used the jdk1.6.0_5 javaw as well as the jre version to no avail.

Frank

[Brian Fernandes]

Frank,

Please go to MyEclipse > Installation Summary > Installation Details and paste the contents here.

[frankc01a]

*** Date:
Saturday, June 28, 2008 5:51:35 AM EDT

** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.6.0_05

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 6.5.0 GA
Build id: 6.5.0-GA-20080609

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 6.5.0 GA
Build id: 6.5.0-GA-20080609

Eclipse Platform

Version: 3.3.3.r33x_r20080129-_19UEl7Ezk_gXF1kouft
Build id: M20080221-1800

Eclipse RCP

Version: 3.3.3.r33x_r20080129-8y8eE9UEUWI6qujeED0xT7bc
Build id: M20080221-1800

Eclipse Java Development Tools

Version: 3.3.2.r33x_r20080129-7o7jE7_EDhYDiyVEnjb1pFd7ZGD7
Build id: M20080221-1800

Eclipse Project SDK

Version: 3.3.3.r33x_r20080129-7M7J7LB-u3aphGW6o3_VmiVfGXWO
Build id: M20080221-1800

Eclipse Plug-in Development Environment

Version: 3.3.3.r33x_r20080129-7N7M5DQVIA_6oJsEFkEL
Build id: M20080221-1800

Eclipse Graphical Editing Framework

Version: 3.3.2.v20080129
Build id: 20080221-1602

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\MyEclipse 6.5\eclipse\eclipse.exe
-name
Eclipse
–launcher.library
C:\Program Files\MyEclipse 6.5\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.3.R33x_v20080118\eclipse_1023.dll
-startup
C:\Program Files\MyEclipse 6.5\eclipse\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
-exitdata
162c_114
-clean
-vm
C:\Program Files\Java\jdk1.6.0_05\bin\javaw.exe

[frankc01a]

Brian

It works now. When I added the Java Bean to the bottom up wizard approach it was complaining about a zero-arg constructor. I saw the error icon and assumed it was the same. Added the zero constructor and all is well now.

So your documentation will be good to update, or the help files for MyEclipse. A better error would be helpful to the others who will go through the same problem I did.

Thanks
Frank

[Author]

Posts