[JBoss JIRA] Created: (JBWS-2376) Fix deployment macros
by Richard Opalka (JIRA)
Fix deployment macros
---------------------
Key: JBWS-2376
URL: https://jira.jboss.org/jira/browse/JBWS-2376
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-cxf, jbossws-metro, jbossws-native
Affects Versions: jbossws-cxf-3.0.4, jbossws-metro-3.0.4, jbossws-native-3.0.4
Reporter: Richard Opalka
Assignee: Richard Opalka
Fix For: jbossws-native-3.0.5, jbossws-metro-3.0.5, jbossws-cxf-3.0.5
Currently we use the following form of include in patternsets:
<patternset id="jbossws.client.patternset">
<include name="**/FastInfoset.jar"/>
...
</patternset>
This approach is error prone. We should include more specific artifacts,
e.g.:
<patternset id="jbossws.client.patternset">
<include name="**/maven/group/id//FastInfoset.jar"/>
...
</patternset>
This applies mainly to JBossAS thirdparty directory (where stack specific macro is reused).
--
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
16 years
[JBoss JIRA] Created: (JBWS-2398) Webservice not running on jboss 4.2.3
by Swati Singhal (JIRA)
Webservice not running on jboss 4.2.3
-------------------------------------
Key: JBWS-2398
URL: https://jira.jboss.org/jira/browse/JBWS-2398
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: Running jboss 4.2.3 on Windows xp. Updating JBoss from 4.0.2 to 4.2.3
Reporter: Swati Singhal
I am updating my jboss server from version 4.0.2 to 4.2.3. I am not able to access the webservices using jboss 4.2.3.
When i access the same code through jboss 4.0.2 it runs absolutely fine. Here is the exception i get:
Caused by: java.lang.ClassCastException: org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy cannot be cast to org.jboss.invocation.Invoker
The stack trace:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.akc.web.lib.ejb.EjbUtil._createEjbObject(EjbUtil.java:291)
at org.akc.web.lib.ejb.EjbUtil.createEjbObject(EjbUtil.java:261)
at org.akc.web.system.impl.SystemManagerEJBProxy.createEJB(SystemManagerEJBProxy.java:215)
at org.akc.web.system.impl.SystemManagerEJBProxy.getAvailabilityByName(SystemManagerEJBProxy.java:57)
at org.akc.web.system.SystemManagerProxy.getAvailabilityByName(SystemManagerProxy.java:272)
at org.akc.web.dog.service.InternalDogService.getDogInfo(InternalDogService.java:32)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:194)
at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:102)
at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassCastException: org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy cannot be cast to org.jboss.invocation.Invoker
at org.jboss.invocation.InvocationContext.getInvoker(InvocationContext.java:103)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:226)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:169)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86)
at $Proxy204.create(Unknown Source)
... 41 more
--
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
16 years
[JBoss JIRA] Created: (JBWS-2343) Enable tests requiring atp/wsgen on client side
by Alessio Soldano (JIRA)
Enable tests requiring atp/wsgen on client side
-----------------------------------------------
Key: JBWS-2343
URL: https://jira.jboss.org/jira/browse/JBWS-2343
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: jbossws-metro
Reporter: Alessio Soldano
Assignee: Alessio Soldano
The testsuite has excluded tests because of the missing wrapper generator. Once this is available, we can deploy the same testsuite jars on Native and Metro, without requiring users to run an external tool when developing endpoints with bottom-up (java first) strategy.
However Metro still need to generate wrapper beans on client side to invoke the service. In a real world scenario, where client and server do not share classes, users would run wsimport and obtain the required classes from the service contract. Thus no wrapper generation required on client side.
We should anyway be able to run our full testsuite with Metro stack, so we need to somehow enhance our test framework to automatically call wsgen when requiring a give artifact to be deployed before running some tests. This would provide the missing piece on client side for running those tests.
--
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
16 years