[JBossWS] - Error: org.jboss.util.NotImplementedException: getTextConten
by anoop10
Hi,
I was trying to write a SOAP client program using Servlet. When the service method called, I am getting the following error.
16:05:02,236 ERROR [STDERR] org.jboss.util.NotImplementedException: getTextContent
16:05:02,237 ERROR [STDERR] at org.jboss.ws.core.soap.NodeImpl.getTextContent(NodeImpl.java:611)
16:05:02,237 ERROR [STDERR] at org.mobicents.slee.resource.http.LdapSearchServlet.service(LdapSearchServlet.java:85)
16:05:02,237 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
16:05:02,237 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
16:05:02,238 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
16:05:02,238 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
16:05:02,238 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
16:05:02,238 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
16:05:02,238 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
16:05:02,238 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
16:05:02,239 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
16:05:02,239 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
16:05:02,239 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
16:05:02,239 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
16:05:02,239 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
16:05:02,239 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
16:05:02,240 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
16:05:02,240 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
16:05:02,240 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
16:05:02,240 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
16:05:02,240 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619)
The code I have written in Servelt is
SOAPMessage responseSM = connection.call(sm, endpoint);
SOAPPart soapPart = responseSM.getSOAPPart();
SOAPEnvelope soapEnv = soapPart.getEnvelope();
SOAPBody soapBody = soapEnv.getBody();
out.println(soapBody.getFirstChild().getFirstChild().getTextContent());
I am using the above code to print value of a text node and getting the above exception on runtime.
I am using JBOSS 4.2.3GA and JDK 1.6.
Please help me to solve this issue.
Thanks
Anoop
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250290#4250290
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250290
16 years, 1 month
[JBossWS] - Re: Cannot obtain wsdl service
by lucastoledo
Hi there, I am running jboss-4.2.1.GA and I am encountering the exact problem.
I followed the instruction posted in the last reply (copying - jaxb-api.jar - jboss-jaxws.jar - jboss-saaj.jar from client\ to lib\endorsed\ ) and it caused a new type of problem.
Here is the log error:
| 14:31:22,046 ERROR [JmsServerSession] Unexpected error delivering message org.jboss.mq.SpyObjectMess
| age {
| Header {
| jmsDestination : QUEUE.AsyncPlugin
| jmsDeliveryMode : 2
| jmsExpiration : 0
| jmsPriority : 4
| jmsMessageID : ID:6-12506022817341
| jmsTimeStamp : 1250602281734
| jmsCorrelationID: null
| jmsReplyTo : null
| jmsType : null
| jmsRedelivered : false
| jmsProperties : {}
| jmsPropReadWrite: false
| msgReadOnly : true
| producerClientId: ID:6
| }
| }
| javax.ejb.EJBTransactionRolledbackException: java.lang.NoClassDefFoundError: org/jboss/logging/Logger
| at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
| at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
| at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:245)
| at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
| at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
| at $Proxy154.onMessage(Unknown Source)
| at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178)
| at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:891)
| at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170)
| at org.jboss.mq.SpySession.run(SpySession.java:323)
| at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:237)
| at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
| at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
| at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: java.lang.RuntimeException: java.lang.NoClassDefFoundError: org/jboss/logging/Logger
| at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:174)
| at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126)
| ... 17 more
| Caused by: java.lang.NoClassDefFoundError: org/jboss/logging/Logger
| at javax.xml.soap.FactoryLoader.<clinit>(FactoryLoader.java:47)
| at javax.xml.ws.spi.Provider.provider(Provider.java:91)
| at javax.xml.ws.Service.<init>(Service.java:83)
| at com.abm_uk.imswebservice.CurrentCrimesRequest_Service.<init>(CurrentCrimesRequest_Service.java:42)
| at com.beatSystems.nottsPolice.crime.myCrime.CurrentCrimesUtility.getService(CurrentCrimesUtility.java:48)
| at com.beatSystems.mobaq.backend.notts.crime.configuration.CrimeConfigurationManager.getCurrentCrimesClient(CrimeConfigurationManager.java:277)
| at com.beatSystems.mobaq.backend.notts.crime.plugins.NottsMyCurrentCrimesUploadPlugin.processUpload(NottsMyCurrentCrimesUploadPlugin.java:55)
| at com.beatSystems.mobaq.core.plugin.GenericUploadPlugin.handle(GenericUploadPlugin.java:17)
| at com.beatSystems.mobaq.core.bean.PluginHandlerListenerBean.handle(PluginHandlerListenerBean.java:55)
| at com.beatSystems.mobaq.core.bean.PluginHandlerListenerBean.onMessage(PluginHandlerListenerBean.java:45)
| 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:585)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112)
| at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
| ... 24 more
|
Has anyone encounter a similar problem as a result of these changes?
Thanks in advance for replies.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250190#4250190
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250190
16 years, 1 month
[JBossWS] - Re: JBoss WS-Eventing vs JMS-Topic
by sbutt
Sorry for the type in my previous message, from JMS-Notification i meant JMS-Topic framework.
"sbutt" wrote : Hi there,
| I'm planning to implement a data-mining/analysis application (using WS-Eventing framework), which would get some data from a number of third party providers and analyse it.
|
| I'm assuming my analysis application would be an Event Consumer (sink) WS-Client, which would subscribe to Event Producer(source), responsible for third party data providers? Do you think my understanding is correct at this stage?
|
| Actually, my scenario is that I have a number of clients to whom we're sending some requests and in return getting some response. So in nut-shell what i'm looking for is a kind of analysis application, through which I can monitor what was sent to which client and what I got in response(success, error, warning etc etc).
|
| So do you think that with the help of WS-Eventing framework I can take care of the above scenario?
|
| Secondly, I have also read about JMS-Notification framework similarly based upon Producer-Subscriber design pattern. So can anybody suggest, which one is more robust and beneficial over the other?
|
| One good reason I can think about WS-Eventing framework is that the communication is going to be in the form of SOAP, so Event-Consumer endpoint can be implemented in any language be it php, c#, asp etc etc.
|
| In-case of JMS-Notification, it is going to be Java dependent. Is this assumption true and what other reasons there can be to give preference to WS-Eventing over JMS-Notification?
|
| Thanks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250120#4250120
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250120
16 years, 1 month
[JBossWS] - JBoss WS-Eventing vs JMS-Topic
by sbutt
Hi there,
I'm planning to implement a data-mining/analysis application (using WS-Eventing framework), which would get some data from a number of third party providers and analyse it.
I'm assuming my analysis application would be an Event Consumer (sink) WS-Client, which would subscribe to Event Producer(source), responsible for third party data providers? Do you think my understanding is correct at this stage?
Actually, my scenario is that I have a number of clients to whom we're sending some requests and in return getting some response. So in nut-shell what i'm looking for is a kind of analysis application, through which I can monitor what was sent to which client and what I got in response(success, error, warning etc etc).
So do you think that with the help of WS-Eventing framework I can take care of the above scenario?
Secondly, I have also read about JMS-Notification framework similarly based upon Producer-Subscriber design pattern. So can anybody suggest, which one is more robust and beneficial over the other?
One good reason I can think about WS-Eventing framework is that the communication is going to be in the form of SOAP, so Event-Consumer endpoint can be implemented in any language be it php, c#, asp etc etc.
In-case of JMS-Notification, it is going to be Java dependent. Is this assumption true and what other reasons there can be to give preference to WS-Eventing over JMS-Notification?
Thanks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250117#4250117
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250117
16 years, 1 month
Jbossws-users@lists.jboss.org
by The Post Office
The original message was received at Tue, 18 Aug 2009 12:45:35 +0530 from 190.53.221.26
----- The following addresses had permanent fatal errors -----
jbossws-users(a)lists.jboss.org
16 years, 1 month
[JBossWS] - webservive form-like authentication
by fejesjoco
I would like to create a JBossWS webservice with a very specific authentication scheme, it's like securing a webservice like a website with form authentication. We want a login(...) webmethod (or several of them). When a client calls it and the authentication succeeds, we store that information (username, roles) in the session. All other webmethods would be declaratively secured like with @RolesAllowed. I haven't implemented anything yet, I'm only planning now.
I believe that in the endpoint class, I can get a @Resource WebServiceContext, and after that, in the login(...) method I can get the MessageContext, and then the HttpServletRequest, and then the HttpSession. This login(...) method is unsecured, so anyone can call it, we log them in and the client automatically receive a session cookie.
What I don't know how to do is this: I want JBoss to ask me before every webservice method invocation who the currently logged in user/Principal is and what roles they have. In this callback I would look at the session and return to JBoss the information that the login method stores in the session. So if I wanted to call WebServiceContext.getUserPrincipal, the principal would appear there, somehow magically, because there's no setUserPrincipal. And I believe that once a Principal is associated to the current request (or maybe the session, automatically), the @RolesAllowed annotation would work as expected.
Is there any extension point that lets me do this? So far I've only come up with some poor workarounds. I think I could create a GenericSOAPHandler, it knows what I want: it does execute before every request and it does have access to the session in the function handleInbound(MessageContext msgContext). I could throw an exception from there if the session is empty, but that's far from role-based security. Or, naturally, I have access to the session in all of the webmethods, so I could call an isInRole function at the start of every method, but that's much worse than doing the same thing declaratively.
I have no doubt that associating a principal+roles with a session is the only viable way for me. So is it possible? Please don't suggest WS-Security or basic authentication or things like that, requirements say we can't use that, it has to be with sessions+cookies (we're porting the server from .NET, yay, but the clients will have to stay the same).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249952#4249952
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249952
16 years, 1 month
