[JBoss JIRA] Created: (JBIDE-7234) JAX-WS generated portType implementation has incorrect @WebService annotation
by Gary Brown (JIRA)
JAX-WS generated portType implementation has incorrect @WebService annotation
-----------------------------------------------------------------------------
Key: JBIDE-7234
URL: https://jira.jboss.org/browse/JBIDE-7234
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.0.M2
Reporter: Gary Brown
Assignee: Brian Fitzpatrick
When generating a Java Bean skeleton web service, based on a WSDL definition, the port type implementation class has an incorrect annotation.
The port type implementation has:
@WebService(serviceName = "CreditAgencyInterface", endpointInterface = "org.example.purchasing.creditAgency.CreditAgencyInterface")
but the interface associated with the implementation defines:
@WebService(name = "CreditAgencyInterface", targetNamespace = "http://www.jboss.org/examples/creditAgency")
The end result is that when accessing the WSDL for the endpoint, once deployed to the JBossAS server, the WSDL has an incorrect target namespace and service name - service name is 'CreditAgencyInterface' instead of 'CreditAgencyService', and the target namespace is autogenerated based on the Java package name of the implementation class.
When the annotation in the port type implementation's annotation was changed to be:
@WebService(name = "CreditAgencyInterface", serviceName="CreditAgencyService", targetNamespace="http://www.jboss.org/examples/creditAgency", endpointInterface = "org.example.purchasing.creditAgency.CreditAgencyInterface")
This fixes the serviceName attribute, and adds a 'name' attribute to be the port type. It also specifies explicitly the target namespace.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBIDE-6207) NullPointerException when changing runtime selection in JBossWSRuntimeConfigBlock
by Peter Gebhard (JIRA)
NullPointerException when changing runtime selection in JBossWSRuntimeConfigBlock
---------------------------------------------------------------------------------
Key: JBIDE-6207
URL: https://jira.jboss.org/jira/browse/JBIDE-6207
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.1.0.GA
Reporter: Peter Gebhard
Assignee: Brian Fitzpatrick
Priority: Minor
eclipse.buildId=
java.version=1.6.0_17
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
Error
Thu Apr 22 12:47:32 EDT 2010
Unhandled event loop exception
java.lang.NullPointerException
at org.jboss.tools.ws.creation.ui.project.facet.JBossWSRuntimeConfigBlock.validateTargetRuntime(JBossWSRuntimeConfigBlock.java:156)
at org.jboss.tools.ws.creation.ui.project.facet.JBossWSRuntimeConfigBlock.changePageStatus(JBossWSRuntimeConfigBlock.java:354)
at org.jboss.tools.ws.creation.ui.project.facet.JBossWSRuntimeConfigBlock.setServerSuppliedSelection(JBossWSRuntimeConfigBlock.java:238)
at org.jboss.tools.ws.creation.ui.project.facet.JBossWSRuntimeConfigBlock$1.widgetSelected(JBossWSRuntimeConfigBlock.java:85)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:157)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBIDE-7104) CA proposals aren't filtered when CA is invoked right before next tag or tag ending (before '<'-character)
by Victor Rubezhny (JIRA)
CA proposals aren't filtered when CA is invoked right before next tag or tag ending (before '<'-character)
----------------------------------------------------------------------------------------------------------
Key: JBIDE-7104
URL: https://jira.jboss.org/browse/JBIDE-7104
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.2.0.M2
Environment: Eclipse 3.6, WTP 3.2
Reporter: Victor Rubezhny
Assignee: Victor Rubezhny
Fix For: 3.2.0.CR1
The proposals aren't filtered and aren't able to be applied when CA is invoked right before next tag / tag ending openning character ('<')
Steps to reproduce:
EXECUTE: Open home.xhtml page (exists in Seam template project, but ) for editing
EXECUTE: Find '<h:panelGrid>' tag and place the cursor right before the beginning character og this tag
EXECUTE: Start to type some tag name, (for example, type '<ui:in') and then press Ctrl-Space to invoke the Content Assistant
ASSERT: The CA shows the tag name proposals which are filtered by 'ui:in' string (<ui:include />, <ui:insert />) - FAILED
ASSERT: It's able to apply some selected proposal - FAILED
JUnit test org.jboss.tools.jst.jsp.test.ca.JstJspJbide1585Test fails because of this issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBIDE-6175) Cannot create JbossWS on EAP 4.2
by Libor Zoubek (JIRA)
Cannot create JbossWS on EAP 4.2
--------------------------------
Key: JBIDE-6175
URL: https://jira.jboss.org/jira/browse/JBIDE-6175
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.1.0.GA
Reporter: Libor Zoubek
Assignee: Brian Fitzpatrick
Attachments: .log
I am not able to generate web service client stubs on eap 4.2. btw there is no direct support for eap 4.2 runtime. One can add only eap 4.3 runtime or jboss-as 4.2.
I am getting error with stacktrace:
IWAB0014E Unexpected exception occurred.
java.lang.NullPointerException
at org.jboss.tools.ws.creation.core.commands.ClientSampleCreationCommand.findJavaUnitsByAnnotation(ClientSampleCreationCommand.java:310)
at org.jboss.tools.ws.creation.core.commands.ClientSampleCreationCommand.execute(ClientSampleCreationCommand.java:80)
at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
Steps to reporoduce:
1. Get eap-4.2 (e.g. from pokchop)
2. Add eap-4.2 as eap 4.3 runtime or jboss-as 4.2 runtime
3. Create dynamic web project
4. Create web service client (to enter valid wsdl url you might need to create some webservice)
Reproducible : always
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBIDE-6692) [tester] http connection should not be done in main thread
by Lukas Jungmann (JIRA)
[tester] http connection should not be done in main thread
----------------------------------------------------------
Key: JBIDE-6692
URL: https://jira.jboss.org/browse/JBIDE-6692
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.0.M2
Reporter: Lukas Jungmann
Assignee: Brian Fitzpatrick
Priority: Critical
-open WebService tester view
-click on the "Get from WSDL" button
-click on the "URL..." button
-type in some wrong URL (ie: http://www.webservicex.net/sunsetriseservice.asmx) in the dialog and press OK
=> IDE becomes unusable for quite big amount of time - seems to be frozen but thread dump says:
"main" prio=10 tid=0x081e8000 nid=0x1289 runnable [0xbfaee000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
- locked <0x430bff98> (a java.io.BufferedInputStream)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:687)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1072)
- locked <0x430af9e0> (a sun.net.www.protocol.http.HttpURLConnection)
at java.net.URL.openStream(URL.java:1010)
at com.ibm.wsdl.util.StringUtils.getContentAsInputStream(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
at org.jboss.tools.ws.ui.utils.TesterWSDLUtils.readWSDLURL(TesterWSDLUtils.java:113)
at org.jboss.tools.ws.ui.views.WSDLBrowseDialog.validate(WSDLBrowseDialog.java:492)
at org.jboss.tools.ws.ui.views.WSDLBrowseDialog.access$0(WSDLBrowseDialog.java:487)
at org.jboss.tools.ws.ui.views.WSDLBrowseDialog$1.modifyText(WSDLBrowseDialog.java:170)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:173)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1263)
at org.eclipse.swt.widgets.Combo.setText(Combo.java:2197)
at org.jboss.tools.ws.ui.views.WSDLBrowseDialog$4.widgetDefaultSelected(WSDLBrowseDialog.java:306)
at org.jboss.tools.ws.ui.views.WSDLBrowseDialog$4.widgetSelected(WSDLBrowseDialog.java:291)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3552)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3171)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$4.widgetSelected(JAXRSWSTestView2.java:367)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)ncher.java:110)
...
-type/paste in some URL into the url combo, ie: http://www.webservicex.net/sunsetriseservice.asmx
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months