[JBoss JIRA] (JBIDE-20124) NPE when removing a returned class in JAX-RS resource method does not exist
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-20124:
-------------------------------------
Summary: NPE when removing a returned class in JAX-RS resource method does not exist
Key: JBIDE-20124
URL: https://issues.jboss.org/browse/JBIDE-20124
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.3.0.Alpha2
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.3.0.Beta2
If a project contains a method such as
{code}
@Path("/{id}/comments")
public Foo addComments() {
return null;
}
{code}
while {{Foo}} does not exist, the JAX-RS Metamodel builder will fail with the following exception:
{code}
java.lang.NullPointerException
at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.findSubtypes(JdtUtils.java:905)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsEndpointFactory.createEndpointsFromSubresourceLocator(JaxrsEndpointFactory.java:145)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsElementChangedProcessorDelegate.processSubresourceLocatorAddition(JaxrsElementChangedProcessorDelegate.java:285)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsElementChangedProcessorDelegate.processAddition(JaxrsElementChangedProcessorDelegate.java:191)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsElementChangedProcessorDelegate.processEvent(JaxrsElementChangedProcessorDelegate.java:70)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processElementChange(JaxrsMetamodel.java:751)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.add(JaxrsMetamodel.java:720)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsBaseElement.joinMetamodel(JaxrsBaseElement.java:127)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResourceMethod$Builder.buildInResource(JaxrsResourceMethod.java:181)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:211)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:65)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:420)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:392)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:73)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20014) Explorer: "New" context menu not showing up at times (Linux only, GTK2 and GTK3)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20014?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20014:
-------------------------------------
Workaround Description: close and reopen the OpenShift explorer and repeat if still no submenu visible (was: close and reopen the OpenShift explorer)
> Explorer: "New" context menu not showing up at times (Linux only, GTK2 and GTK3)
> --------------------------------------------------------------------------------
>
> Key: JBIDE-20014
> URL: https://issues.jboss.org/browse/JBIDE-20014
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.3.0.Beta1
> Environment: Linux GTK2, GTK3
> Reporter: Andre Dietisheim
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.3.0.Beta2
>
> Attachments: new-submenu-not-visible.png, new-submenu-visible.png
>
>
> It is quite frequent that the "New" (and "Show in" for v3) submenu wont show up. This happens even if the submenu is first visible but then, on a 2nd context menu invocation, disappears
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20111) Quickstarts from JBoss Central won't run properly via Run AS > Run in Server
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20111?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20111:
-------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Beta2)
> Quickstarts from JBoss Central won't run properly via Run AS > Run in Server
> ----------------------------------------------------------------------------
>
> Key: JBIDE-20111
> URL: https://issues.jboss.org/browse/JBIDE-20111
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.0.Beta1
> Environment: JBDS 9.0.0.Beta1-v20150617-0654-B56 with bundled EAP
> Reporter: Vlado Pakan
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: respin-c
> Fix For: 4.3.0.Beta1
>
>
> 1. Import kitchensink-rf from JBoss Central (or any other quickstart)
> 2. Run kitchensink-rf on bundled EAP server
> ERROR: URL opened in internal browser is http://localhost:8080/jboss-kitchensink-rf/ and it displays HTTP Status 404 error (JBWEB000124: The requested resource is not available.)
> Imported project name in Package Explorer is kitchensink-rf
> Deployed war file name is kitchensink-rf.war
> Server is creating context for /kitchensink-rf
> {noformat}
> 07:09:58,393 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /kitchensink-rf
> {noformat}
> URL http://localhost:8080/kitchensink-rf/ without 'jboss-' prefix in project name works fine
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20111) Quickstarts from JBoss Central won't run properly via Run AS > Run in Server
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20111?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20111:
--------------------------------
Labels: respin-c (was: )
> Quickstarts from JBoss Central won't run properly via Run AS > Run in Server
> ----------------------------------------------------------------------------
>
> Key: JBIDE-20111
> URL: https://issues.jboss.org/browse/JBIDE-20111
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.0.Beta1
> Environment: JBDS 9.0.0.Beta1-v20150617-0654-B56 with bundled EAP
> Reporter: Vlado Pakan
> Assignee: Fred Bricon
> Priority: Critical
> Labels: respin-c
> Fix For: 4.3.0.Beta2
>
>
> 1. Import kitchensink-rf from JBoss Central (or any other quickstart)
> 2. Run kitchensink-rf on bundled EAP server
> ERROR: URL opened in internal browser is http://localhost:8080/jboss-kitchensink-rf/ and it displays HTTP Status 404 error (JBWEB000124: The requested resource is not available.)
> Imported project name in Package Explorer is kitchensink-rf
> Deployed war file name is kitchensink-rf.war
> Server is creating context for /kitchensink-rf
> {noformat}
> 07:09:58,393 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /kitchensink-rf
> {noformat}
> URL http://localhost:8080/kitchensink-rf/ without 'jboss-' prefix in project name works fine
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20111) Quickstarts from JBoss Central won't run properly via Run AS > Run in Server
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20111?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20111:
--------------------------------
Priority: Blocker (was: Critical)
> Quickstarts from JBoss Central won't run properly via Run AS > Run in Server
> ----------------------------------------------------------------------------
>
> Key: JBIDE-20111
> URL: https://issues.jboss.org/browse/JBIDE-20111
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.0.Beta1
> Environment: JBDS 9.0.0.Beta1-v20150617-0654-B56 with bundled EAP
> Reporter: Vlado Pakan
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: respin-c
> Fix For: 4.3.0.Beta2
>
>
> 1. Import kitchensink-rf from JBoss Central (or any other quickstart)
> 2. Run kitchensink-rf on bundled EAP server
> ERROR: URL opened in internal browser is http://localhost:8080/jboss-kitchensink-rf/ and it displays HTTP Status 404 error (JBWEB000124: The requested resource is not available.)
> Imported project name in Package Explorer is kitchensink-rf
> Deployed war file name is kitchensink-rf.war
> Server is creating context for /kitchensink-rf
> {noformat}
> 07:09:58,393 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /kitchensink-rf
> {noformat}
> URL http://localhost:8080/kitchensink-rf/ without 'jboss-' prefix in project name works fine
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20111) Quickstarts from JBoss Central won't run properly via Run AS > Run in Server
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20111?page=com.atlassian.jira.plugi... ]
Len DiMaggio commented on JBIDE-20111:
--------------------------------------
Without the fix - user installs example, accepts all defaults, and the example appears to not run. That's too basic a use case to ship with the beta - we need the fix in a respin. Thx!
> Quickstarts from JBoss Central won't run properly via Run AS > Run in Server
> ----------------------------------------------------------------------------
>
> Key: JBIDE-20111
> URL: https://issues.jboss.org/browse/JBIDE-20111
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.0.Beta1
> Environment: JBDS 9.0.0.Beta1-v20150617-0654-B56 with bundled EAP
> Reporter: Vlado Pakan
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> 1. Import kitchensink-rf from JBoss Central (or any other quickstart)
> 2. Run kitchensink-rf on bundled EAP server
> ERROR: URL opened in internal browser is http://localhost:8080/jboss-kitchensink-rf/ and it displays HTTP Status 404 error (JBWEB000124: The requested resource is not available.)
> Imported project name in Package Explorer is kitchensink-rf
> Deployed war file name is kitchensink-rf.war
> Server is creating context for /kitchensink-rf
> {noformat}
> 07:09:58,393 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /kitchensink-rf
> {noformat}
> URL http://localhost:8080/kitchensink-rf/ without 'jboss-' prefix in project name works fine
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19946) running webservice test gives errors
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19946?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-19946:
-------------------------------------------
[~nickboldt] Ok, even with Java 8...
{code}
$ java -version
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b15)
Java HotSpot(TM) Client VM (build 25.45-b02, mixed mode, sharing)
{code}
And Tycho 0.22 in the maven command line...
{code}
$ mvn -U clean install -Djbosstools.test.jre.5=e:\jdk5\jre\ -Djbosstools.test.jre.6=e:\jdk6\jre\ -Pdefault,jbosstools-nightly-staging-composite,jbosstools-nightly-staging-composite-soa-tooling -DtychoVersion=0.22.0
{code}
I'm still seeing...
{code}
-------------------------------------------------------
T E S T S
-------------------------------------------------------
java.lang.RuntimeException: Bundle org.jboss.tools.ws.core.test is not found
at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.getBundleClassLoader(OsgiSurefireBooter.java:162)
at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.createCombinedClassLoader(OsgiSurefireBooter.java:98)
at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
Picked up _JAVA_OPTIONS: -Xmx512M
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] jbosstools-webservices ............................ SUCCESS [0.357s]
[INFO] ws.plugins ........................................ SUCCESS [0.014s]
[INFO] org.jboss.tools.ws.core ........................... SUCCESS [5.452s]
[INFO] org.jboss.tools.ws.creation.core .................. SUCCESS [1.456s]
[INFO] org.jboss.tools.ws.wise.ui ........................ SUCCESS [1.901s]
[INFO] org.jboss.tools.ws.ui ............................. SUCCESS [1.809s]
[INFO] org.jboss.tools.ws.creation.ui .................... SUCCESS [1.091s]
[INFO] org.jboss.tools.ws.jaxrs.core ..................... SUCCESS [1.140s]
[INFO] org.jboss.tools.ws.jaxrs.ui ....................... SUCCESS [1.285s]
[INFO] org.jboss.tools.websockets.core ................... SUCCESS [0.694s]
[INFO] org.jboss.tools.websockets.ui ..................... SUCCESS [0.683s]
[INFO] ws.tests .......................................... SUCCESS [0.016s]
[INFO] org.jboss.tools.ws.core.test ...................... FAILURE [17.824s]
[INFO] org.jboss.tools.ws.creation.core.test ............. SKIPPED
[INFO] org.jboss.tools.ws.ui.test ........................ SKIPPED
[INFO] org.jboss.tools.ws.jaxrs.core.test ................ SKIPPED
[INFO] org.jboss.tools.ws.jaxrs.ui.test .................. SKIPPED
[INFO] org.jboss.tools.websockets.ui.test ................ SKIPPED
[INFO] ws.features ....................................... SKIPPED
[INFO] org.jboss.tools.ws.feature ........................ SKIPPED
[INFO] org.jboss.tools.ws.jaxrs.feature .................. SKIPPED
[INFO] org.jboss.tools.ws.test.feature ................... SKIPPED
[INFO] org.jboss.tools.websockets.feature ................ SKIPPED
[INFO] org.jboss.tools.websockets.test.feature ........... SKIPPED
[INFO] ws.site ........................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2:05.562s
[INFO] Finished at: Thu Jun 18 14:33:01 MDT 2015
[INFO] Final Memory: 92M/262M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.22.0:test (default-test) on project org.jboss.tools.ws.core.test: An unexpected error occured while launching the test runtime (return code -1). See log for details. -
> [Help 1]
{code}
> running webservice test gives errors
> ------------------------------------
>
> Key: JBIDE-19946
> URL: https://issues.jboss.org/browse/JBIDE-19946
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Max Rydahl Andersen
> Assignee: Brian Fitzpatrick
> Fix For: 4.3.0.Beta2
>
>
> running 4.3.0.Beta1x with jdk's defined I get this error:
> {code}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> Retrieving document at 'file:/Users/max/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data/JBossWSTestProject/hello_world.wsdl'.
> null
> null
> Retrieving document at '/Users/max/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data/JBossWSTestProject/hello_world.wsdl'.
> Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 272.543 sec <<< FAILURE! - in org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest) Time elapsed: 82.428 sec
> testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest) Time elapsed: 127.267 sec <<< FAILURE!
> junit.framework.AssertionFailedError: ***********************
> Create Web Service Client...
> Create Web Service...
> Create Web Service Operation...
> Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
> at com.sun.proxy.$Proxy14.sayHello(Unknown Source)
> at org.example.www.helloworld.clientsample.ClientSample.main(ClientSample.java:14)
> Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:439)
> at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:83)
> at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
> at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59)
> at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:158)
> at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:291)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
> ... 4 more
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.checkText(JBossWSJavaFirstCommandTest.java:163)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult(JBossWSJavaFirstCommandTest.java:116)
> testInitialClientCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 15.26 sec
> testClientCodeGenerationCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 17.628 sec
> testRemoveClientJarsCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 14.25 sec
> testMergeWebXMLCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest) Time elapsed: 9.174 sec
> testJBIDE6175(org.jboss.tools.ws.creation.core.test.command.JBossWSClientSampleCreationCommandTest) Time elapsed: 6.416 sec
> Results :
> Failed tests:
> JBossWSJavaFirstCommandTest.testDeployResult:116->checkText:163 ***********************
> Create Web Service Client...
> Create Web Service...
> Create Web Service Operation...
> Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
> at com.sun.proxy.$Proxy14.sayHello(Unknown Source)
> at org.example.www.helloworld.clientsample.ClientSample.main(ClientSample.java:14)
> Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:439)
> at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:83)
> at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
> at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59)
> at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:158)
> at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:291)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20111) Quickstarts from JBoss Central won't run properly via Run AS > Run in Server
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20111?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20111:
--------------------------------
Description:
1. Import kitchensink-rf from JBoss Central (or any other quickstart)
2. Run kitchensink-rf on bundled EAP server
ERROR: URL opened in internal browser is http://localhost:8080/jboss-kitchensink-rf/ and it displays HTTP Status 404 error (JBWEB000124: The requested resource is not available.)
Imported project name in Package Explorer is kitchensink-rf
Deployed war file name is kitchensink-rf.war
Server is creating context for /kitchensink-rf
{noformat}
07:09:58,393 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /kitchensink-rf
{noformat}
URL http://localhost:8080/kitchensink-rf/ without 'jboss-' prefix in project name works fine
was:
1. Import kitchensink-rf from JBoss Central
2. Run kitchensink-rf on bundled EAP server
ERROR: URL opened in internal browser is http://localhost:8080/jboss-kitchensink-rf/ and it displays HTTP Status 404 error (JBWEB000124: The requested resource is not available.)
Imported project name in Package Explorer is kitchensink-rf
Deployed war file name is kitchensink-rf.war
Server is creating context for /kitchensink-rf
{noformat}
07:09:58,393 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /kitchensink-rf
{noformat}
URL http://localhost:8080/kitchensink-rf/ without 'jboss-' prefix in project name works fine
> Quickstarts from JBoss Central won't run properly via Run AS > Run in Server
> ----------------------------------------------------------------------------
>
> Key: JBIDE-20111
> URL: https://issues.jboss.org/browse/JBIDE-20111
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.0.Beta1
> Environment: JBDS 9.0.0.Beta1-v20150617-0654-B56 with bundled EAP
> Reporter: Vlado Pakan
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> 1. Import kitchensink-rf from JBoss Central (or any other quickstart)
> 2. Run kitchensink-rf on bundled EAP server
> ERROR: URL opened in internal browser is http://localhost:8080/jboss-kitchensink-rf/ and it displays HTTP Status 404 error (JBWEB000124: The requested resource is not available.)
> Imported project name in Package Explorer is kitchensink-rf
> Deployed war file name is kitchensink-rf.war
> Server is creating context for /kitchensink-rf
> {noformat}
> 07:09:58,393 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /kitchensink-rf
> {noformat}
> URL http://localhost:8080/kitchensink-rf/ without 'jboss-' prefix in project name works fine
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20111) Quickstarts from JBoss Central won't run properly via Run AS > Run in Server
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20111?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20111:
--------------------------------
Fix Version/s: 4.3.0.Beta2
> Quickstarts from JBoss Central won't run properly via Run AS > Run in Server
> ----------------------------------------------------------------------------
>
> Key: JBIDE-20111
> URL: https://issues.jboss.org/browse/JBIDE-20111
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.0.Beta1
> Environment: JBDS 9.0.0.Beta1-v20150617-0654-B56 with bundled EAP
> Reporter: Vlado Pakan
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> 1. Import kitchensink-rf from JBoss Central (or any other quickstart)
> 2. Run kitchensink-rf on bundled EAP server
> ERROR: URL opened in internal browser is http://localhost:8080/jboss-kitchensink-rf/ and it displays HTTP Status 404 error (JBWEB000124: The requested resource is not available.)
> Imported project name in Package Explorer is kitchensink-rf
> Deployed war file name is kitchensink-rf.war
> Server is creating context for /kitchensink-rf
> {noformat}
> 07:09:58,393 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /kitchensink-rf
> {noformat}
> URL http://localhost:8080/kitchensink-rf/ without 'jboss-' prefix in project name works fine
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months