[JBossWS] - Re: trying to access a webservice - not working from either
by rodgerca
Thanks for your reply
I installed JBoss 4.2, I am running the messaging server. I installed the most recent ws files using the ant build in the jbossws-native-2.0.0.GA release. All the right files are now deployed to the default/deploy and messaging/deploy jbossws.sar directories.
I fixed the jboss-xml-binding issue about 3 hours ago by changing the order in which the jars are loaded into my class path in eclipse.
After 5 days solid on this, I now feel I am at the final hurdle: I am now getting the same problem from both the java client and the SOAP UI client:--
Exception in thread "main" java.lang.reflect.UndeclaredThrowableException
at $Proxy0.echo(Unknown Source)
at com.cmmgroup.address.client.EchoClient.main(EchoClient.java:32)
Caused by: java.rmi.RemoteException: Call invocation failed; nested exception is:
java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:536)
at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:277)
at org.jboss.ws.core.jaxrpc.client.PortProxy.invoke(PortProxy.java:151)
... 2 more
Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
at javax.xml.soap.SOAPMessage.setProperty(Unknown Source)
at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:67)
at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:155)
at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:58)
at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:156)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:289)
at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:517)
... 4 more
The release notes for the latest version of jbossws tells me that this issue should be fixed. I understand that getting this error message means that I am not running the right version of jboss-saaj. But I can assure you that I am - everywhere! I've deleted every other saaj jar on my hard drive, including those in the eclipse plug in directories. I've definitely got the right jboss-saaj with the right setProperty() method in my eclipse classpath.
Clutching at straws, I read somewhere about adding the jaxb_api and jaxws-api jars to my JDK and JRE lib/endorsed directories (I am running jdk 6) - but that doesn't seem to make a difference
The bus was late, thank goodness, but I've really got to get the sorted. I've spent way too long on it already....
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066700#4066700
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066700
18Â years, 9Â months
[JBoss Seam] - How to programatically create a seam component in a filter?
by titou09
With seam 1.2.1, is it possible to create a seam component in a servlet filter?
If so how to do it?
In web.xml, I declare a filter after all other filters 9seam, jsf, etc...)
In components.xml:
| <component name="test.utilisateur" auto-create="true" scope="session" class="com.saq.pp.metier.modele.Utilisateur"/>
|
In the servlet filter class, I have:
| public void doFilter(ServletRequest req, ServletResponse resp, FilterChain chain) throws IOException, ServletException {
| chain.doFilter(req, resp);
| Utilisateur cx = (Utilisateur) Component.getInstance("test.utilisateur");
| }
|
This result in the following exception:
| java.lang.IllegalStateException: No application context active
| at org.jboss.seam.Component.forName(Component.java:1577)
| at org.jboss.seam.Component.getInstance(Component.java:1627)
| at org.jboss.seam.Component.getInstance(Component.java:1610)
| at org.jboss.seam.Component.getInstance(Component.java:1604)
| at com.saq.pp.web.filter.FiltreTest.doFilter(FiltreTest.java:70)
| at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
| at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
| at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
| at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:761)
| at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:673)
| at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498)
| at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464)
| at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
| at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744)
| at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1433)
| at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:112)
| at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
| at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
| at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:263)
| at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
| at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
| at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
| at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
| at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
| at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
| at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
| at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
| at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
| at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
|
I have the same results with Component.getInstanceFromFactory()
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066695#4066695
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066695
18Â years, 9Â months