Community
Participate
Working Groups
Move the support for Axis runtime from Axis 1.1 to Axis 1.2. A new plugin org.apache.axis12 (similar to org.apache.axis11) will be created to hold the JARs from Axis 1.2 and it's license files. The dependency of following plugins need to change: org.apache.wsil4j org.eclipse.jst.ws.axis.consumption.core org.eclipse.jst.ws.axis.consumption.ui org.eclipse.wst.ws.explorer org.eclipse.wst.ws.parser org.eclipse.wst.wsi org.uddi4j To support Axis 1.2 in the Web Service wizard: Also AddAxisJARToBuildPathCommand and CopyAxisJarCommand in axis.consumption.ui plugin need to be updated. We also need to test the explorer and the wst.wsi plugin with Axis 1.2.
I've created the org.apache.axis12 plugin and tested bottom-up, top-down and client scenario with the M4 driver. Creating bottom-up Web service with AddressBook worked for RPC/encoded and doc/lit (wrapped) but has a NPE during invocation for doc/lit (same problem as with Axis 1.0 and Axis 1.1). Creating bottom-up Web service with Echo worked fine using doc/lit. I've tested bottom-up scenario using Axis 1.2 with 0603I driver as well but was not able to test skeleton and client because of defect 98537. I've also tested the WSE UDDI funciton and the WS-I validation using Axis 1.2 with 0603I driver and it worked fine. So we are just waiting for legal approval and need to update the license and readme files before able to check in the plugin into the CVS repository.
*** Bug 92603 has been marked as a duplicate of this bug. ***
FYI, Axis 1.2.1 is now available. In Axis' lib/ directory, only axis.jar and axis-ant.jar differ from Axis 1.2. I've sent note(s) to Janet Campbell seeking clearance to ship Axis 1.2.1 in WTP. If we don't get clearance in time for M5, we'll set our sights on M6.
I've updated the JARs, license, release note and readme in the org.apache.axis12 plugin to use the files from Axis 1.2.1. I've also removed the call to LiteralSupportMessageTask since literal support for Axis 1.2 is suppose to be better. I am still getting a runtime error when doing doc/literal (no wrap) on AddressBook though (Echo is fine). There's going to be 8 patches and 1 zip containig the org.apache.axis12 plugin. This can go in once we get legal clearance.
Created attachment 23388 [details] Patch 1 of 8
Created attachment 23389 [details] Patch 2 of 8
Created attachment 23390 [details] Patch 3 of 8
Created attachment 23391 [details] Patch 4 of 8
Created attachment 23392 [details] Patch 5 of 8
Created attachment 23393 [details] Patch 6 of 8
Created attachment 23394 [details] Patch 7 of 8
Created attachment 23395 [details] Patch 8 of 8
I just found out that I could not attach the whole Axis 1.2 plugin in 1 patch. I'm attaching the plugin without the JARs. Here's the list of JARs to get from Axis 1.2.1 and put into the org.apache.axis12 lib directory: activation.jar axis-ant.jar axis.jar commons-discovery-0.2.jar commons-httpclient-3.0-rc2.jar commons-logging-1.0.4.jar jaxrpc.jar log4j-1.2.8.jar mailapi_1_3_1.jar saaj.jar servlet.jar wsdl4j-1.5.1.jar Note that we are not putting xercesImpl.jar and xmlParserAPIs.jar in because it's the same level shipped in the org.apache.xerces plugin and a dependency was added to the xerces plugin. URL for Axis 1.2.1: http://apache.mirror.rafal.ca/ws/axis/1_2_1/axis-bin-1_2_1.zip
Created attachment 23397 [details] org.apache.axis12 plugin without JARs in lib directory
We also need to test Axis 1.2.1 with SLES to see if the problem with deploy is fixed or not. If not, we'll have to repatch config_wsdd in Axis.jar (Rupam did it before).
It doesn't look like it made it to M5, anyone know when axis 1.2.1 will be part of WTP ?
This Axis 1.2.1 didn't make it into M5 so I'm reopening this defect and assigning a target of M6.
Hi Chris Can you change the priority of this defect from "enhancement" to normal/major since I am waiting for Axis 1.2 since the previous release of WTP? I would not have to wait another shifted release (aka M7) due to the "enhancement" flavor. Regards
I agree, this is not an enhancement. Axis is broken with the 1.5 jdk
Changing to major. The most irritating thing about this bug is we have the fix ready (see patches) but cannot commit it until we have the necessary legal clearance. We will continue to push for this and try to get Axis upgraded before WTP 0.7 is released, but if this fails, we will have to target 1.0 M8 and make do with the attached patches in the interim.
Its not in 0.7 RC1 Any word from the legal team? thanks, Luis
Sorry, no word yet. We have notified legal yet again to please approve Axis 1.2.1.
Here's the note Chris sent out to wtp-dev: EOD yesterday we received legal approval to ship Axis 1.2.1 with Eclipse WTP. We are down to the wire on declaring RC2 and WTP 0.7 and would ordinarily not entertain a change of this sort now, but knowing the value of Axis 1.2.1 over Axis 1.1 have decided to attempt this change today, along with all the necessary testing, code reviews and risk assessment required at this stage. If the change goes smoothly and the risk appears very low, we will replace plugin "org.apache.axis11" containing Axis 1.1 by plugin "org.apache.axis" containing Axis 1.2.1. If for any reason - again, thru testing, code reviews or risk assessment - we find this change to carry any risk of regression, then we will regretfully have to postpone it to WTP 1.0. On a more technical level, the change from Axis 1.1 to Axis 1.2.1 affects these aspects of WTP, all of which will endure a measure of testing before we even consider committing the change: 1. The Web service Axis wizards run the Axis emitters and other bits of the Axis distribution to generate Axis services and clients. 2. The Web service Axis wizards deploy the Axis jars to the target Web project hosting the Axis service or client. 3. The Web Services Explorer and UDDI4J both act as Web service clients, using the Axis runtime for invoking Web services and talking to UDDI registries. 4. The WSI test tools rely on a smidgen of code from the Axis distribution. Note: This change is to replace Axis 1.1 by 1.2.1. It will NOT result in both Axis 1.1 and 1.2.1 being available in the Web services wizards for purposes of deploying clients or services. Support for multiple versions of Axis is being tracked under enhancement 88684 (https://bugs.eclipse.org/bugs/show_bug.cgi? id=88684).
Here's the extent of the change: - New plugin org.apache.axis created with version 1.2.1. This replaces org.apache.axis11. The new plugin contains the new license files and the following JARs from axis-bin-1_2_1.zip: axis-ant.jar axis.jar commons-discovery-0.2.jar commons-logging-1.0.4.jar jaxrpc.jar log4j-1.2.8.jar saaj.jar wsdl4j-1.5.1.jar Note that the previous list of JARs from comment 13 was from axis-src-1_2_1.zip and we should only need to include the JARs from axis-bin-1_2_1.zip. - New feature plugin org.apache.axis.feature created with version 1.2.1. This replaces org.apache.axis11.feature. - The dependencies of the following plugins are updated from org.apache.axis11 to org.apache.axis: org.apache.wsil4j org.eclipse.jst.ws.axis.consumption.core org.eclipse.jst.ws.axis.consumption.ui org.eclipse.wst.ws.explorer org.eclipse.wst.ws.parser org.eclipse.wst.wsi org.uddi4j - Code in the following plugins are modified for the Web service wizard to use Axis 1.2.1 rather than Axis 1.1: - org.eclipse.jst.ws.axis.consumption.ui - org.eclipse.jst.ws.axis.creation.ui - Plugin org.eclipse.wst.feature updated to include org.apache.axis.feature rather than org.apache.axis11.feature. The changed had been committed and tagged as v20050721_1900 and the following map files were tagged: - jst-ws.map - wst-ws.map - wst-ws-thirdparty.map - wtp-feature.map I've done some testing with bottom-up, top-down and client scenario using the new plugin. Jeffrey Liu had done testing with the WS Explorer and David Lauzon had tested the wsi validation.
Also changed the reference to org.apache.axis from org.apache.axis11 in the feature org.eclipse.jst.feature and org.uddi4j.feature.
Verified on WTP 0.7.
Same error here with Eclipse Callisto, Version: 3.2.0, Build id: M20060921-0945. Java version 1.4.2_06, Please reopen this bug. IWAB0019E Error in getting method from Java bean. java.lang.NullPointerException at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:357) at org.eclipse.jem.internal.util.emf.workbench.ProjectResourceSetImpl.getResource(ProjectResourceSetImpl.java:262) at org.eclipse.jem.internal.util.emf.workbench.ProjectResourceSetImpl.getEObject(ProjectResourceSetImpl.java:185) at org.eclipse.jem.java.internal.impl.JavaRefFactoryImpl.reflectType(JavaRefFactoryImpl.java:401) at org.eclipse.jem.java.internal.impl.JavaRefFactoryImpl.reflectType(JavaRefFactoryImpl.java:388) at org.eclipse.jst.ws.internal.common.JavaMOFUtils.getJavaClass(JavaMOFUtils.java:199) at org.eclipse.jst.ws.internal.axis.creation.ui.command.JavaToWSDLMethodCommand.execute(JavaToWSDLMethodCommand.java:83) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:413) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:353) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:251) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$5.run(SimpleCommandEngineManager.java:250) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:851) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:220) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:94) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:145) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:751) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:351) at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:254) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952)
Mirza, I'm not sure if you meant your comment 27 for this bug, or another. In any event, please open a new bug to track the problem you're seeing. Thanks - CB.
