Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 188895

Summary:

WSDM Tooling code generation should use In-built or User-defined Axis-2 jar files

Product:

z_Archived

Reporter:

Saurabh Dravid <sadravid>

Component:

TPTP.monitoring

Assignee:

Andrew Eberbach <aeberbac>

Status:

CLOSED FIXED

QA Contact:

Bhanu Prathap V <bhanu.prathap>

Severity:

major

Priority:

CC:

aeberbac, sadravid

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

closed460

Bug Depends on:

179329

Bug Blocks:

178487

Attachments:

Description	Flags
Use built in axis2	none
Updated patch to include the plugin skeleton for axis2	none

Description Saurabh Dravid

2007-05-24 08:50:27 EDT

When doing code generation in WSDM tooling we need to use the Axis-2 jar files comes with Eclipse built-in plugin, and also we need to support the other version of Axis-2 that requires exiting preference page UI changes so that user can specify the other version of Axis-2 and those jar files will be used in code generation.

Comment 1 Balan Subramanian

2007-05-30 17:40:25 EDT

Created attachment 69406 [details]
Use built in axis2

Comment 2 Balan Subramanian

2007-05-30 17:50:44 EDT

Created attachment 69412 [details]
Updated patch to include the plugin skeleton for axis2

Comment 3 Balan Subramanian

2007-05-30 23:13:27 EDT

Clarification on the bug:
Eclipse legal has approved Apache Axis2 JARs to be shipped with TPTP particularly for the WSDM tooling. However the approval is only for Axis2 1.1. Users may wish to use other axis2 versions so we should allow option for user to either use the built version of axis2 or provide the location of their own.

Also we need a plugin for axis2 since orbit does not provide one today.

Comment 4 Balan Subramanian

2007-05-30 23:31:03 EDT

Patch from 5/30 checked in. 
QA please verify and also add new test cases to cover this.

Comment 5 Paul Slauenwhite

2009-06-30 12:15:05 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.