Bug 235309 - Java First: no additional code generated if JAX-WS RI chosen as runtime
Summary: Java First: no additional code generated if JAX-WS RI chosen as runtime
Status: RESOLVED DUPLICATE of bug 236417
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: STP (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Oisin Hurley CLA
QA Contact: Oisin Hurley CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-03 07:44 EDT by David Porter CLA
Modified: 2012-09-21 14:40 EDT (History)
0 users

See Also:


Attachments
Log file with errors when creating a Java First project with the JAX-WS RI (156.13 KB, application/octet-stream)
2008-06-03 07:44 EDT, David Porter CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Porter CLA 2008-06-03 07:44:52 EDT
Created attachment 103286 [details]
Log file with errors when creating a Java First project with the JAX-WS RI

To reproduce:

Set the JAX-WS RI as your installed runtime for SOA Tools.
Create a Java First project based on the following HelloWorld.java:

package test.hw;

public class HelloWorld {

	public static void main(String[] args) {

		System.out.println("Hello world!");

	}

}

Expected

After you have chosen the Java source file, I expected to be able to generate a client or a server and/or a WSDL file, as is the case when using the CXF runtime.
This choice was not available to me.

The log file displays the following error:

!ENTRY org.eclipse.jst.server.core 4 0 2008-06-03 12:32:15.467
!MESSAGE Could not create delegate RuntimeClasspathProviderWrapper[org.eclipse.stp.soas.deploy.runtime.cxf.runtimeTarget]
!STACK 1
org.eclipse.core.runtime.CoreException: Plug-in org.eclipse.stp.soas.deploy.runtime.jaxwsri was unable to load class org.eclipse.jst.server.generic.core.internal.GenericServerRuntimeTargetHandler.
Comment 1 Oisin Hurley CLA 2008-06-11 22:50:22 EDT

*** This bug has been marked as a duplicate of bug 236417 ***