October 2007 - jbossws-users - Jboss List Archives

[JBossWS] - Re: wstool jboss 4.05 vs jboss 4.2.0GA wsdl-java

by alessio.soldano＠jboss.com

"nirre" wrote : then one included in jboss 4.2 - jbossws-1.2.1.GA (build=200704151756) | | I have another problem now. Wstool now (with the above mentioned version) generates "strange array data types" in the jax-rpc file (and it does not generate the corresponding java files) - they where not generated when using the jbossws 1.03 (the one incuded in jboss 4.0.5)... | | At runtime I know get errors like: | [EndpointMetaData] Cannot load class for type: {http://company.com/theIntegration}ArrayOfOpportunityID,com.company.theIntegration.ArrayOfOpportunityID | | and then I get a: | | RemoteException occured when invoking web service method!java.rmi.RemoteException: Call invocation failed; nested exception is: | | java.io.IOException: Could not transmit message | | This seems to me the same as http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120947. I also invite you to create a minimal application reproducing the bug and attaching it to a new tools-jaxrpc jira issue. Then the community might take care of it. Thank you View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094955#4094955 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094955

16 years, 9 months

1
0
0 / 0

[JBossWS] - Re: ClassCastException @ BaseDeserializerFactory.getSpeciali

by alessio.soldano＠jboss.com

Sorry, can't remember of it; moreover as you said, setting the username/pwd into the stub should not cause this. If migrating to a more recent jboss application server and ws stack is not affordable for you, in order to understand what's happening I would suggest you to capture the soap messages being exchanged. This way you might see what is really changing and that could drive you to understand where is the problem. If you still think there's a bug, you can nevertheless create a minimal application reproducing the problem and attach it to a new jira issue, however keep in mind that the team is putting his main effort into the jaxws development, thus your potential issue might have to be handled by the community. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094953#4094953 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094953

16 years, 9 months

1
0
0 / 0

[JBossWS] - Re: jax-rpc/wstools genereate problem

by alessio.soldano＠jboss.com

Starting from some months ago, the JBossWS team is putting his main effort into JAXWS. However, you might create a minimal application reproducing this problem and attach it to a new Jira issue. This way somebody from the community may try to fix the potential bug into the codebase. Apart from this, considering you're dealing with migration issues due to the AS upgrade, I would really suggest you to evaluate switching to jaxws (also upgrading to the latest jbossws release); here http://jbws.dyndns.org/mediawiki/index.php?title=JAX-WS_vs_JAX-RPC you can find a brief introduction explaining why this might be a good idea. Thank you View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094951#4094951 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094951

16 years, 9 months

1
0
0 / 0

[JBossWS] - Re: Problems with installation of jbossws2.0.1 on jboss4.2.1

by alessio.soldano＠jboss.com

http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094907 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094950#4094950 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094950

16 years, 9 months

1
0
0 / 0

[JBossWS] - Re: I don't succeded installing jbossws2.0.1 please help me

by abdujaparov

I have resolved the problem, in the path of jboss42 it lacks a \, in fact I wrote C:\jboss-4.2.1.GA instead C:\\jboss-4.2.1.GA, writing C:\\jboss-4.2.1.GA all works. Thanks to all and excuse me. Bye bye. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094907#4094907 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094907

16 years, 9 months

1
0
0 / 0

[JBossWS] - I don't succeded installing jbossws2.0.1 please help me I ne

by abdujaparov

Hi all, I have been trying for 3 days to install jbossws with jboss42. Before I had jdk6 now I have the jdk5, I have downloaded the jbossws 2.0.1 native and I have followed the instruction but I have this error and I don't know how risolving. The errore is the following: | | BUILD FAILED | C:\jbossws-src-2.0.1.GA\ant-import\build-deploy.xml:84: The following error occu | rred while executing this line: | C:\jbossws-src-2.0.1.GA\ant-import\macros-deploy-native.xml:385: Directory does | not exist:C:\jbossws-src-2.0.1.GA\jboss-4.2.1.GA\lib\endorsed | | Total time: 7 seconds | The path of jboss42 I have setted in ant.propertis is the following: | jboss42.home= C:\jboss-4.2.1.GA | jbossws is the directory C:\jbossws-src-2.0.1.GA The macros-deploy-native.xml:385 is line with *:  | <macrodef name="macro-undeploy-endorsed"> | <attribute name="jbosshome"/> | <sequential> | <delete> * | <fileset dir="@{jbosshome}/lib/endorsed"> | <include name="jaxb-api.jar"/> | <include name="jboss-jaxrpc.jar"/> | <include name="jboss-jaxws.jar"/> | <include name="jboss-saaj.jar"/> | </fileset> | </delete> | </sequential> | </macrodef> | Why does it search jboss-4.2.1.GA\lib\endorsed in the directory of jbossws and not in jboss42 directory? What does I wrong? How can I resolve? I need jbossws, please help me! Thanks to all. Bye Bye View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094890#4094890 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094890

16 years, 9 months

1
0
0 / 0

[JBossWS] - Re: jbossws-2.0.1 released

by ptenn10

Richard, Thanks very much for your response. I downloaded a pure copy of the JBoss AS 4.0.4GA and compared default/conf/standardjboss.xml to our /conf/standardjboss.xml. It appears that in the pure 4.0.4GA, the interceptor is: org.jboss.ws.server.ServiceEndpointInterceptor and we had changed this to org.jboss.ws.integration.jboss.ServiceEndpointInterceptor when we upgraded to jbossws-1.4. Although I wasn't the person on our team who did this upgrade to jbossws-1.4, this is what I can gather based on subversion revision messages. So, as you suggested, I changed the interceptor to org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor in our /conf/standardjboss.xml: | <container-configuration> | <container-name>Standard Stateless SessionBean</container-name> | <call-logging>false</call-logging> | <invoker-proxy-binding-name>stateless-rmi-invoker</invoker-proxy-binding-name> | <container-interceptors> | <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor> | <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor> | <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor> |  | <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor> | <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> | <interceptor transaction="Container">org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor</interceptor> | <interceptor transaction="Container">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor> |  | <interceptor transaction="Bean">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor> | <interceptor transaction="Bean">org.jboss.ejb.plugins.TxInterceptorBMT</interceptor> | <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> | <interceptor transaction="Bean">org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor</interceptor> | <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor> | </container-interceptors> | <instance-pool>org.jboss.ejb.plugins.StatelessSessionInstancePool</instance-pool> | <instance-cache></instance-cache> | <persistence-manager></persistence-manager> | <container-pool-conf> | <MaximumSize>100</MaximumSize> | </container-pool-conf> | </container-configuration> | | <container-configuration> | <container-name>Clustered Stateless SessionBean</container-name> | <call-logging>false</call-logging> | <invoker-proxy-binding-name>clustered-stateless-rmi-invoker</invoker-proxy-binding-name> | <container-interceptors> | <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor> | <interceptor>org.jboss.ejb.plugins.CleanShutdownInterceptor</interceptor> | <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor> | <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor> |  | <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor> | <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> | <interceptor transaction="Container">org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor </interceptor> | <interceptor transaction="Container">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor> |  | <interceptor transaction="Bean">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor> | <interceptor transaction="Bean">org.jboss.ejb.plugins.TxInterceptorBMT</interceptor> | <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> | <interceptor transaction="Bean">org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor </interceptor> | <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor> | </container-interceptors> | <instance-pool>org.jboss.ejb.plugins.StatelessSessionInstancePool</instance-pool> | <instance-cache></instance-cache> | <persistence-manager></persistence-manager> | <container-pool-conf> | <MaximumSize>100</MaximumSize> | </container-pool-conf> | <cluster-config> | <partition-name>${jboss.partition.name:DefaultPartition}</partition-name> | </cluster-config> | </container-configuration> | However, this class is not found either. I get the exception 2007-10-12 15:40:44,728 WARN [org.jboss.ejb.EjbModule] Could not load the org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor interceptor | java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor | Could you tell me which JAR this class (org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor) is supposed to reside in? I've tried going through the JARs inside the jbossws.sar directory, but have not been able to find it. Thanks again for your help! Philip Tenn View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094763#4094763 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094763

16 years, 9 months

1
0
0 / 0

[JBossWS] - Re: Troble Connecting a client to web service

by alessio.soldano＠jboss.com

Hi, could you please provide us some more details (wsdl, SEI, etc). Generally speaking, I would suggest you to upgrade to jbossws 2.0.1.GA and use the jaxws tools to create the SEI and in/out classes that correctly fit the wsdl contract I think you need to remain unchanged. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094713#4094713 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094713

16 years, 9 months

1
0
0 / 0

[JBossWS] - Re: Web seervice with authentication and wsconsume

by alessio.soldano＠jboss.com

Yes, you need to also specify the authMethod and transportGuarantee. You can also take a look at the samples, in particular the jaxws-samples-context features this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094696#4094696 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094696

16 years, 9 months

1
0
0 / 0

[JBossWS] - trouble calling web service

by fjump

HI, i need help please, i got the following problem: when i made a call to the web service, appears the error avax.xml.ws.WebServiceException: java.io.IOException: Could not transmit message org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:317) org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:255) org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164) org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) $Proxy112.update(Unknown Source) com.blackbulltv.settopbox.web.MainMenu.doGet(MainMenu.java:109) javax.servlet.http.HttpServlet.service(HttpServlet.java:697) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) im trying to discover what is the problem but i dont find any solution. this is the web service call here is where i made a call to the web service, extracting the URL from a xml file: BlackBullTvWebServices wsconf = new BlackBullTvWebServices(); String serv = wsconf.getPropertyValue("UpdateServiceURL"); URL url = new URL(serv); QName qname = new QName("urn:com.blackbulltv.server.ws", "UpdateService"); Service service = Service.create(url,qname); Update up = (Update)service.getPort(Update.class); temp = up.update(vVersion,component_name,pType); this is my xml file, that contain the URL of my web service. http://192.168.0.17:8080/com.blackbulltv.server/MenuWs?wsdl urn:com.blackbulltv.server.ws this is the web service client file: @WebServiceClient(name = "MainMenuWsService", targetNamespace = "urn:com.blackbulltv.server.ws", wsdlLocation = "http://localhost:8080/Update/MainMenuWs?wsdl") public class MainMenuWsService extends Service { private final static URL MAINMENUWSSERVICE_WSDL_LOCATION; static { URL url = null; try { url = new URL("http://localhost:8080/Update/MainMenuWs?wsdl"); } catch (MalformedURLException e) { e.printStackTrace(); } MAINMENUWSSERVICE_WSDL_LOCATION = url; } public MainMenuWsService(URL wsdlLocation, QName serviceName) { super(wsdlLocation, serviceName); } public MainMenuWsService() { super(MAINMENUWSSERVICE_WSDL_LOCATION, new QName("urn:com.blackbulltv.server.ws", "MainMenuWsService")); } /** * * @return * returns MainMenuWs */ @WebEndpoint(name = "MainMenuWsPort") public MainMenuWs getMainMenuWsPort() { return (MainMenuWs)super.getPort(new QName("urn:com.blackbulltv.server.ws", "MainMenuWsPort"), MainMenuWs.class); } } View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094556#4094556 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094556

16 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users October 2007