June 2009 - jboss-user - Jboss List Archives

[JBossWS] - Re: JBOSS-5.1.0.GA web service client doesn't work ( runtime

by rangalo

This was indeed a missing jars in classpath problem. I had to add following to the classpath: | $ echo $CLASSPATH | jboss_libs/jboss-common-core.jar:jboss_libs/jbossall-client.jar:jboss_libs/jbossws-spi.jar:jboss_libs/jbossws-native-core.jar:jboss_libs/jbossws-native-client.jar::jboss_libs/jaxb-impl.jar:jboss_libs/jboss-xml-binding.jar:jboss_libs/stax-api.jar:jboss_libs/wstx.jar:jboss_libs/jboss-logging-jdk.jar:jboss_libs/jboss-logging-spi.jar:jboss_libs/jbossws-common.jar:jboss_libs/wsdl4j.jar:jboss_libs/mail.jar:jboss_libs/policy.jar:jboss_libs/commons-logging.jar:jboss_libs/javassist.jar:jboss_libs/jboss-remoting.jar | All these libs were from jboss/client But after the client started working, I had following exception in server.log. | 3:29:21,925 ERROR [[HelloBean]] Servlet.service() for servlet HelloBean threw exception | java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441) | at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:87) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:169) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.createSOAPMessage(SOAPFaultHelperJAXWS.java:295) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:256) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:187) | at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:102) | at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:671) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:496) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131) | at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) | 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:235) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) | at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) | at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) | 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:158) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Thread.java:619) | | On client side it looks like following: | $ wsrunclient.sh -cp "dist/hello-client.jar:jboss-generated:lib:$CLASSPATH" com.hardik.mejb.JAXWSClient | http://localhost:8080/hello-ws-hello-ws/HelloBean?WSDL | [Fatal Error] :-1:-1: Premature end of file. | 2: null | I installed JBOSS from jboss-5.1.0.GA-jdk6.zip file. thanks & regards. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240300#4240300 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240300

16 years, 10 months

1
0
0 / 0

[EJB 3.0] - Re: Limit IP access to a session beans (EAR)

by Wolfgang Knauf

Hi, I think XACML could help (I don't know it, just stumbled across this article): http://server.dzone.com/articles/security-features-jboss-510-1 Best regards Wolfgang View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240296#4240296 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240296

16 years, 10 months

1
0
0 / 0

[EJB 3.0] - Re: Limit IP access to a session beans (EAR)

by mikioma

I see... I'm sorry I can't help you further. I don't know much abuout JBoss specific configuration. However, I'll keep an eye on this thread as your question is very interesting :-) Good luck, xmedeko!! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240295#4240295 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240295

16 years, 10 months

1
0
0 / 0

[EJB 3.0] - Re: [URGENT] Deploying an EJB using Metro and persistence

by creaturita

The thing is that the EJB is exposed like a webservice, It is not a webservice which calls an EJB, it is a EJB exposed as a webservice. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240294#4240294 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240294

16 years, 10 months

1
0
0 / 0

[EJB 3.0] - Re: [URGENT] Deploying an EJB using Metro and persistence

by mikioma

I don't know metro... but I don't think it is EJB-aware or EntityManager-aware without some kind of configuration... is it? If you're not using an EAR... I guess you need to configure which EJB you want to call from within your web application (as your web service reside into your web application). I think that deploying everything into a single EAR file makes all the modules within it a single application, so injection has a better chance to work. However, I've never deployed WARs into the same server I deploy EJBs... so I've never tried... Good luck!! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240293#4240293 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240293

16 years, 10 months

1
0
0 / 0

[EJB 3.0] - Re: Limit IP access to a session beans (EAR)

by xmedeko

Well, JEE does not specify this, I was thinking something JBoss specific. Like Tomcat has http://www.jboss.org/community/wiki/LimitAccessToCertainClients View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240290#4240290 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240290

16 years, 10 months

1
0
0 / 0

[JBoss Cache: Core Edition] - Re: Transfered objects during a cluster state transfer event

by galder.zamarreno＠jboss.com

We haven't got such information published in a wiki or documentation but I believe you should be able to figure out what the state is composed of by looking at the code in the different org.jboss.cache.remoting.jgroups.ChannelMessageListener.setState calls that effectively delegate the state handling to org.jboss.cache.statetransfer.DefaultStateTransferManager.setState(). Check this code in the JBossCache version that you're using or preferably, since JBoss Cache is now in maintenance mode, I'd suggest you use Infinispan instead. Note that Infinispan, even though it's a new project, it's based on some code from JBoss Cache, so it's pretty robust already for all features JBoss Cache provided (non blocking state transfer, async/sync replication, mvcc locking...etc). Besides, we have switched from a tree structure to a map and I believe it'll be easier to deal with such structure from a client's perspective. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240288#4240288 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240288

16 years, 10 months

1
0
0 / 0

[EJB 3.0] - Re: Limit IP access to a session beans (EAR)

by mikioma

I don't know J2EE deep enough to be sure... but I don't think you can, I'm affraid. Web applications have concepts like "HttpRequest" with which you can get things like IP addresses... but AFAIK there is no such concept in EJB. Anyway, I think the point in J2EE applications is to grant or deny access through the concepts of authentication, authoritation, users, roles... I don't know of a specific security mechanism in which IP addresses is in mind... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240287#4240287 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240287

16 years, 10 months

1
0
0 / 0

[EJB 3.0] - Re: [URGENT] Deploying an EJB using Metro and persistence

by creaturita

I am not using any EAR, I am deploying the EAR directly, should be an EAR neccesary? I deploy a war with the following: -WebContent -----META-INF -----------MANIFEST.MF WEB-INF ------lib -----------sun-jaxws.xml -----------web.xml In web.xml I have the following: <?xml version="1.0" encoding="UTF-8"?> <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5"> <display-name>GatewayVademecum</display-name> <listener-class>com.sun.xml.ws.transport.http.servlet.WSServletContextListener</listener-class> JAX-WS endpoint - Vademecum <display-name>ServicioVademecum</display-name> <servlet-name>VademecumPort</servlet-name> <servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class> <load-on-startup>1</load-on-startup> <servlet-mapping> <servlet-name>VademecumPort</servlet-name> <url-pattern>/ServicioVademecumService</url-pattern> </servlet-mapping> </web-app> This work in WebLogic, perhaps I am missing something View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240286#4240286 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240286

16 years, 10 months

1
0
0 / 0

[EJB 3.0] - Re: [URGENT] Deploying an EJB using Metro and persistence

by jaikiran

"creaturita" wrote : Hello, | | I am still fighting here with JBoss 5, he is like hulk. | LOL :) "creaturita" wrote : | I have installed EJB and Metro plugins specting to be able to use ejb 3 in a servlet. With JBoss 4 I could not do it. | | Well, I want to deploy an EJB webservice in a war and I am having lots of difficulties: | - It does not resolve @EJB and @PersistenceContext. The wsdl is well formed, but when I call the @ejb does not work. | | It could be a problem with metro? | | Could you please open a thread with the details in the WS metro forum here http://www.jboss.org/index.html?module=bb&op=viewforum&f=275. They might have a better idea whether this is supported or not. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240283#4240283 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240283

16 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user June 2009