Community
Participate
Working Groups
Please look at http://www.eclipse.org/tptp/groups/Architecture/documents/features/hf_150385.html - the second option for user installed axis2 has been approved.
This involves adding a preference page to allow user to pre-specify the location where Axis2 is installed and making the code generation dialog a wizard in which if user chooses a projectizer that needs axis2, the next wizard page will ask for location of axis2 installation. If location is already specified in preferences, it will only do a check and allow for user verification. ON the same wizard page on hitting finish, the tooling will validate that an axis2 install actually exists and the required files are available. Then it will copy those files into the generated project (by specifying them as additional jars in the dd being passed to Muse code gen).
*** Bug 165113 has been marked as a duplicate of this bug. ***
Created attachment 58111 [details] Patch for Code Generation to use Axis2.
Comment on attachment 58111 [details] Patch for Code Generation to use Axis2. The patch is not created properly.
Created attachment 58236 [details] Patch for Code Generation to use Axis2. Please apply this patch.
Removing target because it has not been approved by PMC yet for inclusion in the 4.4 plan. This could be considered part of feature of 150385 and tracked there, unless the sizing for this work cannot be accomodated in the current sizing of 150385.
Will be resolved under 150385 *** This bug has been marked as a duplicate of bug 150385 ***
Created attachment 60426 [details] Axis2 license patch Please apply this patch. This patch will ask for Axis-2 License and it will read the required jar files from extension point.
Created attachment 61508 [details] Reading licence from file Please apply this patch. This will read the Axis-2 licence from licence file.
Verified - closed Build: TPTP-4.4.0-200704250100
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.
