Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339273 - Web Service Client Wizard should not publish JPA projects to the server
Summary: Web Service Client Wizard should not publish JPA projects to the server
Status: RESOLVED FIXED
Alias: None
Product: WTP Webservices
Classification: WebTools
Component: jst.ws (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.3 M6   Edit
Assignee: Mark Hutchinson CLA
QA Contact: Keith Chong CLA
URL:
Whiteboard:
Keywords:
Depends on: 335246
Blocks:
  Show dependency tree
 
Reported: 2011-03-08 14:25 EST by Mark Hutchinson CLA
Modified: 2011-03-08 15:20 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Hutchinson CLA 2011-03-08 14:25:11 EST 
Commit this fix to HEAD for WTP 3.3 also

+++ This bug was initially created as a clone of Bug #335246 +++

To reproduce this problem, generate an axis web service client into a "JPA Project" with the slider set to "start". The wizard will try to add the project to the server.  

JPA Projects have the Utility Module facet.  There is no web or ejb module so there is nothing that can be "run" on the server.


In the org.eclipse.jst.ws.internal.consumption.command.common.AddModuleToServerCommand class we have a check like below:
  if (!J2EEUtils.isJavaComponent(iproject))

The intention is to not add utility modules to the server.   The problem is that if the module is associated with an EAR project this command is doing the isJavaComponent check on the EAR project so it always returns "false".
Comment 1 Mark Hutchinson CLA 2011-03-08 14:30:07 EST 
Checked into HEAD for WTP 3.3
Comment 2 Keith Chong CLA 2011-03-08 15:20:41 EST 
This is a safe fix.  We should get this in for 3.3 M6.