[EJB 3.0 Users] - EJB 3.0 and JBoss 5 CR1 : calling a web service
by longbeach
Hi,
I have defined a web service which is a stateless session bean :
| @Stateless
| @WebService(endpointInterface ="com.bla.blabla.DoSomething")
| @Remote(DoSomething.class)
|
| public class DoSomethingBean {
|
| @WebMethod(operationName="DoSomething")
| public boolean go(String t, String n){
| ...
| }
|
| }
|
I call that web service in a main java client :
URL url = new URL("http://127.0.0.1:8085/blabla/DoSomethingBean?wsdl");
| QName qname = new QName("http://services.blabla.com/", "DoSomethingBeanService");
|
| ServiceFactory factory = ServiceFactory.newInstance();
| Service remote = factory.createService(url, qname);
|
| DoSomething dosome = (DoSomething) remote.getPort(DoSomething.class);
| dosome.go("arg1", arg2");
|
http://127.0.0.1:8085/blabla/DoSomethingBean?wsdl works, it points to the WSDL.
I get an error message :
| javax.servlet.ServletException: java.lang.reflect.UndeclaredThrowableException
| org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:515)
| org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:419)
| org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
|
Also :
| cause m�re
|
| java.rmi.RemoteException: Call invocation failed; nested exception is:
| java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
| org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:536)
| org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:277)
| org.jboss.ws.core.jaxrpc.client.PortProxy.invoke(PortProxy.java:156)
|
Does Web services work well with JBoss 5 CR1 ?
Thanks for helping
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262672#4262672
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262672
16 years, 6 months
[JBoss Remoting Users] - Problem with multiple ethernet adapters
by mayankmit2002
Setup
---------
Server Name : Server001
IBM Blade Server
-> Two Ethernet adapters eth0 (100 Mbps) and eth1 (1000 Mbps)
-> eth0: 150.158.73.49
-> eth1: 192.168.200.49
Debian 5 Installed
Jboss 4.2.3
Jboss Remoting 2.4.0 SP1
Jboss Messaging 1.4.2
Host file entry:
| 127.0.0.1 localhost
| 150.158.73.49 Server001 Server001
|
Scenario
-----------
Jboss is bound to "Server001"
lookup Code
| final Properties props = new Properties();
| props.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
| props.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
| props.put("jnp.sotimeout", "2000");
| props.put("jnp.timeout", "2000");
| props.put(Context.PROVIDER_URL, java.lang.System.getProperty("bind.address") + ":1100"); // HA-JNDI port.
|
|
| String partitionName = java.lang.System.getProperty("jboss.partition.name", java.lang.System.getenv("COMPUTERNAME") + "_PARTITION");
| partitionName = partitionName.toUpperCase();
|
| // for auto discovery through partition name
| props.put(NamingContext.JNP_PARTITION_NAME, partitionName);
| props.put(NamingContext.JNP_DISCOVERY_GROUP, "230.0.0.4");// Default
| props.put(NamingContext.JNP_DISCOVERY_PORT, "1102");// Default
| props.put(NamingContext.JNP_DISABLE_DISCOVERY, "false");
Problem
---------
now the problem is, some time we have seen that, Jboss starts normally without any exception and is looking at eth0 but suddently it starts looking up at eth1, thus unable to lookup deployed services.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262663#4262663
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262663
16 years, 6 months