[JBoss JIRA] (JBIDE-12394) Unable to load dialect Error in Drools project
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-12394?page=com.atlassian.jira.plugi... ]
André Dietisheim resolved JBIDE-12394.
--------------------------------------
Resolution: Won't Fix
> Unable to load dialect Error in Drools project
> ----------------------------------------------
>
> Key: JBIDE-12394
> URL: https://issues.jboss.org/browse/JBIDE-12394
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: drools
> Environment: JBoss Tools 2.3.0.v20120321-1339-H91-Beta2
> JBoss Drools Plugin 5.2.1.Final
> On classpath of project in question (configured via maven):
> * drools-compiler, drools-core, knowledge-api, knowledge-internal-api 5.4.0.Final
> * antlr, antlr-runtime 3.3
> * mvel2 2.1.0.drools16
> * ecj 3.5.1
> * stringtemplate 3.2.1
> * xstream 1.4.1
> * xmlpull 1.1.3
> * xpp3_min 1.1.4c
> Reporter: Jörg Henne
> Assignee: Kris Verlaenen
> Priority: Blocker
>
> When new Drools project is created there is this error:
> Unable to load dialect 'org.drools.rule.builder.dialect.mvel.MVELDialectConfiguration:mvel:org.drools.rule.builder.dialect.mvel.MVELDialectConfiguration'
> See attached screenshot.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-12394) Unable to load dialect Error in Drools project
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-12394?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-12394 at 7/2/19 3:26 PM:
------------------------------------------------------------------
Drools was deprecated, I'll thus resolve this as WONTFIX.
was (Author: adietish):
Drools was deprecated, I'll thus resolve this as outdated.
> Unable to load dialect Error in Drools project
> ----------------------------------------------
>
> Key: JBIDE-12394
> URL: https://issues.jboss.org/browse/JBIDE-12394
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: drools
> Environment: JBoss Tools 2.3.0.v20120321-1339-H91-Beta2
> JBoss Drools Plugin 5.2.1.Final
> On classpath of project in question (configured via maven):
> * drools-compiler, drools-core, knowledge-api, knowledge-internal-api 5.4.0.Final
> * antlr, antlr-runtime 3.3
> * mvel2 2.1.0.drools16
> * ecj 3.5.1
> * stringtemplate 3.2.1
> * xstream 1.4.1
> * xmlpull 1.1.3
> * xpp3_min 1.1.4c
> Reporter: Jörg Henne
> Assignee: Kris Verlaenen
> Priority: Blocker
> Fix For: 4.0.0.Alpha1-SOA
>
>
> When new Drools project is created there is this error:
> Unable to load dialect 'org.drools.rule.builder.dialect.mvel.MVELDialectConfiguration:mvel:org.drools.rule.builder.dialect.mvel.MVELDialectConfiguration'
> See attached screenshot.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-18526) CordovaSim: Debugger doesn't work properly with the last JDK 8u20
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-18526?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-18526:
---------------------------------------
[~adietish] CordovaSim was removed, wasn't it?
> CordovaSim: Debugger doesn't work properly with the last JDK 8u20
> -----------------------------------------------------------------
>
> Key: JBIDE-18526
> URL: https://issues.jboss.org/browse/JBIDE-18526
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, cordovasim, upstream
> Affects Versions: 4.2.0.CR2
> Environment: Not reproducible with Oracle JDK 7u67
> Affects Oracle JDK 8u20 and above (Not reproducible with JDK 8u5 and 8u11)
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: upstream
> Fix For: 4.12.x
>
> Attachments: debugger error.png
>
>
> CordovaSim freezes with the following stack trace:
> {code}
> java.lang.IllegalStateException: Nested event loops are allowed only while handling system events
> at com.sun.javafx.tk.quantum.QuantumToolkit.enterNestedEventLoop(QuantumToolkit.java:506)
> at com.sun.javafx.webkit.EventLoopImpl.cycle(EventLoopImpl.java:59)
> at com.sun.webkit.EventLoop.fwkCycle(EventLoop.java:45)
> at com.sun.webkit.Timer.twkFireTimerEvent(Native Method)
> at com.sun.webkit.Timer.fireTimerEvent(Timer.java:83)
> at com.sun.webkit.Timer.notifyTick(Timer.java:64)
> at javafx.scene.web.WebEngine$PulseTimer.lambda$static$44(WebEngine.java:1167)
> at javafx.scene.web.WebEngine$PulseTimer$$Lambda$67/10449826.pulse(Unknown Source)
> at com.sun.javafx.tk.Toolkit.lambda$runPulse$28(Toolkit.java:314)
> at com.sun.javafx.tk.Toolkit$$Lambda$134/26908315.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at com.sun.javafx.tk.Toolkit.runPulse(Toolkit.java:313)
> at com.sun.javafx.tk.Toolkit.firePulse(Toolkit.java:340)
> at com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:451)
> at com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:431)
> at com.sun.javafx.tk.quantum.QuantumToolkit.lambda$runToolkit$363(QuantumToolkit.java:298)
> at com.sun.javafx.tk.quantum.QuantumToolkit$$Lambda$40/33541029.run(Unknown Source)
> at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
> at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:114)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:91)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-22965:
---------------------------------------
[~adietish] CDK supports its own implementation of proxy solution. One can use cdk adapter launch configuration to use it. True is that we do not provide any fancy GUI element that would do so for the adapter. Neither we use eclipse proxy definition to pass the params into adapter's launch configuration which would be the same as writing it down manually. Agreeing to close this as won't fix.
> CDK tools should work behind proxy
> ----------------------------------
>
> Key: JBIDE-22965
> URL: https://issues.jboss.org/browse/JBIDE-22965
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.12.0.Final
>
> Attachments: create_proxy-test_env.sh
>
>
> Proxy support has been added in CDK vagrant box and in vagrant-registration plugin.
> We should make sure our CDK tooling supports it too.
> In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/...
> Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982
> + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25
> Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]:
> {noformat}
> lalatenduM: we exepect customers workstation is configured to porixy server
> that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work
> lalatenduM: on a customer worksttaion
> lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information
> lalatenduM: vagrant-registration uses subscription manager for registraton
> lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info
> {noformat}
> in a mail on the 26th of October 2017 "Re: [openshift-sme] CDK: Usage behind proxy":
> {quote}
> The CDK supports a number of methods to apply proxy configuration.
> You can specify a few of these at startup using the “minishift start” command.
> First, you can set the --http-proxy and/or --https-proxy to apply RHEL environment variables.
> For Docker Pulls, you can specify environment variables that are applied to the Docker daemon using the --docker-env flag (HTTP_PROXY, HTTPS_PROXY, NO_PROXY).
> There are additional considerations for builds as well that can be applied. Please see the following document on the proxy considerations:
> https://docs.openshift.com/container-platform/3.6/install_config/http_pro...
> - Andy
> {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-23995) Eclipse Hibernate Connection Password Issue Reverse Code Generation
by Adam J. Griff, Ph.D. (Jira)
[ https://issues.jboss.org/browse/JBIDE-23995?page=com.atlassian.jira.plugi... ]
Adam J. Griff, Ph.D. commented on JBIDE-23995:
----------------------------------------------
I don't know if this issue has been fixed. Have not used it in several years and had found my work around mentioned above. Would be great to hear the bug was fixed to close this bug.
> Eclipse Hibernate Connection Password Issue Reverse Code Generation
> --------------------------------------------------------------------
>
> Key: JBIDE-23995
> URL: https://issues.jboss.org/browse/JBIDE-23995
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.2.Final
> Environment: Eclipse is Neon.2
> MySQL is 5.6.35
> Connector/J is 5.1.40
> Hibernate Tools 5.1.2.v20161121-1143 org.hibernate.eclipse.feature.feature.group JBoss by Red Hat
> Reporter: Adam J. Griff, Ph.D.
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.12.x
>
> Attachments: hibernate_1.png, hibernate_2.png
>
>
> Password is corrupted resulting in a password error when attempting to connect to the database to perform Reverse Code Generation POJO
> [Here is a link to the description on the Hibernate Forum|https://forum.hibernate.org/viewtopic.php?f=1&t=1044013&p=2491457#p...]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-24141) Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-24141?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-24141.
------------------------------
Resolution: Done
> Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component
> ------------------------------------------------------------
>
> Key: JBIDE-24141
> URL: https://issues.jboss.org/browse/JBIDE-24141
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: webservices
> Affects Versions: 4.4.4.AM2, 4.5.0.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: testfailure
> Fix For: 4.12.x
>
>
> *2 Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component:*
> https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
> [Search for Test Failure JIRAs in JBIDE 4.4.4.AM2 for webservices component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...]
> -----
> {code}
> All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.15 sec 2
> {code}
> {code}
> Failed
> org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication
> Failing for the past 2 builds (Since Unstable#74 )
> Took 0.15 sec.
> add description
> Error Message
> Expected: <6>
> but: was <10>
> Stacktrace
> java.lang.AssertionError:
> Expected: <6>
> but: was <10>
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.junit.Assert.assertThat(Assert.java:956)
> at org.junit.Assert.assertThat(Assert.java:923)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication(JaxrsMetamodelChangedProcessorTestCase.java:358)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-24555) Test Failure(s) in JBIDE 4.5.0.AM1 for jst component - org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-24555?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-24555.
------------------------------
Resolution: Done
> Test Failure(s) in JBIDE 4.5.0.AM1 for jst component - org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24555
> URL: https://issues.jboss.org/browse/JBIDE-24555
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jst
> Affects Versions: 4.5.0.AM1
> Reporter: Martin Malina
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: testfailure
> Fix For: 4.12.x
>
>
> *2 Test Failure(s) in JBIDE 4.5.0.AM2 for jst component:*
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> [Search for Test Failure JIRAs in JBIDE 4.5.0.AM1 for jst component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...]
> -----
> {code}
> All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML 0.22 sec 194
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML 1.1 sec 194
> {code}
> {code}
> Failed
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests)
> Failing for the past 194 builds (Since #1 )
> Took 0.22 sec.
> Error Message
> Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15)
> Stacktrace
> junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkHyperlinksInTextEditor(HyperlinkTestUtil.java:203)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinks(DatalistHyperlinkDetectorTest.java:64)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML(DatalistHyperlinkDetectorTest.java:57){code}
> {code}
> Failed
> org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests)
> Failing for the past 194 builds (Since #1 )
> Took 1.1 sec.
> Error Message
> Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14)
> Stacktrace
> junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14)
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkRegionsInTextEditor(HyperlinkTestUtil.java:546)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinkDetector(DatalistHyperlinkDetectorTest.java:53)
> at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML(DatalistHyperlinkDetectorTest.java:47){code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-12283) Unable to connect to SOAP web service in IPv6 environment
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-12283?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-12283:
------------------------------------
I think this can be closed as it is an EAP issue
> Unable to connect to SOAP web service in IPv6 environment
> ---------------------------------------------------------
>
> Key: JBIDE-12283
> URL: https://issues.jboss.org/browse/JBIDE-12283
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream, webservices
> Affects Versions: 3.3.0.Final
> Environment: Two Fedora 17 machines connected to each other with IPv6 protocol, JBDS 5.0.0 GA, EAP 6
> Reporter: Jaroslav Jankovič
> Assignee: Brian Fitzpatrick
> Priority: Blocker
> Labels: jax-ws
> Fix For: 4.1.x, 4.2.x, LATER
>
>
> When I was trying to obtain the content of WSDL file of deployed SOAP WS, an error was thrown in error log and no content could be viewed:
> {code}
> 08:45:31,450 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/prj].[HelloWorld]] (http-/fc00:0:0:0:0:0:0:1%2:8080-1) Servlet.service() for servlet HelloWorld threw exception: javax.servlet.ServletException: Cannot obtain destination for: /prj/HelloWorld
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination(RequestHandlerImpl.java:164)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:81)
> at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:169)
> at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:185)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:113)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-1.jar:1.0.1.Final-redhat-1]
> at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
> at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-2.0.3.GA-redhat-1.jar:2.0.3.GA-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-1.jar:1.0.1.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_32]
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-12283) Unable to connect to SOAP web service in IPv6 environment
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-12283?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-12283:
------------------------------------------
[~jeffmaury], [~jkopriva], [~odockal]: not even sure if we can verify this 7y+ old issue so that we could resolve it. If we can't we could simply set it to LATER?
> Unable to connect to SOAP web service in IPv6 environment
> ---------------------------------------------------------
>
> Key: JBIDE-12283
> URL: https://issues.jboss.org/browse/JBIDE-12283
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream, webservices
> Affects Versions: 3.3.0.Final
> Environment: Two Fedora 17 machines connected to each other with IPv6 protocol, JBDS 5.0.0 GA, EAP 6
> Reporter: Jaroslav Jankovič
> Assignee: Brian Fitzpatrick
> Priority: Blocker
> Labels: jax-ws
> Fix For: 4.1.x, 4.2.x, LATER
>
>
> When I was trying to obtain the content of WSDL file of deployed SOAP WS, an error was thrown in error log and no content could be viewed:
> {code}
> 08:45:31,450 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/prj].[HelloWorld]] (http-/fc00:0:0:0:0:0:0:1%2:8080-1) Servlet.service() for servlet HelloWorld threw exception: javax.servlet.ServletException: Cannot obtain destination for: /prj/HelloWorld
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination(RequestHandlerImpl.java:164)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:81)
> at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:169)
> at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:185)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:113)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-1.jar:1.0.1.Final-redhat-1]
> at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
> at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-2.0.3.GA-redhat-1.jar:2.0.3.GA-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-1.jar:1.0.1.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_32]
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months