From do-not-reply at jboss.com  Sat Nov  1 07:15:37 2008
From: do-not-reply at jboss.com (majeric)
Date: Sat, 1 Nov 2008 07:15:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to access webservice
Message-ID: <7618045.1225538137091.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, 
I'm new at webservices and have been searching for solution but couldn't find this specific problem anywhere. I'm pretty sure that I'm not the first one with this problem, but anyway.

I have a webservice that works fine on my local machine. I access to it with URL: http://127.0.0.1:8081/taskws/TaskService?wsdl
Web services looks like this:
@Stateless
  | @WebContext(contextRoot="/taskws")
  | @WebService(name = "TaskService", serviceName = "TaskService")
  | public class TaskService implements TaskServiceRemote {
  | //...
  | }

But problem appears when I deploy on my server. I can't acces my web services there. I have an application instaled like this:
in application.xml:
<context-root>/<context-root>
in jboss-web:
<jboss-web>  
  | ...
  | 	<virtual-host>test</virtual-host>
  | 	<context-root>/</context-root>
  | </jboss-web>

and in server.xml: a have a host:
<Host name="test" autoDeploy="false" deployOnStartup="false" deployXML="false">
  | 		<Alias>test.domain.com</Alias>
  | ...
  | 	</Host>

Jboss runs on localhost and I access to jboss via apache mod_jk.

How do I have to configure to have access to this service. 
application works fine if I access test.domain.com.

I appriciate your help.

Uros

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186166#4186166

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186166


From do-not-reply at jboss.com  Sat Nov  1 10:00:41 2008
From: do-not-reply at jboss.com (mignaak)
Date: Sat, 1 Nov 2008 10:00:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: jax-ws soap protocol handler and
	white space.
Message-ID: <16382469.1225548041341.JavaMail.jboss@colo-br-02.atl.jboss.com>

Well, i'm going to try geronimo with axis2.
Hope to have better luck.
Will let you know.
Thanks for the support

Bye

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186172#4186172

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186172


From do-not-reply at jboss.com  Mon Nov  3 01:19:39 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 3 Nov 2008 01:19:39 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Diff. between web.xml and
	web.xml.org?
Message-ID: <12101898.1225693179746.JavaMail.jboss@colo-br-02.atl.jboss.com>

We're rewriting web.xml with our endpoint servlet because there's no support for doing it in memory. This JBoss 4.x issue only.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186294#4186294

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186294


From do-not-reply at jboss.com  Mon Nov  3 08:04:05 2008
From: do-not-reply at jboss.com (RogerSilvaSauro)
Date: Mon, 3 Nov 2008 08:04:05 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - how autheticate JME Client (midlet) on
	jboss server
Message-ID: <28364547.1225717445795.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi people, how are you?
I have a Stateless Bean deployed on a jboss server with some security constrains on its methods declared as web service.

The web service consumer is a midlet client, and as there are security constraints, thus the client needed to authenticate himself on jboss before calling the web service.
Please, Does someone know how to authenticate a midlet client on jboss in order to access a secured web service?

I'm searching for a solution for this problem on google for long time with no success...

I appreciate any help you can give me,
Thanks,
Roger

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186378#4186378

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186378


From do-not-reply at jboss.com  Mon Nov  3 12:18:43 2008
From: do-not-reply at jboss.com (freejohn22)
Date: Mon, 3 Nov 2008 12:18:43 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - EJB client for a Web service
Message-ID: <18423661.1225732723702.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi all!
I'm trying to use an EJB as client for a Web service. Unfortunately I'm having some problems when I'm injecting the WebServiceRef into the EJB.

Here's my code:
This is the WebService in the .war file :

@WebService
  | @SOAPBinding(style = SOAPBinding.Style.RPC)
  | public class POJOWs   implements POJOWsItf
  | {
  |    
  |    @WebMethod
  |    public String echo(String input)
  |    {
  |       return input + " called !";
  |    }
  | }

This is the EJb in the jar file:

@Stateless
  | 
  | public class EJBClient implements EJBClientItf {
  | 	
  | 	
  | 	@WebServiceRef(POJOWs.class)  
  | 	private POJOWs service;
  | 
  | 	public String callWS(String input) {
  | 	 
  | 	System.out.println("EJB called !"); 
  | 	return service.echo(input);  
  | 	 
  | 	
  | 	}
  | }

Now when I try to lookup my EJb and invoke the method callWS :

<%
  |             InitialContext ctx = new InitialContext();
  | 	    com.sample.EJBClientItf ejb = null;
  | 	    ejb = ( com.sample.EJBClientItf)ctx.lookup("StatelessfulExample/EJBClient/remote");
  | 	    String ss = ejb.callWS("hello");
  | 	    out.println(ss);
  | 
  | %>


Here's the error I get:

javax.ejb.EJBException: java.lang.RuntimeException: Unable to inject jndi dependency: env/com.sample.EJBClient/service into property com.sample.EJBClient.service: WebServiceRef type 'class com.sample.POJOWs' is not assignable to javax.xml.ws.Service

How can I fix it ?
thanks a lot
john

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186444#4186444

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186444


From do-not-reply at jboss.com  Mon Nov  3 18:10:33 2008
From: do-not-reply at jboss.com (sreeramrt3)
Date: Mon, 3 Nov 2008 18:10:33 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Unsupported content type:
	application/xml
Message-ID: <1299686.1225753833279.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi

I have a web service client which I use to post a simple Echo message with JBOSS 4.2.2 GA and JBOSSWS-Native-3.0.3 stack. I see a SOAPException due to unsupported content type: application/xml. Could I be missing libraries on the client side which could fix this error and generate the right content type?

Thanks


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186504#4186504

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186504


From do-not-reply at jboss.com  Tue Nov  4 18:30:42 2008
From: do-not-reply at jboss.com (rjdbc)
Date: Tue, 4 Nov 2008 18:30:42 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - How to generate the WSDL at build time
	for EJB3 based web se
Message-ID: <22614515.1225841442646.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am exposing a Stateless Session Bean as a web service using following annotations and would like to capture WSDL during build time. Currently, the wsdl is getting generated at deployment. Is there a way to generate it before deployment for EJB3 based web services?

I am using jbossws-3.0.1-native-2.0.4.GA in Jboss portal 2.6.6GA

Example EJB3 WS:

@Stateless
@WebService( targetNamespace = "http://www.xyz.com/product/services/AdminFacade" )
@SOAPBinding( style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL )
public class AdminFacadeBean implements AdminFacadeLocal, AdminFacadeRemote
{
   //methods here
}

Thanks,
rjdbvc

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186851#4186851

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186851


From do-not-reply at jboss.com  Wed Nov  5 05:00:57 2008
From: do-not-reply at jboss.com (jopersson)
Date: Wed, 5 Nov 2008 05:00:57 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: EJB client for a Web service
Message-ID: <25752616.1225879257240.JavaMail.jboss@colo-br-02.atl.jboss.com>

Is the jndi name present in JNDIView in JMXConsole ?

Does EJBClientItf annotate @Remote ?

If you like you can extend your Web Service with a remote interface also, making EJBClient redundant  ?


  | @Remote
  | public interface POJOWsItf
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186937#4186937

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186937


From do-not-reply at jboss.com  Wed Nov  5 05:06:34 2008
From: do-not-reply at jboss.com (jopersson)
Date: Wed, 5 Nov 2008 05:06:34 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Unsupported content type:
	application/xml
Message-ID: <9598561.1225879594882.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

Client libraries depends on enabled features like ws-security etc.

It is easier to see the problem if you post client and server code snippets along with stack traces for both.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186943#4186943

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186943


From do-not-reply at jboss.com  Wed Nov  5 05:11:53 2008
From: do-not-reply at jboss.com (jopersson)
Date: Wed, 5 Nov 2008 05:11:53 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: how autheticate JME Client (midlet)
	on jboss server
Message-ID: <15939610.1225879913797.JavaMail.jboss@colo-br-02.atl.jboss.com>


If you start with making the ws-client working from a plain JavaSE setup small app ? From there it is maybe easier for you to move to JavaME ?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4186945#4186945

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4186945


From do-not-reply at jboss.com  Thu Nov  6 04:43:56 2008
From: do-not-reply at jboss.com (pxstein)
Date: Thu, 6 Nov 2008 04:43:56 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Diff. between @WebService(name=... and
	@WebService(endpointI
Message-ID: <5461131.1225964636463.JavaMail.jboss@colo-br-02.atl.jboss.com>

Diff. between @WebService(name=... and @WebService(endpointInterface=...  ?

In several tutorials I found different ways of defining a WebService with
annotated Java classes. In some samples web services are annotated like:

@javax.jws.WebService(endpointInterface="aaa)

while others declare them as:

@WebService(name = "bbb", targetNamespace = "http://......")

What is the difference?

Are these declarations Framework specific (Axis vs. JAX-WS) ?
Or are these declarations valid for ALL kind of web services?

Peter

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187243#4187243

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187243


From do-not-reply at jboss.com  Thu Nov  6 09:17:40 2008
From: do-not-reply at jboss.com (will.tatam)
Date: Thu, 6 Nov 2008 09:17:40 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - replacement of REPLACE_WITH_ACTUAL_URL
	when using annotation
Message-ID: <12695572.1225981060308.JavaMail.jboss@colo-br-02.atl.jboss.com>

In the past we used the wstools to create our wsdl and then replaced REPLACE_WITH_ACTUAL_URL with http://REPLACE_WITH_ACTUAL_URL if the server we were going to deploy to was directly accessible.
For servers that were behind a firewall we replace with the actual url we wish to use for the <soap:address location=""/>

We are now using the @WebService annotation. For the directly accessible servers we can use the @WebContext(transportGuarantee="CONFIDENTIAL") but we still need a way to solve the second issue. I have tried setting the virtualHosts param but this appears to have no impact on the wsdl

ideas ?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187356#4187356

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187356


From do-not-reply at jboss.com  Thu Nov  6 12:15:48 2008
From: do-not-reply at jboss.com (AceFrehley)
Date: Thu, 6 Nov 2008 12:15:48 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - wsconsume fails on
	NoClassDefFoundException (AS 4.2.2)
Message-ID: <29184106.1225991748429.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi. I have created a web service using annotations, but when I try to generate the client code I keep getting this exception:

 
  | sudo sh ./wsconsume.sh -k -o ~/wstest/bin/ -s ~/wstest/src/ -p test.ws.client http://myurl:8080/mywebproject/mywebservice?wsdl
  | Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory
  | 

I am using java 1.5, and tools.jar is being added to the classpath, according to the wsconsume.sh script.

Thanks.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187438#4187438

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187438


From do-not-reply at jboss.com  Thu Nov  6 15:57:59 2008
From: do-not-reply at jboss.com (newmanw10)
Date: Thu, 6 Nov 2008 15:57:59 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Create WSDL file using jbossws in
	Eclipse
Message-ID: <26959648.1226005079803.JavaMail.jboss@colo-br-02.atl.jboss.com>

I am running into a problem creating a WSDL file using Eclipse IDE v3.4.  When I go through through the 'bottom up web service' wizard and select JBossWS for my web service runtime and choose a simple web service that I created I get the following erorr:

Error: Could not load class [and]. Did you specify a valid --classpath?

When I hit next on the 'JBoss Web Service Code Generation Configuration' menu.  I have both check boxes checked which are 'Generate WSDL file' and 'Update default web.xml'

I assume that I do not have something setup correctly in Eclipse as far as JBoss is concerened.

Please help I have been struggling with this for over a week and I cannot find anything on the web as to why this is happening.

Thanks,
Billy

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187530#4187530

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187530


From do-not-reply at jboss.com  Thu Nov  6 16:36:58 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 6 Nov 2008 16:36:58 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: wsconsume fails on
	NoClassDefFoundException (AS 4.2.2)
Message-ID: <19047808.1226007418824.JavaMail.jboss@colo-br-02.atl.jboss.com>

Try running it without the "sudo sh". If you run it with sudo, then you get the env vars set up for root, and you might not have JAVA_HOME set for root, in which case you might be getting the GNU-java.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187542#4187542

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187542


From do-not-reply at jboss.com  Thu Nov  6 17:33:25 2008
From: do-not-reply at jboss.com (bschmoll1)
Date: Thu, 6 Nov 2008 17:33:25 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Upgrade jbossws on JBoss EAP 4.2
Message-ID: <28830267.1226010805994.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I'm trying to upgrade the JBossws stack on a JBoss EAP 4.2 server instance. I run the upgrade process and it all seems to work fine until I attempt to invoke a web service on the server. I get th following


  | 2008-11-06 08:52:11,288 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/OnDemandReport].[OnDemandReportBean]] Servlet.service() for servlet OnDem
  | andReportBean threw exception
  | java.lang.NoSuchMethodError: org.jboss.ejb3.stateless.StatelessBeanContext.setWebServiceContext(Ljavax/xml/ws/WebServiceContext;)V
  |         at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3$CallbackImpl.attached(InvocationHandlerEJB3.java:134)
  |         at org.jboss.ejb3.EJBContainerInvocation.setBeanContext(EJBContainerInvocation.java:77)
  |         at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:56)
  |         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |         at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166)
  |         at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:108)
  |         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |         at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
  |         at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:106)
  |         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |         at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
  |         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |         at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
  |         at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  |         at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:103)
  |         at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:219)
  |         at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:476)
  |         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.stack.jbws.EndpointServlet.service(EndpointServlet.java:81)
  |         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  |         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:230)
  |         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
  |         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
  |         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
  |         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
  |         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
  |         at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
  |         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  |         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
  |         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
  |         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
  |         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
  |         at java.lang.Thread.run(Thread.java:619)
  | 

This all works fine on a JBoss 4.2.2 instance, so I'm thinking it's that the EAP version isn't compatible with the new jbossws stacks. Can anyone confirm this?

Thanks,

-Brett

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187556#4187556

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187556


From do-not-reply at jboss.com  Fri Nov  7 05:31:17 2008
From: do-not-reply at jboss.com (eminil)
Date: Fri, 7 Nov 2008 05:31:17 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Samples? Tutorials? There is a lack of
	readable docs!
Message-ID: <16138315.1226053877684.JavaMail.jboss@colo-br-02.atl.jboss.com>

I've been looking into putting our wsdl files into a webservice using JBossWS on JBoss 4.2.3 but the docs are so bad i'm getting a headache!

For example: http://docs.jboss.org/jbossas/getting_started/v4/html/ws.html
There is no explanation AT ALL what the following does:
ant -f jboss-build.xml package-ws
ant -f jboss-build.xml deploy-ws

I would like to put that into our own build script.

So my questions are:

1. From our wsdl files how do we exactly turn it into the java source files. Using wsdl2java yes, but need more info. What do we need to download to get it working on the computer we have installed JBoss on. What do we need to put in PATHS etc.

2. When we have the java files... What do we do now? How do we package it? Can we package it with the rest of our EJB files that we put on the jboss server as an .ear?

JBossWS seriously lack a good tutorial that has links to all referenced build scripts or files.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187651#4187651

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187651


From do-not-reply at jboss.com  Fri Nov  7 06:02:10 2008
From: do-not-reply at jboss.com (Marlboro)
Date: Fri, 7 Nov 2008 06:02:10 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - JBossWS 3.0.3 memory leak
Message-ID: <29992004.1226055730553.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

We are running an EJB3/JBossWS aplication on JBoss 4.2.2 with JBossWS - native 3.0.3. Our application causes JBoss to crash with "out of memory error" under load, and we have memory dump from Java 1.6. After analyze of this dump we suspect JBossWS to cause the memory leak. There are 22942513  instances of class java.util.HashMap$Entry with 367080208 bytes and 58967 instances of class [Ljava.util.HashMap$Entry; with 231301484 bytes. Both HashMap entries contain some data from data type's definitions of our endpoints.

For better understating: our application has two parts. At this moment, both parts are deployed on one server but in the future it will be possible to deploy them on two distinct servers. One part is web service client, second one is web service endpoint. We tested our application with Java 1.5 and also 1.6 but we are able to obtain memory dump only with Java 1.6 . Nevertheless both JVMs have the same behavior - they crash approximately after 48 hours.

Any help will be greatly appreciated. If you will need more data/infos please feel free to contact me.

Thanks,
Vratislav Kuzela


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187660#4187660

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187660


From do-not-reply at jboss.com  Fri Nov  7 06:33:19 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 7 Nov 2008 06:33:19 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Samples? Tutorials? There is a lack
	of readable docs!
Message-ID: <18779733.1226057599646.JavaMail.jboss@colo-br-02.atl.jboss.com>

Have you taken a look at the project documentation? http://jbossws.jboss.org/mediawiki/index.php?title=JBossWS

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187668#4187668

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187668


From do-not-reply at jboss.com  Fri Nov  7 06:57:11 2008
From: do-not-reply at jboss.com (eminil)
Date: Fri, 7 Nov 2008 06:57:11 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Samples? Tutorials? There is a lack
	of readable docs!
Message-ID: <17225719.1226059031025.JavaMail.jboss@colo-br-02.atl.jboss.com>

"alessio.soldano at jboss.com" wrote : Have you taken a look at the project documentation? http://jbossws.jboss.org/mediawiki/index.php?title=JBossWS

Yes found no good examples or easy to follow tutorials.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187680#4187680

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187680


From do-not-reply at jboss.com  Fri Nov  7 07:48:50 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 7 Nov 2008 07:48:50 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Samples? Tutorials? There is a lack
	of readable docs!
Message-ID: <18700445.1226062130309.JavaMail.jboss@colo-br-02.atl.jboss.com>

Perhaps you didn't look carefully ;-)

"eminil" wrote : 1. From our wsdl files how do we exactly turn it into the java source files. Using wsdl2java yes, but need more info. What do we need to download to get it working on the computer we have installed JBoss on. What do we need to put in PATHS etc.

Contract-first (top-down) development:
- the JAXWS tools page: http://jbossws.jboss.org/mediawiki/index.php?title=JBossWS_JAX-WS_Tools
- in particular, the Wsconsume tool's page: http://jbossws.jboss.org/mediawiki/index.php?title=Wsconsume
The tool, which lives in your JBoss installation's bin directory, automatically pulls in all the required libraries, but if you want to know which libraries are required, you can see the classpath declared in its script.

anonymous wrote : 2. When we have the java files... What do we do now? How do we package it? Can we package it with the rest of our EJB files that we put on the jboss server as an .ear?
http://jbossws.jboss.org/mediawiki/index.php?title=JAX-WS_User_Guide#Web_Service_Endpoints

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187688#4187688

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187688


From do-not-reply at jboss.com  Fri Nov  7 07:53:15 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 7 Nov 2008 07:53:15 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.0.3 memory leak
Message-ID: <12363394.1226062395294.JavaMail.jboss@colo-br-02.atl.jboss.com>

For sure more info would help, perhaps further details on the webservice endpoint(s), the contract and the full memory dump.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187689#4187689

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187689


From do-not-reply at jboss.com  Fri Nov  7 07:56:42 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 7 Nov 2008 07:56:42 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Upgrade jbossws on JBoss EAP 4.2
Message-ID: <10725609.1226062602912.JavaMail.jboss@colo-br-02.atl.jboss.com>

You are supposed not to change the webservice stack on a EAP distribution. Please get in touch with your JBoss product contact and explain the problems you need to solve by updating the stack so that you can get the appropriate support.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187691#4187691

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187691


From do-not-reply at jboss.com  Fri Nov  7 08:01:04 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 7 Nov 2008 08:01:04 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Create WSDL file using jbossws in
	Eclipse
Message-ID: <33076239.1226062864252.JavaMail.jboss@colo-br-02.atl.jboss.com>

If this relates the Eclipse tooling provided by JBoss please post it here:
http://www.jboss.com/index.html?module=bb&op=viewforum&f=201
or
http://www.jboss.com/index.html?module=bb&op=viewforum&f=258

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187692#4187692

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187692


From do-not-reply at jboss.com  Fri Nov  7 08:04:03 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 7 Nov 2008 08:04:03 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <13568229.1226063043778.JavaMail.jboss@colo-br-02.atl.jboss.com>

Does this http://jbossws.jboss.org/mediawiki/index.php?title=FAQ#How_does_rewriting_of_the_soap_address_in_WSDL_work.3F address your issue?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187693#4187693

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187693


From do-not-reply at jboss.com  Fri Nov  7 08:07:45 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 7 Nov 2008 08:07:45 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Diff. between @WebService(name=...
	and @WebService(endpo
Message-ID: <12823381.1226063265426.JavaMail.jboss@colo-br-02.atl.jboss.com>

The @WebService annotation is defined by the JAX-WS specifications, so its usage is not framework specific.
The above mentioned ways of declaring a ws endpoint simply differ in providing or not an endpoint interface (which of course can have further annotations).

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187694#4187694

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187694


From do-not-reply at jboss.com  Fri Nov  7 08:18:14 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 7 Nov 2008 08:18:14 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: How to generate the WSDL at build
	time for EJB3 based we
Message-ID: <28780013.1226063894544.JavaMail.jboss@colo-br-02.atl.jboss.com>

Try using the wsprovide tool.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187696#4187696

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187696


From do-not-reply at jboss.com  Fri Nov  7 08:46:26 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 7 Nov 2008 08:46:26 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: jax-ws soap protocol handler and
	white space.
Message-ID: <8330570.1226065586329.JavaMail.jboss@colo-br-02.atl.jboss.com>

Does this still happen with a more recent JBossWS version? Which application server version are you using?
Perhaps you can create a jira issue for this and attach a minimal example reproducing the issue.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187707#4187707

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187707


From do-not-reply at jboss.com  Fri Nov  7 08:47:21 2008
From: do-not-reply at jboss.com (mlange)
Date: Fri, 7 Nov 2008 08:47:21 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Upgrade jbossws on JBoss EAP 4.2
Message-ID: <6311197.1226065641654.JavaMail.jboss@colo-br-02.atl.jboss.com>

We also tried to use the new stack on EAP (4.3). This is not supported unfortunately and gives errors. You have to stick to the old 2.x native stack included.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187708#4187708

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187708


From do-not-reply at jboss.com  Fri Nov  7 08:56:33 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 7 Nov 2008 08:56:33 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Jboss 4.2.2 hangs when after
	deploying a WAR
Message-ID: <13153637.1226066193265.JavaMail.jboss@colo-br-02.atl.jboss.com>

Please file a jira issue for this, if possible with an application reproducing the issue, so that we can work on it.
Thanks

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187714#4187714

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187714


From do-not-reply at jboss.com  Fri Nov  7 09:01:37 2008
From: do-not-reply at jboss.com (mignaak)
Date: Fri, 7 Nov 2008 09:01:37 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: jax-ws soap protocol handler and
	white space.
Message-ID: <17987959.1226066497956.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm using jboss 4.2.3 + jbossws native 3.0.4 ga.

My application in a client to a web service.
Everything worked fine with jboss 4.2.2 and jbossws 2.0.3

After jbossws went to 2.0.4 nothing worked anymore.

The remote server always responds with a java.io.exception:

It seems something is wrong with how jboss connects to the remote service. Notice that the soap message produced by jbossws works fine if run through soapui.

Thanks.

Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Invalid HTTP server response [400] - POST/PUT Must Be Explicitly Terminated. Response: POST/PUT Must Be Explicitly Terminated/400.
	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:348)
	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:137)
	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
	at org.jboss.remoting.Client.invoke(Client.java:1634)
	at org.jboss.remoting.Client.invoke(Client.java:548)
	at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:242)
	... 131 more
Caused by: org.jboss.ws.WSException: Invalid HTTP server response [400] - POST/PUT Must Be Explicitly Terminated
	at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75)
	at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:518)
	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:307)


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187716#4187716

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187716


From do-not-reply at jboss.com  Fri Nov  7 09:02:16 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Fri, 7 Nov 2008 09:02:16 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: How to pass whole ValueObjects as
	parameter to a webserv
Message-ID: <20251636.1226066536326.JavaMail.jboss@colo-br-02.atl.jboss.com>

"pxstein" wrote : Nearly all of the web service examples show on how to pass single input parameters as "string" or "int" to a web service.
  | 
  | But what if I want to pass a whole Java class ValueObject like e.g.
  | 
  | public class MyValueObj {
  |     public String name;
  |     public int value;
  |     protected boolean result;  }
  |     
  | Is there somewhere an example (client and webservice implementation)
  | of passing such more complex ValueObjects to a web service?
  | 
  | Peter
Take a look at the jbossws testsuite, package org.jboss.test.ws.jaxws.samples.advanced.retail for instance.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187717#4187717

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187717


From do-not-reply at jboss.com  Fri Nov  7 10:13:08 2008
From: do-not-reply at jboss.com (will.tatam)
Date: Fri, 7 Nov 2008 10:13:08 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <31154504.1226070788883.JavaMail.jboss@colo-br-02.atl.jboss.com>

nope 

The issue is not the hard coding on the client side

The client being used is asp.net and php

We could "hack" the

${jboss.bind.address}

To have the name of our load balancer rather than the ${jboss.bind.address}  but that is a rather ugly hack


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187744#4187744

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187744


From do-not-reply at jboss.com  Fri Nov  7 11:55:14 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 7 Nov 2008 11:55:14 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Samples? Tutorials? There is a lack
	of readable docs!
Message-ID: <27753425.1226076914798.JavaMail.jboss@colo-br-02.atl.jboss.com>

How about this: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182251

Or this: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=104843

In addition, I have a complete tutorial, but it is not free. I can supply the URL if you like.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187780#4187780

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187780


From do-not-reply at jboss.com  Fri Nov  7 12:51:58 2008
From: do-not-reply at jboss.com (lcompton)
Date: Fri, 7 Nov 2008 12:51:58 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS
	2.0.0 - setProperty must
Message-ID: <15509216.1226080318625.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm having trouble getting JBossWS/JBossAS working in JDK 1.6. I'm aware of the existing bug report....

  https://jira.jboss.org/jira/browse/JBWS-1439

I ran the JBossWS ant script using JDK 1.6 and verified that the following JARs were copied into $JBOSS_HOME/lib/endorsed....
  jaxb-api.jar
  jboss-jaxrpc.jar
  jboss-jaxws.jar
  jboss-saaj.jar

However, I still get exceptions of this sort....
javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
	at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:317)
	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:255)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)

Configuration:
  JDK 1.6.0_10
  JBoss AS 4.2.0.GA
  JBossWS 2.0.0
  Ubuntu 8.10

Unfortunately, upgrading to later versions isn't an option.

Larry

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187795#4187795

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187795


From do-not-reply at jboss.com  Fri Nov  7 13:13:16 2008
From: do-not-reply at jboss.com (tonioc)
Date: Fri, 7 Nov 2008 13:13:16 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Jboss 4.2.2 hangs when after
	deploying a WAR
Message-ID: <7556974.1226081596500.JavaMail.jboss@colo-br-02.atl.jboss.com>

Ok I'll do it.

I was trying to construct a small example that can show this problem, but until know I was not able.

I'll continue working on it.

thanks

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187797#4187797

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187797


From do-not-reply at jboss.com  Sun Nov  9 02:50:28 2008
From: do-not-reply at jboss.com (javaee5)
Date: Sun, 9 Nov 2008 02:50:28 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Not getting instance of Service
	object from a WSDL file.
Message-ID: <29601120.1226217028633.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

How Can I create Object from WSDL in JBoss-4.2.2.GA?

Regards,
Hatami. 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187936#4187936

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187936


From do-not-reply at jboss.com  Sun Nov  9 04:55:05 2008
From: do-not-reply at jboss.com (eminil)
Date: Sun, 9 Nov 2008 04:55:05 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Samples? Tutorials? There is a lack
	of readable docs!
Message-ID: <15790629.1226224505497.JavaMail.jboss@colo-br-02.atl.jboss.com>

"PeterJ" wrote : How about this: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182251
  | 
  | Or this: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=104843
  | 
  | In addition, I have a complete tutorial, but it is not free. I can supply the URL if you like.

We're not using EJB3 so all the annotations and stuff in the webservice classes do not apply as far as i know. We'd like to get it working with our EJB2 implementations.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187939#4187939

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187939


From do-not-reply at jboss.com  Sun Nov  9 05:46:16 2008
From: do-not-reply at jboss.com (eminil)
Date: Sun, 9 Nov 2008 05:46:16 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Samples? Tutorials? There is a lack
	of readable docs!
Message-ID: <15069048.1226227576630.JavaMail.jboss@colo-br-02.atl.jboss.com>

"alessio.soldano at jboss.com" wrote : Perhaps you didn't look carefully ;-)
  | 
  | "eminil" wrote : 1. From our wsdl files how do we exactly turn it into the java source files. Using wsdl2java yes, but need more info. What do we need to download to get it working on the computer we have installed JBoss on. What do we need to put in PATHS etc.
  | 
  | Contract-first (top-down) development:
  | - the JAXWS tools page: http://jbossws.jboss.org/mediawiki/index.php?title=JBossWS_JAX-WS_Tools
  | - in particular, the Wsconsume tool's page: http://jbossws.jboss.org/mediawiki/index.php?title=Wsconsume
  | The tool, which lives in your JBoss installation's bin directory, automatically pulls in all the required libraries, but if you want to know which libraries are required, you can see the classpath declared in its script.
  | 
  | anonymous wrote : 2. When we have the java files... What do we do now? How do we package it? Can we package it with the rest of our EJB files that we put on the jboss server as an .ear?
  | http://jbossws.jboss.org/mediawiki/index.php?title=JAX-WS_User_Guide#Web_Service_Endpoints

I've tried looking carefully :P

These examples seem to be for EJB3 right with annotations and stuff for webservices? What if we are using older EJB2 beans?

Also, prefreably we would like all our webservice building to be inside our build ant script. It is possible to get this onto each developers computer's eclipse installation without having to install jboss on every computer? We have a development server running the jboss. I imagine most developers use this approach.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4187941#4187941

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4187941


From do-not-reply at jboss.com  Mon Nov 10 05:56:04 2008
From: do-not-reply at jboss.com (pallas_athena)
Date: Mon, 10 Nov 2008 05:56:04 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS
	2.0.0 - setProperty m
Message-ID: <32671086.1226314564801.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have the same issues with the following config:
Windows XP
JDK 1.6.0_10
JBoss AS 5.0.0 CR2
JBossWS 3.0.4

I, too, have followed the steps described in https://jira.jboss.org/jira/browse/SOA-984 
and https://jira.jboss.org/jira/browse/JBWS-1439.

So upgrading to newer versions might not be a guarantee for success, either :-/

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188066#4188066

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188066


From do-not-reply at jboss.com  Mon Nov 10 08:49:39 2008
From: do-not-reply at jboss.com (yanivc24)
Date: Mon, 10 Nov 2008 08:49:39 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Replacing the logic that returns the
	corrospoding WS java ob
Message-ID: <27506692.1226324979731.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi 

I am new to JbossWS, I have to say that I very much relate to the message posted at : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=145268
I really feel frustrated. all the given documentation is unstructured properly. and many assumptions are made on the reader without specifying prior knowledge requirements. 

Anyhow, What I'd like to achieve is to be able to have the WS layer instantiate beans that reside on a remote server in order to invoke the required java methods 
I am wondering if there is a class or an interface that I can replace to implement only the logic that returns the required java object to preform the WS opertation. I will implement that class such that is will return remote bean proxy objects. 


I hope I made my question clear.

Many Thanks,

Yaniv

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188120#4188120

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188120


From do-not-reply at jboss.com  Mon Nov 10 09:10:19 2008
From: do-not-reply at jboss.com (will.tatam)
Date: Mon, 10 Nov 2008 09:10:19 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <8656635.1226326219745.JavaMail.jboss@colo-br-02.atl.jboss.com>

no further suggestions ? or still not really understanding our needs ?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188132#4188132

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188132


From do-not-reply at jboss.com  Mon Nov 10 09:37:30 2008
From: do-not-reply at jboss.com (AceFrehley)
Date: Mon, 10 Nov 2008 09:37:30 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: wsconsume fails on
	NoClassDefFoundException (AS 4.2.2)
Message-ID: <3925768.1226327850570.JavaMail.jboss@colo-br-02.atl.jboss.com>

Peter - Thank you *very* much!! That solved the problem.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188142#4188142

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188142


From do-not-reply at jboss.com  Mon Nov 10 12:44:54 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 10 Nov 2008 12:44:54 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <26390356.1226339094409.JavaMail.jboss@colo-br-02.atl.jboss.com>

anonymous wrote : or still not really understanding our needs ?

I agree with this statement. Look at your first post, and then at your second. In the second post you suddenly throw in a lot of information (php and .net clients, load balancer) that was completely missing from the first post. So the first question that comes to my mind is: what else are you not telling us? It is hard to help someone when they have not provided all of the information necessary to provide an answer.

Perhaps a complete example of what you are hoping to achieve and what you are seeing instead would help.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188219#4188219

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188219


From do-not-reply at jboss.com  Mon Nov 10 13:30:12 2008
From: do-not-reply at jboss.com (will.tatam)
Date: Mon, 10 Nov 2008 13:30:12 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <6977236.1226341812785.JavaMail.jboss@colo-br-02.atl.jboss.com>

PeterJ: 

If you re-read my first post, you will see that i already explained that some of our jboss servers are directly accessible and some are not.

This means that for the servers that are directly accessible, using the ${jboss.bind.address} is a reasonable guess when trying to construct the full url for the soap address.

For example

http://123.123.123.123:8080/myapp/mySoapService

or if @WebContext(transportGuarantee="CONFIDENTIAL") then jboss will guess

https://123.123.123.123:8443/myapp/mySoapService

Now, as I have already stated this is not applicable for all servers. If a jboss server is behind a firewall then the bind address might not be publicly accessible.

This leaves a bit of an issue, if you leave true then you would end up with an address like

https://192.168.1.123:8443/myapp/mySoapService

which is unless unless your clients have a VPN in place, in which case the firewall is redundant as you would be side-stepping the firewall by using the VPN tunnel to get behind it !!

The old way was use false. If this by itself then just breaks your service as your wsdl now just contains the litteral value REPLACE_WITH_ACTUAL_URL. To get round this, we had modified our build system so when building copies of our app that were destined for use on our servers that are not directly accessible, we used to replace the REPLACE_WITH_ACTUAL_URL with the correct address as compilation time. We are happy to continue with this model, but are unable to as we have yet to find a way to effect the construction of the soap address within the wsdl that is created at runtime

What client code is being used to consume a given web service is irrelevant as when consuming a soap webservice you need wsdl that defines a url for it to actually perform a given action, which if it it contains a private ip, as per RFC1918 is not going to be much use to you unless you are also inside the same address space. Also the fact that our "firewall" is infact a SSL off-loader is again irrelevant to the construction of the URL

I have found very little in the way of documentation for the virtualHosts option, but this is in effect what we want to define as it is the host part of the url we wish to override (we already use the context to set the filepath aspect of the url)

Can anyone spread any further light on virtualHosts and confirm (or deny) if JBoss AS 4.2.3 supports it's usage ?


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188240#4188240

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188240


From do-not-reply at jboss.com  Mon Nov 10 17:16:58 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 10 Nov 2008 17:16:58 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <27847264.1226355418806.JavaMail.jboss@colo-br-02.atl.jboss.com>

If I understand you correctly, I think that what you are saying is that when a client accesses the wsdl via https://192.168.1.123:8443/myapp/mySoapService?wsdl, that you want the wsdl returned to contain:

<soap:address location='https://192.168.1.123:8443/myapp/mySoapService'/>

but at this time it is returning:

<soap:address location='https://123.123.123.123:8443/myapp/mySoapService'/>

Note I am guessing that 123.123.123.123 is the internally-accessible IP address (that is, the hosts configured IP address) and that 192.168.1.123 is the IP address accessible from outside the firewall (that is, the IP address used by the firewall/router). Even after reading your post several times I am not exactly sure which is the physical IP address and which is the IP address accessible outside the firewall.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188291#4188291

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188291


From do-not-reply at jboss.com  Tue Nov 11 04:28:15 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Tue, 11 Nov 2008 04:28:15 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Samples? Tutorials? There is a lack
	of readable docs!
Message-ID: <30593320.1226395695813.JavaMail.jboss@colo-br-02.atl.jboss.com>

"eminil" wrote : 
  | I've tried looking carefully :P
  | 
  | These examples seem to be for EJB3 right with annotations and stuff for webservices?
Yes, those examples are about what JAXWS specs talk about... both EJB3 and POJO web service endpoints are supported.

anonymous wrote : What if we are using older EJB2 beans?
Did you say this before stating that the doc is not readable??
Anyway, you can refer to the legacy JAX-RPC documentation in this case, which is indeed less rich of examples being about something we don't actively work on since a lot of time.
There are anyway tons of jax-rpc examples in the distribution that you can run as junit test and use as a starting point for your development.
http://jbossws.jboss.org/mediawiki/index.php?title=JAX-RPC_User_Guide

anonymous wrote : Also, prefreably we would like all our webservice building to be inside our build ant script. It is possible to get this onto each developers computer's eclipse installation without having to install jboss on every computer? We have a development server running the jboss. I imagine most developers use this approach.
  | 
Sure that's possible. We even developed a user project generator for getting started easily with your project, but that's for JAX-WS only. See the "Setup your IDE" page on the mediawiki: http://jbossws.jboss.org/mediawiki/index.php?title=Setup_your_IDE
Since you're using old technologies, you'll have to setup your environment on your own, but that almost trivial once you know the libraries you need on client side.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188378#4188378

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188378


From do-not-reply at jboss.com  Tue Nov 11 04:50:34 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Tue, 11 Nov 2008 04:50:34 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Replacing the logic that returns
	the corrospoding WS jav
Message-ID: <18215059.1226397034469.JavaMail.jboss@colo-br-02.atl.jboss.com>

No, your question is not that clear, look at the documentation and samples and see what webservices and jbossws are about and allow you to do.
Regarding the documentation, I can't say the documentation at http://jbossws.jboss.org/mediawiki/index.php?title=JBossWS is perfect, consumable by everybody outside there having no knwoledge at all (of course, the topic is quite complex), however did you really spend some time reading it carefully before saying it's not usable? Did you see there's even a guided tour? Did you look at the samples in the src/bin distribution?
What are the assumptions you refer to?

If something is not clear after reading the docs / trying the samples, you can post specific questions, providing the required details here on the forum and perhaps somebody will think your question is interesting and will be happy to help you. Otherwise there's customer support.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188387#4188387

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188387


From do-not-reply at jboss.com  Tue Nov 11 05:02:26 2008
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Tue, 11 Nov 2008 05:02:26 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS
	2.0.0 - setProperty m
Message-ID: <5782876.1226397746583.JavaMail.jboss@colo-br-02.atl.jboss.com>

"pallas_athena" wrote : I have the same issues with the following config:
  | Windows XP
  | JDK 1.6.0_10
  | JBoss AS 5.0.0 CR2
  | JBossWS 3.0.4
  | 
  | I, too, have followed the steps described in https://jira.jboss.org/jira/browse/SOA-984 
  | and https://jira.jboss.org/jira/browse/JBWS-1439.
  | 
  | So upgrading to newer versions might not be a guarantee for success, either :-/

Did you try using the jdk6 distribution of the AS? Otherwise, could you please double-check again which jars (where they come from) are you using at runtime on client side (you get exceptions on client side, don't you?) ?
We run the whole testsuite with JDK 6 every night (and of course before every release), so this should really work http://jbossws.jboss.org:8180/hudson/job/Native-Core-AS-5.0.0-JDK6/ (<-- this is with AS 5.0.0.CR2 and the current jbossws trunk)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188392#4188392

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188392


From do-not-reply at jboss.com  Tue Nov 11 05:29:59 2008
From: do-not-reply at jboss.com (yanivc24)
Date: Tue, 11 Nov 2008 05:29:59 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Replacing the logic that returns
	the corrospoding WS jav
Message-ID: <22846176.1226399399145.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thanks for the response.

I will try to rephrase the question. basically I have two Jboss servers. one is used as a frontend which receives all the calls from a web browser client. ( http requests and web service calls) the second server is used as a backend to do some business logic and mainly runs EJB components.

in the current landscape environment the second server is located behind a firewall so that it cannot receive http requests or web service calls. (both are HTTP). the frontend server is used for that purpose.

The web service stack is responsible for the translation web service calls into methods calls to the required objects. what I would like to achieve is that the method calls to the required objects will be done on a remote object located on the backend server I previously described. the same way it is being achieved today on our old axis implementation.

In the current web service engine we have we are using AXIS 1.4 which is old but is quite modular. it allowed us to replace the module which is responsible for retrieving the required objects to execute the web method call. what we actually did is that we simply made a lookup from the frontend server to the remote backend and received a proxy object. the proxy object is then used by axis to make the required method calls. so basically what happens is that the frontend server receives the web service call, it then receives a proxy objects which executes the calls on the remote backend server. 

Please let me know if you need some further descriptions.

Regarding the documentation, I took a long look at the documentation including the guided tour( more than a work day) the assumptions that I mentioned were regarding the prior knowledge needed in order to understand the documentation. Even though I understand web services and have experience with implementing and consuming them. I don't understand much of the information provided to a useful degree. 



Many Thanks,

Yaniv

 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188406#4188406

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188406


From do-not-reply at jboss.com  Tue Nov 11 06:31:05 2008
From: do-not-reply at jboss.com (Juergen.Zimmermann)
Date: Tue, 11 Nov 2008 06:31:05 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS
	2.0.0 - setProperty m
Message-ID: <10716761.1226403065485.JavaMail.jboss@colo-br-02.atl.jboss.com>

Don't forget to use the endorsed mechanism for jaxb-api.jar, jbossws-native-*.jar

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188438#4188438

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188438


From do-not-reply at jboss.com  Tue Nov 11 09:00:21 2008
From: do-not-reply at jboss.com (twwwt)
Date: Tue, 11 Nov 2008 09:00:21 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - NullPointerException on combined EJB3
	session bean and JAX-W
Message-ID: <11243849.1226412021636.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,

I'm implementing a class that is both a EJB3 stateless session bean and also exposes itself as a JAX-WS Web service. Below you can see relevant excerpt from the code.

When I want to access the WSDL document from a Web browser I get an NPE, see below. When I remove the EJBContext variable declaration including the @Resource annotiation the exception does not appear.

I'm using JBoss 4.2.3GA and jbossws-cxf-3.0.4.GA.

It seems to me that it is related to CXF but appears only for classes that are both EJBs and JAX-WS Web services. Am I right or did I missed something? Should I try with jbossws-native or jbossws-metro again or would they fail as well?

Regards,
Thorsten




  | 
  | // ...
  | 
  | @Local(BankServiceLocal.class)
  | @Remote(BankServiceRemote.class)
  | @Stateless
  | @TransactionAttribute(TransactionAttributeType.REQUIRED)
  | @WebService(name="BankService", targetNamespace="http://myCompany.com")
  | public class BankServiceImpl implements BankService
  | {
  | 	@PersistenceContext
  | 	protected EntityManager em;
  | 	
  | 	@Resource
  | 	protected EJBContext context;
  | 	
  | 	@WebResult(name = "customer")
  | 	public Customer getCustomerDetails(
  | 		@WebParam(name = "bic") String bic,
  | 		@WebParam(name = "iban") String iban) throws UnknownAccountException
  | 	{
  | 		// ...
  | 	}
  | 
  | // ...
  | 
  | }
  | 



  | 14:35:43,937 INFO  [ServerImpl] Setting the server's publish address to be http://127.0.0.1:8080/dis.ws/BankServiceImpl
  | 14:35:43,968 ERROR [AnnotationProcessor] an AnnotationVisitor (org.apache.cxf.common.injection.ResourceInjector at 151e077) raised an exception on element protected javax.ejb.EJBContext ch.unibas.cs.dbis.dis.jaxws.BankServiceImpl.context.
  | java.lang.NullPointerException
  | 	at javax.naming.InitialContext.getURLScheme(InitialContext.java:269)
  | 	at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:318)
  | 	at javax.naming.InitialContext.lookup(InitialContext.java:392)
  | 	at org.apache.cxf.transport.servlet.ServletContextResourceResolver.resolve(ServletContextResourceResolver.java:62)
  | 	at org.apache.cxf.resource.DefaultResourceManager.findResource(DefaultResourceManager.java:99)
  | 	at org.apache.cxf.resource.DefaultResourceManager.resolveResource(DefaultResourceManager.java:55)
  | 	at org.apache.cxf.common.injection.ResourceInjector.resolveResource(ResourceInjector.java:401)
  | 	at org.apache.cxf.common.injection.ResourceInjector.visitField(ResourceInjector.java:164)
  | 	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:597)
  | 	at org.apache.cxf.common.annotation.AnnotationProcessor.visitAnnotatedElement(AnnotationProcessor.java:131)
  | 	at org.apache.cxf.common.annotation.AnnotationProcessor.processFields(AnnotationProcessor.java:110)
  | 	at org.apache.cxf.common.annotation.AnnotationProcessor.accept(AnnotationProcessor.java:89)
  | 	at org.apache.cxf.common.injection.ResourceInjector.inject(ResourceInjector.java:81)
  | 	at org.apache.cxf.common.injection.ResourceInjector.inject(ResourceInjector.java:76)
  | 	at org.apache.cxf.jaxws.JaxWsServerFactoryBean.injectResources(JaxWsServerFactoryBean.java:217)
  | 	at org.apache.cxf.jaxws.JaxWsServerFactoryBean.init(JaxWsServerFactoryBean.java:168)
  | 	at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:161)
  | 	at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:322)
  | 	at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:244)
  | 	at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:194)
  | 	at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:380)
  | 	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:597)
  | 	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1242)
  | 	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1208)
  | 	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1172)
  | 	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:427)
  | 	at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:249)
  | 	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:155)
  | 	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:246)
  | 	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
  | 	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:291)
  | 	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352)
  | 	at org.jboss.wsf.stack.cxf.CXFServletExt.loadAdditionalConfigExt(CXFServletExt.java:141)
  | 	at org.jboss.wsf.stack.cxf.CXFServletExt.loadBus(CXFServletExt.java:118)
  | 	at org.apache.cxf.transport.servlet.AbstractCXFServlet.init(AbstractCXFServlet.java:86)
  | 	at org.jboss.wsf.stack.cxf.CXFServletExt.init(CXFServletExt.java:73)
  | 	at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
  | 	at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806)
  | 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
  | 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
  | 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
  | 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
  | 	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:157)
  | 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
  | 	at java.lang.Thread.run(Thread.java:619)
  | 
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188463#4188463

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188463


From do-not-reply at jboss.com  Tue Nov 11 13:21:33 2008
From: do-not-reply at jboss.com (will.tatam)
Date: Tue, 11 Nov 2008 13:21:33 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <30945938.1226427693097.JavaMail.jboss@colo-br-02.atl.jboss.com>

There are two totally different setups

123.123.123.123 is the dummy ip for a server that runs on a global ip address

192.168.1.123 is the private ip address of a server sitting behind the unspecified ip address of the firewall

If the client accesses a url of

https://456.456.456.456:8443/myapp/mySoapService?wsdl

they the wsdl should list the location as <soap:address location='https://456.456.456.456:8443/myapp/mySoapService'/>  

ideally it should be HTTP 1.1 compliant, so rather than use a hard coded hostname or ${jboss.bind.address} it builds the url based on the url used for the wsdl request (which is just as simple as stripping the ?wsdl from the end)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188551#4188551

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188551


From do-not-reply at jboss.com  Tue Nov 11 13:54:56 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 11 Nov 2008 13:54:56 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <10662786.1226429696270.JavaMail.jboss@colo-br-02.atl.jboss.com>

anonymous wrote : There are two totally different setups
  | 
  | 123.123.123.123 is the dummy ip for a server that runs on a global ip address
  | 
  | 192.168.1.123 is the private ip address of a server sitting behind the unspecified ip address of the firewall

This is what I though was the case based on the IP addresses themselves (I recognize the subnet 129.168.1.xxx as being the subnet typically used by routers), but your text seemed to indicate the opposite.

anonymous wrote : If the client accesses a url of
  | 
  | https://456.456.456.456:8443/myapp/mySoapService?wsdl
  | 
  | they the wsdl should list the location as <soap:address location='https://456.456.456.456:8443/myapp/mySoapService'/>

You say that it "should list" that location. What location is it giving instead?

anonymous wrote : ideally it should be HTTP 1.1 compliant, so rather than use a hard coded hostname or ${jboss.bind.address} it builds the url based on the url used for the wsdl request (which is just as simple as stripping the ?wsdl from the end)

I do not know what you are saying here. What does HTTP 1.1 compliance have to do with this? What does the text "${jboss.bind.address}" have to do with this? When you say "it builds the url based on the url used for the wsdl request (which is just as simple as stripping the ?wsdl from the end)" are you saying that the soap location you are getting in the wsdl is:

<soap:address location='https://456.456.456.456:8443/myapp/mySoapService'/>

If so, then I am really confused because you earlier said "the wsdl should list the location as...".

So once again I am not sure what it is you are seeing and what it is that you are expecting. Please understand that I am not trying to give you a hard time, I am simply trying to understand what the problem is that you are having.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188570#4188570

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188570


From do-not-reply at jboss.com  Tue Nov 11 14:15:18 2008
From: do-not-reply at jboss.com (will.tatam)
Date: Tue, 11 Nov 2008 14:15:18 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <22256092.1226430918117.JavaMail.jboss@colo-br-02.atl.jboss.com>

please read http://www.jboss.org/community/docs/DOC-12519 as this is basically the same problem as that of the creation of RMI stubs

This document details the use of these attributes to ensure that jndi returns the correct url for rmi invocations, just in the same way as the wsdl needs to return the correct url for soap invocations

    -Djava.rmi.server.hostname=<external_host_name>
    -Djava.rmi.server.useLocalHostname=true

In both cases, you are making a call to a given address, which is then forwarded on the the real jboss server, which is on a different address. When jboss is then creating anything that gives any kind or addressing details, by default it guesses it should use it's own address as it's unaware of the publicly accessible address.

The comment about HTTP 1.1 is that jboss should never be guessing the value for url in the first place. when the call for the WSDL is made, the HTTP connection provides the hostname as well as the filepath that was requested, this can then be used to build the response.

i,e

Current model

https://${webServiceHost}:${webServiceSecurePort}/${path.to.sevice}

where webServiceHost and webServiceSecurePort are hard coced values in WSServerConfig


Ideal Model

https://${http.request.hostname}:${http.request.port}/${path.to.sevice}

where the http.request values are populated based on the HTTP headers as part of the call for the WSDL


e.g

if I call https://myserver1.cust1,example.com:8443/myservice?wsl then the soap location should come back as https://myserver1.cust1,example.com:8443/myservice

if i have a dns record so that soap.example.com resolves to a http load balancer the if i call https://soap.example.com/myservice?wsdl then  i get back a location of https://soap.example.com/myservice no matter whether it goes to myserver1.cust1,example.com, myserver2.cust1,example.com or even myserver9.cust4,example.com



As i say, this is the ideal. I would be happy with the old method whereby i hard-code the <soap:address location=''/> within the automatically created WSDL

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188573#4188573

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188573


From do-not-reply at jboss.com  Tue Nov 11 22:03:22 2008
From: do-not-reply at jboss.com (Grid.Qian)
Date: Tue, 11 Nov 2008 22:03:22 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - the generated java file has errors when
	using wsprovide
Message-ID: <12070213.1226459002405.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi guys,
I used wsprovide in the bin folder of jboss as 4.2.2GA to generate wsdl and java files.
the class is :
package echo;
  | 
  | @javax.jws.WebService
  | public class Echo
  | {
  |    public String echo(String input)
  |    {
  |       return input;
  |    }
  | }

the command line : wsprovide.bat -ktw echo.Echo 

the generated files have a wsdl and two java files.
A java file is : EchoResponse.java

  | package echo.jaxws;
  | 
  | import javax.xml.bind.annotation.XmlAccessType;
  | import javax.xml.bind.annotation.XmlAccessorType;
  | import javax.xml.bind.annotation.XmlElement;
  | import javax.xml.bind.annotation.XmlRootElement;
  | import javax.xml.bind.annotation.XmlType;
  | 
  | @XmlRootElement(namespace = "http://echo/", name = "echoResponse")
  | @XmlType(namespace = "http://echo/", name = "echoResponse")
  | @XmlAccessorType(XmlAccessType.FIELD)
  | public class EchoResponse {
  | 
  |     @XmlElement(namespace = "", name = "return")
  |     private String return;
  | 
  |     public String getReturn() {
  |         return this.return;
  |     }
  | 
  |     public void setReturn(String return) {
  |         this.return = return;
  |     }
  | 
  | }


the return is key of java, but in the java file , return is used to the name of a variable. This is big issue.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188640#4188640

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188640


From do-not-reply at jboss.com  Wed Nov 12 01:16:05 2008
From: do-not-reply at jboss.com (Marlboro)
Date: Wed, 12 Nov 2008 01:16:05 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.0.3 memory leak
Message-ID: <16540532.1226470565918.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi Alessio,

I'm sorry for the delay. The endpoints are part of web layer of our application. I will send you both wsdl files via email, and also I will send you link to the web page with JHat result because the memory dump is 1.17GB large. Do you need more data or these are sufficient?

Thanks,
Vratislav Kuzela

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188655#4188655

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188655


From do-not-reply at jboss.com  Wed Nov 12 05:41:00 2008
From: do-not-reply at jboss.com (twwwt)
Date: Wed, 12 Nov 2008 05:41:00 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: NullPointerException on combined
	EJB3 session bean and J
Message-ID: <30924626.1226486460823.JavaMail.jboss@colo-br-02.atl.jboss.com>

Meanwhile, I tried it with JBossWS-Native-3.0.4.GA and it works!

-- Thorsten

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188734#4188734

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188734


From do-not-reply at jboss.com  Wed Nov 12 10:33:36 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Wed, 12 Nov 2008 10:33:36 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: the generated java file has errors
	when using wsprovide
Message-ID: <3262047.1226504016559.JavaMail.jboss@colo-br-02.atl.jboss.com>

Try adding @WebMethod to the echo method.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188821#4188821

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188821


From do-not-reply at jboss.com  Wed Nov 12 10:53:31 2008
From: do-not-reply at jboss.com (MrGuy)
Date: Wed, 12 Nov 2008 10:53:31 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Sigining a SOAP message using the
	enveloped-signature transf
Message-ID: <245738.1226505211607.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have an application that needs to consume a webservice. I've generated the client stubs with wsconsume, and I've configured most of the security settings our partner requires ( username tokens, and a signature ). However, the webservice provider requires that the SOAP envelope be signed using the enveloped-signature transform, and I can't seem to track down any information on how to do that. It _seems_ to be the sort of thing that would be configured in jboss-wsse-client.xml, but I don't see any reference to it in the xsd. If someone could point me in the right direction for this, even just let me know what documentation to look at, I would be grateful.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188829#4188829

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188829


From do-not-reply at jboss.com  Wed Nov 12 11:42:27 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Wed, 12 Nov 2008 11:42:27 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Sigining a SOAP message using the
	enveloped-signature tr
Message-ID: <14428944.1226508147985.JavaMail.jboss@colo-br-02.atl.jboss.com>

Does the WS-Security section of the docs help: http://jbossws.jboss.org/mediawiki/index.php?title=JAX-WS_User_Guide#WS-Security

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188850#4188850

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188850


From do-not-reply at jboss.com  Wed Nov 12 12:07:21 2008
From: do-not-reply at jboss.com (MrGuy)
Date: Wed, 12 Nov 2008 12:07:21 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Sigining a SOAP message using the
	enveloped-signature tr
Message-ID: <13105203.1226509641496.JavaMail.jboss@colo-br-02.atl.jboss.com>

Unfortunately, the WS-Security documentation hasn't helped with the particular problem. It was very helpful in getting the WS-Security set up initially, and working from there I created the following jboss-wsse-client.xml file:


  | <jboss-ws-security  xmlns="http://www.jboss.com/ws-security/config" 
  |                                   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  |                                   xsi:schemaLocation="http://www.jboss.com/ws-security/config 
  |                                   http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">
  | 	<key-store-file>META-INF/keystores/zcg.keystore</key-store-file>
  | 	<key-store-password>zcgstore</key-store-password>
  | 	<trust-store-file>META-INF/keystores/zcg.truststore</trust-store-file>
  | 	<trust-store-password>zcgstore</trust-store-password>
  | 	<config>
  | 		<username/>
  | 		<sign type="x509v3" alias="bandwidth.com">
  | 			<targets>
  | 				<target type="qname">{http://schemas.xmlsoap.org/soap/envelope/}Envelope</target>
  | 			</targets>
  | 		</sign>
  | 	</config>
  | </jboss-ws-security>

Which signs the full SOAP envelope:

  | <env:Envelope wsu:Id='element-2-1226509117041-2045010446' xmlns:env='http://schemas.xmlsoap.org/soap/envelope/' xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'>
  | ...
  | <ds:Reference URI='#element-2-1226509117041-2045010446' xmlns:ds='http://www.w3.org/2000/09/xmldsig#'>
  | 

But it still lists the Transform Algorithm as XML Exclusive Canonicalization:


  |        <ds:Transform Algorithm='http://www.w3.org/2001/10/xml-exc-c14n#' xmlns:ds='http://www.w3.org/2000/09/xmldsig#'/>
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188863#4188863

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188863


From do-not-reply at jboss.com  Wed Nov 12 15:40:23 2008
From: do-not-reply at jboss.com (lcompton)
Date: Wed, 12 Nov 2008 15:40:23 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS
	2.0.0 - setProperty m
Message-ID: <23775256.1226522423786.JavaMail.jboss@colo-br-02.atl.jboss.com>

I solved my problem. Here's a synopsis of the winning configuration:

1. Configured JBoss via the ant script in "jbossws-native-2.0.0". Ended up with the following in "$JBOSS_HOME/lib/endorsed":
- jaxb-api.jar
- jboss-jaxrpc.jar
- jboss-jaxws.jar
- jboss-saaj.jar
- serializer.jar
- xalan.jar
- xercesImpl.jar

2. Added the same files to "$JAVA_HOME/jre/lib/endorsed", which allowed my standalone web service client to work.

Note that I tried every permutation of "endorsed" directories and "java.endorsed.dirs" settings and this is the ONLY configuration that worked.

Larry

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188924#4188924

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188924


From do-not-reply at jboss.com  Wed Nov 12 19:10:11 2008
From: do-not-reply at jboss.com (bschmoll1)
Date: Wed, 12 Nov 2008 19:10:11 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <5024030.1226535011168.JavaMail.jboss@colo-br-02.atl.jboss.com>

I've been recently struggling with the same issue. Apache operates as a front-end for our JBoss server which host several apps, one of which is a web service. 

Look at the:
../deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml


  |   <bean name="ServiceEndpointManager" class="org.jboss.ws.core.server.ServiceEndpointManager">
  | 
  |     <!--
  |         The WSDL, that is a required deployment artifact for an endpoint, has a <soap:address>
  |         element which points to the location of the endpoint. JBoss supports rewriting of that SOAP address.
  | 
  |         If the content of <soap:address> is a valid URL, JBossWS will not rewrite it unless 'alwaysModifySOAPAddress' is true.
  |         If the content of <soap:address> is not a valid URL, JBossWS will rewrite it using the attribute values given below.
  | 
  |         If next line (webServiceHost) is commented, JBossWS uses requesters protocolo, host and port when rewriting the <soap:address>.
  |     -->
  | <!--    <property name="webServiceHost">192.168.1.101</property> -->
  |     <property name="alwaysModifySOAPAddress">true</property>
  | 
  |     <!--
  |       Set these properties to explicitly define the ports that will be used for rewriting the SOAP address.
  |       Otherwise the ports will be identified by querying the list of installed connectors.
  |       If multiple connectors are found the port of the first connector is used.
  |       <property name="webServiceSecurePort">8443</property>
  |       <property name="webServicePort">8080</property>
  |     -->
  | 

The webServiceHost property should be commented out. I believe this is what your looking for.



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188943#4188943

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188943


From do-not-reply at jboss.com  Thu Nov 13 04:05:41 2008
From: do-not-reply at jboss.com (pallas_athena)
Date: Thu, 13 Nov 2008 04:05:41 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS
	2.0.0 - setProperty m
Message-ID: <30861901.1226567141331.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thank you Alessio and Juergen for the suggestions, you put me on the right track! :)

Yes, I was using the jdk6 distribution of the application server and the endorsed mechanism, but the client was using jars from the %JBOSS_HOME%/client folder. As soon as the client used the jars from the /lib/endorsed folder, the error disappeared.

Just out of curiosity, what is the difference between the /client and the /lib/endorsed jars? The files seem to have exactly the same size, which is why I assumed they were identical.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188996#4188996

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188996


From do-not-reply at jboss.com  Thu Nov 13 06:53:13 2008
From: do-not-reply at jboss.com (will.tatam)
Date: Thu, 13 Nov 2008 06:53:13 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <29890532.1226577193462.JavaMail.jboss@colo-br-02.atl.jboss.com>

what happens if you comment out the webServiceHost ? does it then use the HOST value of the HTTP 1.1 request ?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189045#4189045

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189045


From do-not-reply at jboss.com  Thu Nov 13 11:07:33 2008
From: do-not-reply at jboss.com (bschmoll1)
Date: Thu, 13 Nov 2008 11:07:33 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <24526091.1226592453611.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes it uses the inbound http HOST value. Though I'm having "issues" with getting the correct port specified, currently the wsdl is showing

  |  <soap:address location="http://<www.blah.com>:-1/myservice"/>
  | 

No idea how it's coming up with -1, I tried setting the "webServicePort" in the property file to 80, but it still comes up as -1. 

So if you find a work-around to that, I'd appreciate it if you could post it.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189142#4189142

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189142


From do-not-reply at jboss.com  Thu Nov 13 11:13:38 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 13 Nov 2008 11:13:38 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <15812588.1226592819259.JavaMail.jboss@colo-br-02.atl.jboss.com>

Try uncommenting the webServiceHost, setting the value to the IP address used outside the firewall. This example uses the IP address you identified as being the one that outside clients use:

  <bean name="ServiceEndpointManager" class="org.jboss.ws.core.server.ServiceEndpointManager">
  |     <!--
  |      ---comment removed--
  |     -->
  |     <property name="webServiceHost">123.123.123.123</property>
  |     <property name="alwaysModifySOAPAddress">true</property>

Let us know if this fixes the problem.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189145#4189145

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189145


From do-not-reply at jboss.com  Thu Nov 13 11:27:37 2008
From: do-not-reply at jboss.com (will.tatam)
Date: Thu, 13 Nov 2008 11:27:37 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <9667469.1226593657091.JavaMail.jboss@colo-br-02.atl.jboss.com>

This works, but it's still a hack

There is no reason at all to use a hard coded hostname unless you are looking to support ancient HTTP 1.0 clients, of which given SOAP comes years after 1.1 was released, I'm pretty sure all client support 1.1

Also this hack does not work as well as the way I used to do it as this will still re-write the url to include a port number, where my old method defined the full url so the access address doesn't have the nasty 8443 in there that can cause issues for clients accessing who might be behind firewalls

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189153#4189153

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189153


From do-not-reply at jboss.com  Thu Nov 13 11:47:44 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 13 Nov 2008 11:47:44 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <27659646.1226594864108.JavaMail.jboss@colo-br-02.atl.jboss.com>

Maybe someone from the JBoss Web Services team could comment on the HTTP 1.0 vs. 1.1 issue and if there is a 1.1-compliant mechanism for doing this, or if one is planned, or if will.tatum should open a JIRA to get one implemented?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189165#4189165

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189165


From do-not-reply at jboss.com  Thu Nov 13 17:32:20 2008
From: do-not-reply at jboss.com (eminil)
Date: Thu, 13 Nov 2008 17:32:20 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Help setting up a ws
Message-ID: <20765257.1226615540609.JavaMail.jboss@colo-br-02.atl.jboss.com>

Suppose we have an EJB3 defined with

@Stateless
@WebService

It all works as it should. Connecting to the ejb seems fine. And the ws shows up in the jboss jmx console.

However, suppose the EJB methods use more complex arguments than Strings. Does this work automatically or how do we configure it somehow? I got the impression only Strings as arguments to the ejb methods would work with ws default...

Previously when using axis we used a schema .xsd file where all the types were configured (and converted to java files with wsdl2java).

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189249#4189249

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189249


From do-not-reply at jboss.com  Thu Nov 13 18:40:59 2008
From: do-not-reply at jboss.com (Juergen.Zimmermann)
Date: Thu, 13 Nov 2008 18:40:59 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: JDK 1.6.0_10/JBoss4.2.0.GA/JBossWS
	2.0.0 - setProperty m
Message-ID: <23724653.1226619659816.JavaMail.jboss@colo-br-02.atl.jboss.com>

"Endorsed" is described at http://java.sun.com/javase/6/docs/technotes/guides/standards.

JDK 6 ships with an (internal) implementation of JAXB, and JBoss ships its own implementation of JAXB which should be used instead of the one of JDK.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189253#4189253

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189253


From do-not-reply at jboss.com  Fri Nov 14 06:38:56 2008
From: do-not-reply at jboss.com (eminil)
Date: Fri, 14 Nov 2008 06:38:56 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: How to generate the WSDL at build
	time for EJB3 based we
Message-ID: <15360752.1226662736506.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hmm, i have the same question.

But is it really necessary to use the wsprovide tool. From the wiki it says:
anonymous wrote : 
  | A JSE or EJB3 deployment can be built using this class, and it is the only Java code needed to deploy on JBossWS. The WSDL, and all other Java artifacts called "wrapper classes" will be generated for you at deploy time. This actually goes beyond the JAX-WS specification, which requires that wrapper classes be generated using an offline tool. The reason for this requirement is purely a vender implementation problem, and since we do not believe in burdening a developer with a bunch of additional steps, we generate these as well. However, if you want your deployment to be portable to other application servers, you will unfortunately need to use a tool and add the generated classes to your deployment.
  | 
  | This is the primary purpose of the wsprovide tool, to generate portable JAX-WS artifacts. Additionally, it can be used to "provide" the abstract contract (WSDL file) for your service. This can be obtained by invoking wsprovide using the "-w" option: 

>From which i get the impression i would not need to use any other tools...
Or is it so that the CLIENT will need the generated classes from wsprovide to be able to use the webservice?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189349#4189349

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189349


From Paul.WOODWARD at rbs.com  Fri Nov 14 08:48:31 2008
From: Paul.WOODWARD at rbs.com (Paul.WOODWARD at rbs.com)
Date: Fri, 14 Nov 2008 13:48:31 +0000
Subject: [jbossws-users] Classloader problem in WSDLDefinitionsFactory
Message-ID: <B1F2861AED068344B72C4AA018B6F54A022503C203EA@LONMC01012.rbsres07.net>

Hi Guys,

I have a problem - org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse() has the following line:

WSDLFactory wsdlFactory = WSDLFactory.newInstance(JBossWSDLFactoryImpl.class.getName();

This makes it use the system classloader to search for the WSDL factory implementation which breaks when it is used inside a container which provides a different classloader. Is there a good reason for this or would it be possible to replace it with :

WSDLFactory wsdlFactory = WSDLFactory.newInstance(JBossWSDLFactoryImpl.class.getName(), getClass().getClassLoader());

Thanks, Paul

***********************************************************************************
The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. 
Authorised and regulated by the Financial Services Authority 
 
This e-mail message is confidential and for use by the 
addressee only. If the message is received by anyone other 
than the addressee, please return the message to the sender 
by replying to it and then delete the message from your 
computer. Internet e-mails are not necessarily secure. The 
Royal Bank of Scotland plc does not accept responsibility for 
changes made to this message after it was sent. 

Whilst all reasonable care has been taken to avoid the 
transmission of viruses, it is the responsibility of the recipient to 
ensure that the onward transmission, opening or use of this 
message and any attachments will not adversely affect its 
systems or data. No responsibility is accepted by The 
Royal Bank of Scotland plc in this regard and the recipient should carry 
out such virus and other checks as it considers appropriate. 
Visit our websites at: 
www.rbs.com
www.rbs.com/gbm
www.rbsgc.com
***********************************************************************************




From do-not-reply at jboss.com  Fri Nov 14 09:01:19 2008
From: do-not-reply at jboss.com (raheemch)
Date: Fri, 14 Nov 2008 09:01:19 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - getting errors while starting JBoss
	Portal 2.7.0 server
Message-ID: <26613848.1226671279832.JavaMail.jboss@colo-br-02.atl.jboss.com>

i have downloaded JBoss Portal 2.7.0 GA and started the server by clicking run.bat file in bin directory. I am getting following errors:

17:54:19,593 INFO  [TomcatDeployer] deploy, ctxPath=/portal-wsrp, warUrl=.../dep
loy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.war/
17:54:46,078 ERROR [MainDeployer] Could not start deployment: file:/D:/jboss-por
tal-2.7.0.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.
war/
org.jboss.ws.metadata.wsdl.WSDLException: javax.wsdl.WSDLException: WSDLExceptio
n: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.ConnectExce
ption: Connection timed out: connect
        at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsF
actory.java:154)
        at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(Service
MetaData.java:295)
        at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCServerMetaDataBuilder.buil
dMetaData(JAXRPCServerMetaDataBuilder.java:97)
        at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(Unifi
edMetaDataDeploymentAspect.java:56)
        at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy
(DeploymentAspectManagerImpl.java:118)
        at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDep
loyerHook.java:97)
        at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInt
erceptor.java:90)
        at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.
start(SubDeployerInterceptorSupport.java:188)
        at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce
ptor.java:95)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy201.start(Unknown Source)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.addDeployer(MainDeployer.java:368)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy199.addDeployer(Unknown Source)
        at org.jboss.web.tomcat.service.JBossWeb.startService(JBossWeb.java:517)

        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
        at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
        at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor
.java:97)
        at org.jboss.deployment.SubDeployerInterceptor.invokeNext(SubDeployerInt
erceptor.java:124)
        at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce
ptor.java:109)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        at org.jboss.system.ServiceController.start(ServiceController.java:435)
        at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy4.start(Unknown Source)
        at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
        at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy9.deploy(Unknown Source)
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:421)
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:634)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:263)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
bstractDeploymentScanner.java:336)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
        at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy4.start(Unknown Source)
        at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy5.deploy(Unknown Source)
        at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
        at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
        at org.jboss.Main.boot(Main.java:200)
        at org.jboss.Main$1.run(Main.java:508)
        at java.lang.Thread.run(Thread.java:619)
Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Canno
t extract schema definition: java.net.ConnectException: Connection timed out: co
nnect
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:3
94)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:4
16)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:4
16)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.j
ava:178)
        at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsF
actory.java:128)
        ... 129 more
Caused by: java.net.ConnectException: Connection timed out: connect
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.Socket.connect(Socket.java:519)
        at java.net.Socket.connect(Socket.java:469)
        at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:500)
        at sun.net.www.http.HttpClient.(HttpClient.java:233)
        at sun.net.www.http.HttpClient.New(HttpClient.java:306)
        at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLC
onnection.java:799)
        at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConne
ction.java:747)
        at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection
.java:658)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
nection.java:981)
        at java.net.URL.openStream(URL.java:1009)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.handleSchemaImports(WSDL11Reader
.java:588)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.handleSchemaImports(WSDL11Reader
.java:589)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processSchemaInclude(WSDL11Reade
r.java:560)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:3
85)
        ... 133 more
17:54:46,218 ERROR [MainDeployer] DeploymentException while trying to deploy a p
ackage with a new deployer
org.jboss.deployment.DeploymentException: Could not create deployment: file:/D:/
jboss-portal-2.7.0.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/por
tal-wsrp.war/; - nested throwable: (org.jboss.ws.metadata.wsdl.WSDLException: ja
vax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Cannot extract sch
ema definition: java.net.ConnectException: Connection timed out: connect)
        at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException
(DeploymentException.java:53)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1050)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.addDeployer(MainDeployer.java:368)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy199.addDeployer(Unknown Source)
        at org.jboss.web.tomcat.service.JBossWeb.startService(JBossWeb.java:517)

        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
        at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
        at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor
.java:97)
        at org.jboss.deployment.SubDeployerInterceptor.invokeNext(SubDeployerInt
erceptor.java:124)
        at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce
ptor.java:109)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        at org.jboss.system.ServiceController.start(ServiceController.java:435)
        at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy4.start(Unknown Source)
        at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
        at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy9.deploy(Unknown Source)
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:421)
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:634)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:263)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
bstractDeploymentScanner.java:336)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
        at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy4.start(Unknown Source)
        at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy5.deploy(Unknown Source)
        at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
        at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
        at org.jboss.Main.boot(Main.java:200)
        at org.jboss.Main$1.run(Main.java:508)
        at java.lang.Thread.run(Thread.java:619)
Caused by: org.jboss.ws.metadata.wsdl.WSDLException: javax.wsdl.WSDLException: W
SDLException: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.
ConnectException: Connection timed out: connect
        at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsF
actory.java:154)
        at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(Service
MetaData.java:295)
        at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCServerMetaDataBuilder.buil
dMetaData(JAXRPCServerMetaDataBuilder.java:97)
        at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(Unifi
edMetaDataDeploymentAspect.java:56)
        at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy
(DeploymentAspectManagerImpl.java:118)
        at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDep
loyerHook.java:97)
        at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInt
erceptor.java:90)
        at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.
start(SubDeployerInterceptorSupport.java:188)
        at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce
ptor.java:95)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy201.start(Unknown Source)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        ... 115 more
Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Canno
t extract schema definition: java.net.ConnectException: Connection timed out: co
nnect
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:3
94)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:4
16)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:4
16)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.j
ava:178)
        at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsF
actory.java:128)
        ... 129 more
Caused by: java.net.ConnectException: Connection timed out: connect
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.Socket.connect(Socket.java:519)
        at java.net.Socket.connect(Socket.java:469)
        at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:500)
        at sun.net.www.http.HttpClient.(HttpClient.java:233)
        at sun.net.www.http.HttpClient.New(HttpClient.java:306)
        at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLC
onnection.java:799)
        at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConne
ction.java:747)
        at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection
.java:658)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
nection.java:981)
        at java.net.URL.openStream(URL.java:1009)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.handleSchemaImports(WSDL11Reader
.java:588)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.handleSchemaImports(WSDL11Reader
.java:589)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processSchemaInclude(WSDL11Reade
r.java:560)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:3
85)
        ... 133 more
17:54:46,421 INFO  [TomcatDeployer] deploy, ctxPath=/portal-users-samples, warUr
l=.../deploy/jboss-portal.sar/samples/portal-users-samples.sar/portal-users-samp
les.war/
17:54:47,015 INFO  [TomcatDeployer] deploy, ctxPath=/portal-ajax, warUrl=.../dep
loy/jboss-portal.sar/portal-ajax.war/

----------------------------------------------------

17:59:54,796 INFO  [TableMetadata] table found: PUBLIC.JBP_OBJECT_NODE_SEC
17:59:54,796 INFO  [TableMetadata] columns: [node_key, role, pk]
17:59:54,796 INFO  [TableMetadata] foreign keys: [fk9cbbd94dd209e280]
17:59:54,796 INFO  [TableMetadata] indexes: [sys_idx_410, sys_idx_408]
17:59:54,812 INFO  [TableMetadata] table found: PUBLIC.JBP_OBJECT_NODE_SEC_ACTIO
NS
17:59:54,812 INFO  [TableMetadata] columns: [actions, pk]
17:59:54,812 INFO  [TableMetadata] foreign keys: [fkbe83b7ebf2685fb6]
17:59:54,812 INFO  [TableMetadata] indexes: [sys_idx_413]
17:59:54,843 INFO  [TableMetadata] table found: PUBLIC.JBP_PAGE
17:59:54,843 INFO  [TableMetadata] columns: [pk]
17:59:54,843 INFO  [TableMetadata] foreign keys: [fk3856045695cb95c3]
17:59:54,843 INFO  [TableMetadata] indexes: [sys_idx_415, sys_idx_565]
17:59:55,187 INFO  [TableMetadata] table found: PUBLIC.JBP_PORTAL
17:59:56,484 ERROR [ServiceObjectFactoryJAXRPC] Cannot create service
org.jboss.ws.metadata.wsdl.WSDLException: javax.wsdl.WSDLException: WSDLExceptio
n: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.ConnectExce
ption: Connection timed out: connect
        at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsF
actory.java:154)
        at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(Service
MetaData.java:295)
        at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buil
dMetaData(JAXRPCClientMetaDataBuilder.java:116)
        at org.jboss.ws.core.jaxrpc.client.ServiceImpl.(ServiceImpl.java:1
26)
        at org.jboss.ws.core.jaxrpc.client.ServiceObjectFactoryJAXRPC.getObjectI
nstance(ServiceObjectFactoryJAXRPC.java:156)
        at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:3
04)
        at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java
:1273)
        at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingC
ontext.java:1290)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:763)
        at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
        at javax.naming.InitialContext.lookup(InitialContext.java:392)
        at org.jboss.portal.wsrp.services.AbstractJNDIServiceFactory.getServiceF
or(AbstractJNDIServiceFactory.java:152)
        at org.jboss.portal.wsrp.services.AbstractSOAPServiceFactory.getService(
AbstractSOAPServiceFactory.java:75)
        at org.jboss.portal.wsrp.consumer.EndpointConfigurationInfo.getService(E
ndpointConfigurationInfo.java:395)
        at org.jboss.portal.wsrp.consumer.EndpointConfigurationInfo.getServiceDe
scriptionService(EndpointConfigurationInfo.java:370)
        at org.jboss.portal.wsrp.consumer.EndpointConfigurationInfo.refreshServi
ces(EndpointConfigurationInfo.java:469)
        at org.jboss.portal.wsrp.consumer.EndpointConfigurationInfo.forceRefresh
(EndpointConfigurationInfo.java:462)
        at org.jboss.portal.wsrp.consumer.EndpointConfigurationInfo.refresh(Endp
ointConfigurationInfo.java:455)
        at org.jboss.portal.wsrp.consumer.ProducerInfo.internalRefresh(ProducerI
nfo.java:327)
        at org.jboss.portal.wsrp.consumer.ProducerInfo.detailedRefresh(ProducerI
nfo.java:282)
        at org.jboss.portal.wsrp.consumer.ProducerInfo.refresh(ProducerInfo.java
:277)
        at org.jboss.portal.wsrp.consumer.ProducerInfo.getPortletMap(ProducerInf
o.java:662)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(Ja
vassistLazyInitializer.java:173)
        at org.jboss.portal.wsrp.consumer.ProducerInfo_$$_javassist_101.getPortl
etMap(ProducerInfo_$$_javassist_101.java)
        at org.jboss.portal.wsrp.consumer.WSRPConsumerImpl.getPortlets(WSRPConsu
merImpl.java:150)
        at org.jboss.portal.portlet.federation.impl.FederatedPortletInvokerServi
ce.getPortlets(FederatedPortletInvokerService.java:89)
        at org.jboss.portal.core.management.PortletDiscoveryService.processPortl
etDiscovery(PortletDiscoveryService.java:89)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.varia.scheduler.Scheduler$MBeanListener.handleNotification(
Scheduler.java:1346)
        at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.notification.NotificationListenerProxy.invoke(Notificati
onListenerProxy.java:153)
        at $Proxy11.handleNotification(Unknown Source)
        at javax.management.NotificationBroadcasterSupport.handleNotification(No
tificationBroadcasterSupport.java:257)
        at javax.management.NotificationBroadcasterSupport$SendNotifJob.run(Noti
ficationBroadcasterSupport.java:322)
        at javax.management.NotificationBroadcasterSupport$1.execute(Notificatio
nBroadcasterSupport.java:307)
        at javax.management.NotificationBroadcasterSupport.sendNotification(Noti
ficationBroadcasterSupport.java:229)
        at javax.management.timer.Timer.sendNotification(Timer.java:1234)
        at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1203)
        at javax.management.timer.TimerAlarmClock.run(Timer.java:1286)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Canno
t extract schema definition: java.net.ConnectException: Connection timed out: co
nnect
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:3
94)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:4
16)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:4
16)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.j
ava:178)
        at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsF
actory.java:128)
        ... 57 more
Caused by: java.net.ConnectException: Connection timed out: connect
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.Socket.connect(Socket.java:519)
        at java.net.Socket.connect(Socket.java:469)
        at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:500)
        at sun.net.www.http.HttpClient.(HttpClient.java:233)
        at sun.net.www.http.HttpClient.New(HttpClient.java:306)
        at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLC
onnection.java:799)
        at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConne
ction.java:747)
        at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection
.java:658)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
nection.java:981)
        at java.net.URL.openStream(URL.java:1009)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.handleSchemaImports(WSDL11Reader
.java:588)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.handleSchemaImports(WSDL11Reader
.java:589)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processSchemaInclude(WSDL11Reade
r.java:560)
        at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:3
85)
        ... 61 more
18:00:29,281 INFO  [TableMetadata] columns: [pk]
18:00:29,281 INFO  [TableMetadata] foreign keys: [fk7bb0d07395cb95c3]

--------------------------------------------------

8:00:29,531 INFO  [SchemaUpdate] schema update complete
8:00:29,531 INFO  [NamingHelper] JNDI InitialContext properties:{}
8:00:31,359 INFO  [HbmBinder] Mapping collection: org.jboss.portal.core.impl.po
tlet.state.PersistentPortletState.entries -> JBP_PORTLET_STATE_ENTRY
8:00:54,671 ERROR [ServiceObjectFactoryJAXRPC] Cannot create service
rg.jboss.ws.metadata.wsdl.WSDLException: javax.wsdl.WSDLException: WSDLExceptio
: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.ConnectExce
tion: Connection timed out: connect
       at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsF
ctory.java:154)
       at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(Service
etaData.java:295)
       at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buil
MetaData(JAXRPCClientMetaDataBuilder.java:116)
       at org.jboss.ws.core.jaxrpc.client.ServiceImpl.(ServiceImpl.java:1
6)
       at org.jboss.ws.core.jaxrpc.client.ServiceObjectFactoryJAXRPC.getObjectI
stance(ServiceObjectFactoryJAXRPC.java:156)
       at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:3
4)
       at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java
1273)
       at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingC
ntext.java:1290)
       at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:763)
       at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
       at javax.naming.InitialContext.lookup(InitialContext.java:392)
       at org.jboss.portal.wsrp.services.AbstractJNDIServiceFactory.getServiceF
r(AbstractJNDIServiceFactory.java:152)
       at org.jboss.portal.wsrp.services.AbstractSOAPServiceFactory.getService(
bstractSOAPServiceFactory.java:75)
       at org.jboss.portal.wsrp.consumer.EndpointConfigurationInfo.getService(E
dpointConfigurationInfo.java:395)
       at org.jboss.portal.wsrp.consumer.EndpointConfigurationInfo.getServiceDe
criptionService(EndpointConfigurationInfo.java:370)
       at org.jboss.portal.wsrp.consumer.EndpointConfigurationInfo.refreshServi
es(EndpointConfigurationInfo.java:469)
       at org.jboss.portal.wsrp.consumer.EndpointConfigurationInfo.forceRefresh
EndpointConfigurationInfo.java:462)
       at org.jboss.portal.wsrp.consumer.ProducerInfo.internalRefresh(ProducerI
fo.java:334)
       at org.jboss.portal.wsrp.consumer.ProducerInfo.detailedRefresh(ProducerI
fo.java:282)
       at org.jboss.portal.wsrp.consumer.ProducerInfo.refresh(ProducerInfo.java
277)
       at org.jboss.portal.wsrp.consumer.ProducerInfo.getPortletMap(ProducerInf
.java:662)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
ava:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
orImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:597)
       at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(Ja
assistLazyInitializer.java:173)
       at org.jboss.portal.wsrp.consumer.ProducerInfo_$$_javassist_101.getPortl
tMap(ProducerInfo_$$_javassist_101.java)
       at org.jboss.portal.wsrp.consumer.WSRPConsumerImpl.getPortlets(WSRPConsu
erImpl.java:150)
       at org.jboss.portal.portlet.federation.impl.FederatedPortletInvokerServi
e.getPortlets(FederatedPortletInvokerService.java:89)
       at org.jboss.portal.core.management.PortletDiscoveryService.processPortl
tDiscovery(PortletDiscoveryService.java:89)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
ava:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
orImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:597)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
r.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
r.java:133)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
eanOperationInterceptor.java:142)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
ava:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.varia.scheduler.Scheduler$MBeanListener.handleNotification(
cheduler.java:1346)
       at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
orImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:597)
       at org.jboss.mx.notification.NotificationListenerProxy.invoke(Notificati
nListenerProxy.java:153)
       at $Proxy11.handleNotification(Unknown Source)
       at javax.management.NotificationBroadcasterSupport.handleNotification(No
ificationBroadcasterSupport.java:257)
       at javax.management.NotificationBroadcasterSupport$SendNotifJob.run(Noti
icationBroadcasterSupport.java:322)
       at javax.management.NotificationBroadcasterSupport$1.execute(Notificatio
BroadcasterSupport.java:307)
       at javax.management.NotificationBroadcasterSupport.sendNotification(Noti
icationBroadcasterSupport.java:229)
       at javax.management.timer.Timer.sendNotification(Timer.java:1234)
       at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1203)
       at javax.management.timer.TimerAlarmClock.run(Timer.java:1286)
       at java.util.TimerThread.mainLoop(Timer.java:512)
       at java.util.TimerThread.run(Timer.java:462)
aused by: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Canno
 extract schema definition: java.net.ConnectException: Connection timed out: co
nect
       at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:3
4)
       at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:4
6)
       at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:4
6)
       at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.j
va:178)
       at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsF
ctory.java:128)
       ... 56 more
aused by: java.net.ConnectException: Connection timed out: connect
       at java.net.PlainSocketImpl.socketConnect(Native Method)
       at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
       at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
       at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
       at java.net.Socket.connect(Socket.java:519)
       at java.net.Socket.connect(Socket.java:469)
       at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
       at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
       at sun.net.www.http.HttpClient.openServer(HttpClient.java:500)
       at sun.net.www.http.HttpClient.(HttpClient.java:233)
       at sun.net.www.http.HttpClient.New(HttpClient.java:306)
       at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLC
nnection.java:799)
       at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConne
tion.java:747)
       at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection
java:658)
       at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
ection.java:981)
       at java.net.URL.openStream(URL.java:1009)
       at org.jboss.ws.tools.wsdl.WSDL11Reader.handleSchemaImports(WSDL11Reader
java:588)
       at org.jboss.ws.tools.wsdl.WSDL11Reader.handleSchemaImports(WSDL11Reader
java:589)
       at org.jboss.ws.tools.wsdl.WSDL11Reader.processSchemaInclude(WSDL11Reade
.java:560)
       at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:3
5)
       ... 60 more
8:01:07,796 INFO  [HbmBinder] Mapping collection: org.jboss.portal.core.impl.po
tlet.state.PersistentPortletState.children -> JBP_PORTLET_STATE
8:01:07,796 INFO  [HbmBinder] Mapping collection: org.jboss.portal.core.impl.po
tlet.state.PersistentConsumerGroup.relatedConsumers -> JBP_PORTLET_CONSUMER
8:01:07,796 INFO  [HbmBinder] Mapping collection: org.jboss.portal.core.impl.po
tlet.state.PersistentConsumer.relatedRegistrations -> JBP_PORTLET_REG
8:01:07,796 INFO  [HbmBinder] Mapping collection: org.jboss.portal.core.impl.po
tlet.state.PersistentRegistration.relatedPortletStates -> JBP_PORTLET_STATE
8:01:07,812 ERROR [Scheduler$Listener] Invoke of the Schedulable MBean failed
avax.management.MBeanException
       at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptio
s(ReflectedDispatcher.java:180)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
r.java:163)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
r.java:133)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
eanOperationInterceptor.java:142)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
ava:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.varia.scheduler.Scheduler$MBeanListener.handleNotification(
cheduler.java:1346)
       at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
orImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:597)
       at org.jboss.mx.notification.NotificationListenerProxy.invoke(Notificati
nListenerProxy.java:153)
       at $Proxy11.handleNotification(Unknown Source)
       at javax.management.NotificationBroadcasterSupport.handleNotification(No
ificationBroadcasterSupport.java:257)
       at javax.management.NotificationBroadcasterSupport$SendNotifJob.run(Noti
icationBroadcasterSupport.java:322)
       at javax.management.NotificationBroadcasterSupport$1.execute(Notificatio
BroadcasterSupport.java:307)
       at javax.management.NotificationBroadcasterSupport.sendNotification(Noti
icationBroadcasterSupport.java:229)
       at javax.management.timer.Timer.sendNotification(Timer.java:1234)
       at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1203)
       at javax.management.timer.TimerAlarmClock.run(Timer.java:1286)
       at java.util.TimerThread.mainLoop(Timer.java:512)
       at java.util.TimerThread.run(Timer.java:462)
aused by: org.jboss.portal.portlet.InvokerUnavailableException: Couldn't access
WSRP_v1_ServiceDescription_PortType service. Cause: Could not dereference objec

       at org.jboss.portal.wsrp.consumer.WSRPConsumerImpl.getPortlets(WSRPConsu
erImpl.java:155)
       at org.jboss.portal.portlet.federation.impl.FederatedPortletInvokerServi
e.getPortlets(FederatedPortletInvokerService.java:89)
       at org.jboss.portal.core.management.PortletDiscoveryService.processPortl
tDiscovery(PortletDiscoveryService.java:89)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
ava:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
orImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:597)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
r.java:155)
       ... 22 more

Even though i am getting errors,I open the link "http://localhost:8080/portal" in the browser. The portlets in the home page are getting open properly. Dont really know whats happening...is the server getting connected to any web service during startup. Please help me on this..[/url]

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189401#4189401

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189401


From ropalka at redhat.com  Fri Nov 14 10:13:49 2008
From: ropalka at redhat.com (Richard Opalka)
Date: Fri, 14 Nov 2008 16:13:49 +0100
Subject: [jbossws-users] Classloader problem in WSDLDefinitionsFactory
In-Reply-To: <B1F2861AED068344B72C4AA018B6F54A022503C203EA@LONMC01012.rbsres07.net>
References: <B1F2861AED068344B72C4AA018B6F54A022503C203EA@LONMC01012.rbsres07.net>
Message-ID: <491D95AD.8080809@redhat.com>

Hi Paul,

   use user forum next time, please!
Just FYI I applied your suggested patch
so it will be available in next JBossWS release:

[/home/opalka][/home/opalka/svn/jbossws/stack/native/trunk]>svn diff -r 
8734:8735 
modules/core/src/main/java/org/jboss/ws/tools/wsdl/WSDLDefinitionsFactory.java
Index: 
modules/core/src/main/java/org/jboss/ws/tools/wsdl/WSDLDefinitionsFactory.java
===================================================================
--- 
modules/core/src/main/java/org/jboss/ws/tools/wsdl/WSDLDefinitionsFactory.java    
(revision 8734)
+++ 
modules/core/src/main/java/org/jboss/ws/tools/wsdl/WSDLDefinitionsFactory.java    
(revision 8735)
@@ -107,7 +107,7 @@
          String defaultNamespace = getDefaultNamespace(wsdlDoc);
          if (Constants.NS_WSDL11.equals(defaultNamespace))
          {
-            WSDLFactory wsdlFactory = 
WSDLFactory.newInstance(JBossWSDLFactoryImpl.class.getName());
+            WSDLFactory wsdlFactory = 
WSDLFactory.newInstance(JBossWSDLFactoryImpl.class.getName(), 
this.getClass().getClassLoader());
             WSDLReader wsdlReader = wsdlFactory.newWSDLReader();
             wsdlReader.setFeature("javax.wsdl.verbose", false);

Richard

Paul.WOODWARD at rbs.com wrote:
> Hi Guys,
>
> I have a problem - org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse() has the following line:
>
> WSDLFactory wsdlFactory = WSDLFactory.newInstance(JBossWSDLFactoryImpl.class.getName();
>
> This makes it use the system classloader to search for the WSDL factory implementation which breaks when it is used inside a container which provides a different classloader. Is there a good reason for this or would it be possible to replace it with :
>
> WSDLFactory wsdlFactory = WSDLFactory.newInstance(JBossWSDLFactoryImpl.class.getName(), getClass().getClassLoader());
>
> Thanks, Paul
>
> ***********************************************************************************
> The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. 
> Authorised and regulated by the Financial Services Authority 
>  
> This e-mail message is confidential and for use by the 
> addressee only. If the message is received by anyone other 
> than the addressee, please return the message to the sender 
> by replying to it and then delete the message from your 
> computer. Internet e-mails are not necessarily secure. The 
> Royal Bank of Scotland plc does not accept responsibility for 
> changes made to this message after it was sent. 
>
> Whilst all reasonable care has been taken to avoid the 
> transmission of viruses, it is the responsibility of the recipient to 
> ensure that the onward transmission, opening or use of this 
> message and any attachments will not adversely affect its 
> systems or data. No responsibility is accepted by The 
> Royal Bank of Scotland plc in this regard and the recipient should carry 
> out such virus and other checks as it considers appropriate. 
> Visit our websites at: 
> www.rbs.com
> www.rbs.com/gbm
> www.rbsgc.com
> ***********************************************************************************
>
>
> _______________________________________________
> jbossws-users mailing list
> jbossws-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbossws-users
>   


-- 
B.Sc. Richard Opalka
Senior Software Engineer
JBoss, a division of Red Hat

Mobile: +420 731 186 942
Mail: ropalka at redhat.com



From do-not-reply at jboss.com  Fri Nov 14 15:20:36 2008
From: do-not-reply at jboss.com (aalissa)
Date: Fri, 14 Nov 2008 15:20:36 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Steps for implementing WS-Security
	in JBoss using Userna
Message-ID: <7353778.1226694036939.JavaMail.jboss@colo-br-02.atl.jboss.com>

thanks alot for this post

i was searching the net for a way to use username token with jax-ws and it did not work for me.

i did the same as you did but their was no usename token in the wsdl
and what i did was :
1-
creating the webservice:
/**
 * 
 */
package test;

import javax.ejb.Stateless;
import javax.jws.WebMethod;
import javax.jws.WebService;
import javax.jws.soap.SOAPBinding;

import org.jboss.annotation.security.SecurityDomain;
import org.jboss.ws.annotation.EndpointConfig;

/**
 * @author ISSA
 *
 */
@Stateless
@WebService 
(name="TestUsername", 
targetNamespace = "http://test",  
serviceName = "TestUsernameService") 
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT) 
@EndpointConfig(configName = "Standard WSSecurity Endpoint") 
@SecurityDomain("JBossWS") 

public class TestUsername {
	
	@WebMethod
	public String hi(String name)
	{
		return "hi "+name;
	}

}

2- jboss-wsse-server.xml:
<jboss-ws-security xmlns="http://www.jboss.com/ws-security/config"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/ws-security/config
http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">





</jboss-ws-security>

i put it in the meta-inf folder

please if you know why it did not work with me, help me :)
thanks for all of you :)


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189524#4189524

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189524


From do-not-reply at jboss.com  Fri Nov 14 15:23:46 2008
From: do-not-reply at jboss.com (aalissa)
Date: Fri, 14 Nov 2008 15:23:46 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Steps for implementing WS-Security
	in JBoss using Userna
Message-ID: <3548244.1226694226283.JavaMail.jboss@colo-br-02.atl.jboss.com>

sorry i was trying to reply for other post .

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189525#4189525

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189525


From do-not-reply at jboss.com  Fri Nov 14 15:31:45 2008
From: do-not-reply at jboss.com (aalissa)
Date: Fri, 14 Nov 2008 15:31:45 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Steps for implementing WS-Security
	in JBoss using Userna
Message-ID: <30103331.1226694705936.JavaMail.jboss@colo-br-02.atl.jboss.com>

"aalissa" wrote : sorry i was trying to reply for other post .

i didn't notice that thier i another page so i was thinking that i am in differet post 

execuse me for this things :)
since i could not find a way to delete it .


can you please help.
thanks again pramod_bs for this post.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189528#4189528

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189528


From do-not-reply at jboss.com  Sat Nov 15 06:24:58 2008
From: do-not-reply at jboss.com (aalissa)
Date: Sat, 15 Nov 2008 06:24:58 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - WS Addressing
Message-ID: <27149555.1226748298870.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

i was trying to add ws addressing in my service and i found that by adding the line 

@javax.xml.ws.soap.Addressing(enabled=true, required=true)

i will see this line 

<wsaw:UsingAddressing wsdl:required="true"/>

but in the wsdl it did not appear.

any ideas of why is that.
thanks in advanced


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189585#4189585

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189585


From do-not-reply at jboss.com  Sat Nov 15 11:22:04 2008
From: do-not-reply at jboss.com (eminil)
Date: Sat, 15 Nov 2008 11:22:04 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - A client using both EJB3 (RMI) and
	JBossWS Soap
Message-ID: <19994466.1226766124510.JavaMail.jboss@colo-br-02.atl.jboss.com>

We're using a client that has the option to select between using EJB (RMI) or SOAP to connect to the server.

Our EJB3s are deployed as webservices as well in jboss with the @WebService annotation.

How can we do this easily? Previously we used axis to create classes for this.
It created 

MyServiceBindingImpl  (implements MyService)
MyServiceLocator

The locator class had a method to get the MyService interface.

So basically we had a method to get the MyService interface and let the client execute methods on it. And the method look somewhat like:

  | 
  | If (ejb){
  |   return new MyServiceBindingImpl();
  | }
  | else if (soap){
  |   return myServiceLocator.getMyService()
  | }
  | 

But now we deploy the EJB3 bean MyBean and have a remote interface MyBeanRemote.

And with JBossWS we get a service endpoint MyBean (interface) that we can access through jbossws.

But now these two things don't implement the same interface. Previously (with EJB2) it was MyService that extended java.rmi.Remote. So the functionality of the method above can't be used... since the ws endpoint and the bean remote interface aren't relative...

Any clues on how to work around this easily?


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189607#4189607

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189607


From do-not-reply at jboss.com  Sat Nov 15 11:55:54 2008
From: do-not-reply at jboss.com (eminil)
Date: Sat, 15 Nov 2008 11:55:54 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: New Wiki has been down for at least
	a day and a half....
Message-ID: <21507495.1226768154960.JavaMail.jboss@colo-br-02.atl.jboss.com>

This did never get answered... I'm running into the same problem.

We have Exceptions defined as java classes. And we want both the server and client to use the same classes.

But when we run wsconsume to generate the endpoint for the client, it wraps up the Exceptions in weird _Exception.java classes. We would like the endpoint interface to use the same exception classes as the server. (They are packaged into our client jar and shipped along with the client).

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189613#4189613

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189613


From do-not-reply at jboss.com  Sat Nov 15 12:06:04 2008
From: do-not-reply at jboss.com (eminil)
Date: Sat, 15 Nov 2008 12:06:04 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: A client using both EJB3 (RMI) and
	JBossWS Soap
Message-ID: <22309973.1226768764357.JavaMail.jboss@colo-br-02.atl.jboss.com>

Is it horrible to let the ws endpoint interface extend the *EJBRemote interface for the ejb that the webservice represents? 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189614#4189614

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189614


From do-not-reply at jboss.com  Sat Nov 15 14:30:02 2008
From: do-not-reply at jboss.com (eminil)
Date: Sat, 15 Nov 2008 14:30:02 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: A client using both EJB3 (RMI) and
	JBossWS Soap
Message-ID: <848945.1226777402676.JavaMail.jboss@colo-br-02.atl.jboss.com>

"eminil" wrote : Is it horrible to let the ws endpoint interface extend the *EJBRemote interface for the ejb that the webservice represents? 
Yes it was horrible, did not work :P

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189629#4189629

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189629


From do-not-reply at jboss.com  Sat Nov 15 15:38:30 2008
From: do-not-reply at jboss.com (rlperry)
Date: Sat, 15 Nov 2008 15:38:30 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Setting org.jboss.ws.timeout on
	client
Message-ID: <21564544.1226781510444.JavaMail.jboss@colo-br-02.atl.jboss.com>

Thy passing in the 10 as in Integer instead of as a String for the Timeout property.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189632#4189632

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189632


From do-not-reply at jboss.com  Mon Nov 17 16:31:29 2008
From: do-not-reply at jboss.com (ahowardhobs)
Date: Mon, 17 Nov 2008 16:31:29 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: wsconsume: generated operations do
	not declare throws Re
Message-ID: <13975520.1226957489497.JavaMail.jboss@colo-br-02.atl.jboss.com>

Did you ever find a solution?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189913#4189913

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189913


From do-not-reply at jboss.com  Mon Nov 17 18:15:28 2008
From: do-not-reply at jboss.com (jeckles933)
Date: Mon, 17 Nov 2008 18:15:28 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: How can I do mutual SSL when using
	JBoss as Web service
Message-ID: <29173283.1226963728454.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have a similiar problem.  I can call a ws via https using stand alone project just fine.  Run same code in jboss container, get error

Can not connect http client invoker. Invalid HTTP server response [403] - Service Error. Response: Service Error/403

Side note:  to get around the multiple keystores, you can use this approach

HttpsURLConnection.setDefaultSSLSocketFactory(sslSocketFactory);

you'll find a bunch of posts on it.  i can provide more detail if needed.
if you find solution to 403 problem, please post it.



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189942#4189942

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189942


From do-not-reply at jboss.com  Tue Nov 18 03:01:06 2008
From: do-not-reply at jboss.com (mignaak)
Date: Tue, 18 Nov 2008 03:01:06 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: jax-ws soap protocol handler and
	white space.
Message-ID: <9994151.1226995266667.JavaMail.jboss@colo-br-02.atl.jboss.com>

After days spent debugging I found a solution.
It seems the remote server does not support chunked requests.
The remote server is websphere 5.1.

The solution is to put chunksize=0 in client config "Standard Client" in file
"standard-jaxws-client-config.xml" in jbossws.

Hope this solution ca be useful to others.

Bye.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189993#4189993

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189993


From do-not-reply at jboss.com  Tue Nov 18 04:05:17 2008
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Tue, 18 Nov 2008 04:05:17 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: WS Addressing
Message-ID: <9373759.1226999117040.JavaMail.jboss@colo-br-02.atl.jboss.com>

This is metro approach that doesn't work in native.
See our WS-Addressing documentation/tutorials/tests
to see how to enable WS-Addressing in native if native
is your preferred SOAP stack.
If you don't have preferred stack, use metro integration
instead.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190003#4190003

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190003


From do-not-reply at jboss.com  Tue Nov 18 05:13:10 2008
From: do-not-reply at jboss.com (eontech)
Date: Tue, 18 Nov 2008 05:13:10 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Problem in interpreting SOAP message on
	JBoss EAP 4.3.0
Message-ID: <4120091.1227003190126.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi All,

We are using XFire to invoke webservices. We were using Jboss AS 4.0.5 earlier to deploy our webservices. This combination was working fine.
Now we have upgraded to JBossEAP 4.3.0. When we generate webservice clients via XFire to test webservices deployed on EAP, the parameters passed are null.
If we generate clients from wsconsume (Jboss utility), it works fine. It works well with .NET clients as  well.
I am wondering what has changed in EAP which is not interpreting XFire request correctly. 

Following are the SOAP messages from various clients, all work well in JBoss AS 4.0.4 but on EAP with XFire, parameters become null.

<=====================Jboss Client====================>

  | 
  | <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
  |  <env:Header/>
  |  <env:Body>
  |   <ns1:callwebsvcService xmlns:ns1='http://ws.websvc.services.abhishek.com/standard/head/websvctest'>
  |    <token>myvalue</token>
  |    <holdingId>101</holdingId>
  |   </ns1:callwebsvcService>
  |  </env:Body>
  | </env:Envelope>
  | 

<=====================.NET Client====================>

  | 
  | <soap:Envelope xmlns:soap='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
  |  <soap:Body>
  |   <callwebsvcService xmlns='http://ws.websvc.services.abhishek.com/standard/head/websvctest'>
  |    <token xmlns=''>test</token>
  |    <holdingId xmlns=''>1</holdingId>
  |   </callwebsvcService>
  |  </soap:Body>
  | </soap:Envelope>
  | 

<=====================XFIRE Client===================>

  | 
  | <soap:Envelope xmlns:soap='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
  |  <soap:Body>
  |   <ns1:callwebsvcService xmlns:ns1='http://ws.websvc.services.abhishek.com/standard/head/websvctest'>
  |    <ns1:token>XFire</ns1:token>
  |    <ns1:holdingId>123</ns1:holdingId>
  |   </ns1:callwebsvcService>
  |  </soap:Body>
  | </soap:Envelope>
  | 

<====================================================>

Following is the wsdl contents


  | <?xml version="1.0" encoding="UTF-8"?>
  | <definitions name="websvcCallService" targetNamespace="http://ws.websvc.services.abhishek.com/standard/head/websvctest" 
  | xmlns:tns="http://ws.websvc.services.abhishek.com/standard/head/websvctest" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  | xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/">
  |   <types>
  |     <xs:schema targetNamespace="http://ws.websvc.services.abhishek.com/standard/head/websvctest" version="1.0" 
  |     xmlns:tns="http://ws.websvc.services.abhishek.com/standard/head/websvctest" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  |    <xs:element name="callwebsvcService" type="tns:callwebsvcService"/>
  |    <xs:element name="callwebsvcServiceResponse" type="tns:callwebsvcServiceResponse"/>
  |    <xs:complexType name="callwebsvcService">
  |     <xs:sequence>
  |      <xs:element minOccurs="0" name="token" type="xs:string"/>
  |      <xs:element name="holdingId" type="xs:int"/>
  |     </xs:sequence>
  |    </xs:complexType>
  |    <xs:complexType name="callwebsvcServiceResponse">
  |     <xs:sequence>
  |      <xs:element minOccurs="0" name="callwebsvcServiceResponse" type="xs:string"/>
  |     </xs:sequence>
  |    </xs:complexType>
  |   </xs:schema>
  |   </types>
  |   <message name="websvcCallService_callwebsvcService">
  |     <part name="callwebsvcService" element="tns:callwebsvcService">
  |     </part>
  |   </message>
  |   <message name="websvcCallService_callwebsvcServiceResponse">
  |     <part name="callwebsvcServiceResponse" element="tns:callwebsvcServiceResponse">
  |     </part>
  |   </message>
  |   <portType name="websvcCallService">
  |     <operation name="callwebsvcService" parameterOrder="callwebsvcService">
  |       <input message="tns:websvcCallService_callwebsvcService">
  |     </input>
  |       <output message="tns:websvcCallService_callwebsvcServiceResponse">
  |     </output>
  |     </operation>
  |   </portType>
  |   <binding name="websvcCallServiceBinding" type="tns:websvcCallService">
  |     <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
  |     <operation name="callwebsvcService">
  |       <soap:operation soapAction=""/>
  |       <input>
  |         <soap:body use="literal"/>
  |       </input>
  |       <output>
  |         <soap:body use="literal"/>
  |       </output>
  |     </operation>
  |   </binding>
  |   <service name="websvcCallService">
  |     <port name="websvcCallServicePort" binding="tns:websvcCallServiceBinding">
  |       <soap:address location="http://127.0.0.1:8080/ws/websvcCallService"/>
  |     </port>
  |   </service>
  | </definitions>
  | 
<====================================================>

XFire uses namespace with the attribute which is correct, why does EAP fails to parse these values.

Any Help on this matter is highly appreciated.

Regards,
Abhishek


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190027#4190027

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190027


From do-not-reply at jboss.com  Tue Nov 18 13:03:40 2008
From: do-not-reply at jboss.com (jeckles933)
Date: Tue, 18 Nov 2008 13:03:40 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Problem consuming .net webservice
	with jbossws-3.0.1-nat
Message-ID: <23871141.1227031420660.JavaMail.jboss@colo-br-02.atl.jboss.com>

its this

your working message has 
Content-Length: bla

broken one:
Transfer-Encoding: chunked

looks like not everybody supports chunked, now - how do we turn of chunking??

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190218#4190218

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190218


From do-not-reply at jboss.com  Tue Nov 18 13:54:06 2008
From: do-not-reply at jboss.com (will.tatam)
Date: Tue, 18 Nov 2008 13:54:06 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <3374196.1227034446571.JavaMail.jboss@colo-br-02.atl.jboss.com>

nobody from the JBossWS team going to comment ?

@bschmoll1  - manage to fix your port -1 issue ?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190231#4190231

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190231


From do-not-reply at jboss.com  Tue Nov 18 17:56:58 2008
From: do-not-reply at jboss.com (brintoul)
Date: Tue, 18 Nov 2008 17:56:58 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Logging SOAP Messages
Message-ID: <25983881.1227049018370.JavaMail.jboss@colo-br-02.atl.jboss.com>


I've tried setting the category org.jboss.ws.core.MessageTrace to a priority of "TRACE" in jboss-log4j.xml but I'm still not seeing the outgoing/incoming SOAP messages.

I'm communicating with a web service using SSL - does this change anything?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190282#4190282

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190282


From do-not-reply at jboss.com  Tue Nov 18 17:58:55 2008
From: do-not-reply at jboss.com (brintoul)
Date: Tue, 18 Nov 2008 17:58:55 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Logging SOAP Messages
Message-ID: <33170568.1227049135103.JavaMail.jboss@colo-br-02.atl.jboss.com>

"brintoul" wrote : 
  | I've tried setting the category org.jboss.ws.core.MessageTrace to a priority of "TRACE" in jboss-log4j.xml but I'm still not seeing the outgoing/incoming SOAP messages.
  | 
  | I'm communicating with a web service using SSL - does this change anything?

I'm using jbossws-native-3.0.2.GA.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190283#4190283

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190283


From do-not-reply at jboss.com  Wed Nov 19 01:37:19 2008
From: do-not-reply at jboss.com (plaurentphd)
Date: Wed, 19 Nov 2008 01:37:19 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Help us learn how Feature Requests R
	gathered
Message-ID: <24055708.1227076639608.JavaMail.jboss@colo-br-02.atl.jboss.com>

My name is Paula Laurent. I am a Computer Science PhD student at DePaul University conducting research on soliciting and prioritizing requirements. The goal of this research is to find out about the current requirements processes used in Open Source projects.  

We???re requesting 20 minutes of your time to complete an online survey which can be accessed at   
http://www.surveymonkey.com/s.aspx?sm=973NJ9LtxAuHs224fvrbBg_3d_3d

Thank you.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190344#4190344

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190344



From do-not-reply at jboss.com  Wed Nov 19 02:47:00 2008
From: do-not-reply at jboss.com (aalissa)
Date: Wed, 19 Nov 2008 02:47:00 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: WS Addressing
Message-ID: <12871903.1227080820344.JavaMail.jboss@colo-br-02.atl.jboss.com>

thanks alot richard

i don't have poreferred stack

so i will try metro 
thanks again

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190384#4190384

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190384


From do-not-reply at jboss.com  Wed Nov 19 14:26:32 2008
From: do-not-reply at jboss.com (rocken7)
Date: Wed, 19 Nov 2008 14:26:32 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - soap handler init-param?
Message-ID: <25919353.1227122792094.JavaMail.jboss@colo-br-02.atl.jboss.com>

On the latest jbossWS release ... with jboss-4.2.2.GA.

Is there a way to add init-param or something similiar to the jaxws-handlers.xml configuration file?  

I have implemented a SOAPHandler and due to various environments, it would be nice to provide some injected configuration properties.  

I thought you could do this: 

<?xml version="1.0" encoding="UTF-8"?>
  | <handler-chains xmlns="http://java.sun.com/xml/ns/javaee"
  |   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  |   xsi:schemaLocation="http://java.sun.com/xml/ns/javaee javaee_web_services_1_2.xsd">
  | 	<handler-chain>
  | 		<handler>
  | 			<handler-class>com.yvx.content.wsdev.DeviceHandler</handler-class>
  | 			<init-params>
  | 				<init-param name="myProperty" value="http://localhost:9100/userService"/>
  | 			</init-params> 
  | 		</handler>
  | 	</handler-chain>
  | </handler-chains>
  | 

But that doesn't seem to work.  If there is a better way, please discuss.  

Thnx 

rocken7

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190614#4190614

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190614


From do-not-reply at jboss.com  Wed Nov 19 17:04:37 2008
From: do-not-reply at jboss.com (pa12399)
Date: Wed, 19 Nov 2008 17:04:37 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - problem deploying webservice using
	JBoss 4.2.2 and native we
Message-ID: <30066120.1227132277239.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi

I created a webservice using bottom-up approach and using annotations. When I deploy the service, the WSDL that got generated does not seem to contain the correct host. It is still showing ${jboss.ws.host}

Where should I configure this? Because of this, the service is not getting deployed properly.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190649#4190649

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190649


From do-not-reply at jboss.com  Wed Nov 19 18:20:41 2008
From: do-not-reply at jboss.com (vbatista)
Date: Wed, 19 Nov 2008 18:20:41 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Handling timeouts in WebService
	client
Message-ID: <6135449.1227136841750.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,
Is there any System Property which sets the client timeout?
I have tested my src code with the following line ant it worked:

  | 	    ((BindingProvider) soapService).getRequestContext().put(StubExt.PROPERTY_CLIENT_TIMEOUT, new Long(1000));
  | 

My problem is that I have an application in production, and it's problematic to make a patch (adding the line above).
Is there any System Property I can add which sets the client timeout?

Thanks in advance.
Best regards,
Victor Batista

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190665#4190665

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190665


From do-not-reply at jboss.com  Thu Nov 20 16:17:35 2008
From: do-not-reply at jboss.com (chrissy)
Date: Thu, 20 Nov 2008 16:17:35 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Unsupported content type: text/html on
	WS call
Message-ID: <1568162.1227215855578.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi there.  I am getting the following error in my WS client:

Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. javax.xml.soap.SOAPException: Unsupported content type: text/html. Response: OK/200.
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:348)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:137)

I turned on RequestDumperValve to see the header details and I first see my client requesting the WSDL:


12:23:34,084 INFO  [[localhost]] ===============================================================
  | 12:23:34,092 INFO  [[localhost]] REQUEST URI       =/MyServer/MyService
  | 12:23:34,092 INFO  [[localhost]]           authType=null
  | 12:23:34,092 INFO  [[localhost]]  characterEncoding=null
  | 12:23:34,092 INFO  [[localhost]]      contentLength=-1
  | 12:23:34,092 INFO  [[localhost]]        contentType=null
  | 12:23:34,093 INFO  [[localhost]]        contextPath=/MyServer
  | 12:23:34,093 INFO  [[localhost]]             header=user-agent=Java/1.5.0_16
  | 12:23:34,093 INFO  [[localhost]]             header=host=localhost:8080
  | 12:23:34,093 INFO  [[localhost]]             header=accept=text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
  | 12:23:34,093 INFO  [[localhost]]             header=connection=keep-alive
  | 12:23:34,094 INFO  [[localhost]]             locale=en_US
  | 12:23:34,094 INFO  [[localhost]]             method=GET
  | 12:23:34,094 INFO  [[localhost]]          parameter=wsdl=
  | 12:23:34,095 INFO  [[localhost]]           pathInfo=null
  | 12:23:34,095 INFO  [[localhost]]           protocol=HTTP/1.1
  | 12:23:34,095 INFO  [[localhost]]        queryString=wsdl
  | 12:23:34,095 INFO  [[localhost]]         remoteAddr=127.0.0.1
  | 12:23:34,095 INFO  [[localhost]]         remoteHost=127.0.0.1
  | 12:23:34,095 INFO  [[localhost]]         remoteUser=null
  | 12:23:34,096 INFO  [[localhost]] requestedSessionId=null
  | 12:23:34,096 INFO  [[localhost]]             scheme=http
  | 12:23:34,096 INFO  [[localhost]]         serverName=localhost
  | 12:23:34,096 INFO  [[localhost]]         serverPort=8080
  | 12:23:34,096 INFO  [[localhost]]        servletPath=/MyService
  | 12:23:34,096 INFO  [[localhost]]           isSecure=false
  | 12:23:34,096 INFO  [[localhost]] ---------------------------------------------------------------
  | 12:23:34,642 INFO  [[localhost]] ---------------------------------------------------------------
  | 12:23:34,642 INFO  [[localhost]]           authType=null
  | 12:23:34,648 INFO  [[localhost]]      contentLength=-1
  | 12:23:34,659 INFO  [[localhost]]        contentType=text/xml
  | 12:23:34,694 INFO  [[localhost]]             header=X-Powered-By=Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0
  | 12:23:34,695 INFO  [[localhost]]             header=Content-Type=text/xml
  | 12:23:34,702 INFO  [[localhost]]             header=Transfer-Encoding=chunked
  | 12:23:34,702 INFO  [[localhost]]             header=Date=Thu, 20 Nov 2008 20:23:34 GMT
  | 12:23:34,702 INFO  [[localhost]]            message=null
  | 12:23:34,703 INFO  [[localhost]]         remoteUser=null
  | 12:23:34,703 INFO  [[localhost]]             status=200
  | 12:23:34,703 INFO  [[localhost]] ===============================================================

and then I see the Soap Request:

12:23:38,228 INFO  [[localhost]] ===============================================================
  | 12:23:39,076 INFO  [[localhost]] REQUEST URI       =/
  | 12:23:39,076 INFO  [[localhost]]           authType=null
  | 12:23:39,076 INFO  [[localhost]]  characterEncoding=UTF-8
  | 12:23:39,076 INFO  [[localhost]]      contentLength=-1
  | 12:23:39,076 INFO  [[localhost]]        contentType=text/xml; charset=UTF-8
  | 12:23:39,077 INFO  [[localhost]]        contextPath=
  | 12:23:39,077 INFO  [[localhost]]             header=authorization=Basic Y2hyaXNzeTpwYXNzd29yZA==
  | 12:23:39,077 INFO  [[localhost]]             header=soapaction="http://schemas.mydomain.net/10/myservice/doLogin"
  | 12:23:39,077 INFO  [[localhost]]             header=content-type=text/xml; charset=UTF-8
  | 12:23:39,077 INFO  [[localhost]]             header=jboss-remoting-version=22
  | 12:23:39,077 INFO  [[localhost]]             header=user-agent=JBossRemoting - 2.2.2.SP8
  | 12:23:39,078 INFO  [[localhost]]             header=host=localhost:8080
  | 12:23:39,078 INFO  [[localhost]]             header=accept=text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
  | 12:23:39,078 INFO  [[localhost]]             header=connection=keep-alive
  | 12:23:39,078 INFO  [[localhost]]             header=transfer-encoding=chunked
  | 12:23:39,078 INFO  [[localhost]]             locale=en_US
  | 12:23:39,082 INFO  [[localhost]]             method=POST
  | 12:23:39,083 INFO  [[localhost]]           pathInfo=null
  | 12:23:39,083 INFO  [[localhost]]           protocol=HTTP/1.1
  | 12:23:39,084 INFO  [[localhost]]        queryString=null
  | 12:23:39,084 INFO  [[localhost]]         remoteAddr=127.0.0.1
  | 12:23:39,084 INFO  [[localhost]]         remoteHost=127.0.0.1
  | 12:23:39,084 INFO  [[localhost]]         remoteUser=null
  | 12:23:39,084 INFO  [[localhost]] requestedSessionId=null
  | 12:23:39,084 INFO  [[localhost]]             scheme=http
  | 12:23:39,084 INFO  [[localhost]]         serverName=localhost
  | 12:23:39,085 INFO  [[localhost]]         serverPort=8080
  | 12:23:39,085 INFO  [[localhost]]        servletPath=/index.html
  | 12:23:39,085 INFO  [[localhost]]           isSecure=false
  | 12:23:39,086 INFO  [[localhost]] ---------------------------------------------------------------
  | 12:23:39,087 INFO  [[localhost]] ---------------------------------------------------------------
  | 12:23:39,087 INFO  [[localhost]]           authType=null
  | 12:23:39,087 INFO  [[localhost]]      contentLength=2919
  | 12:23:39,088 INFO  [[localhost]]        contentType=text/html
  | 12:23:39,089 INFO  [[localhost]]             header=X-Powered-By=Servlet 2.4; JBoss-4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)/JBossWeb-2.0
  | 12:23:39,090 INFO  [[localhost]]             header=ETag=W/"2919-1227047690000"
  | 12:23:39,091 INFO  [[localhost]]             header=Last-Modified=Tue, 18 Nov 2008 22:34:50 GMT
  | 12:23:39,091 INFO  [[localhost]]            message=null
  | 12:23:39,091 INFO  [[localhost]]         remoteUser=null
  | 12:23:39,091 INFO  [[localhost]]             status=200
  | 12:23:39,091 INFO  [[localhost]] ===============================================================
  | 

If you look closely the Request URI in the second request is / and the servlet Path is /index.html.  Which might explain why I am getting text/html returned from the server.  I would assume that the Request URI should be /MyServer/MyService as it is in the WSDL service.  Is my thinking correct?  Can anyone point me in the right direction?  I can provide more details but wanted to keep the original post simple.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191047#4191047

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191047


From do-not-reply at jboss.com  Thu Nov 20 17:28:31 2008
From: do-not-reply at jboss.com (chrissy)
Date: Thu, 20 Nov 2008 17:28:31 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Unsupported content type: text/html
	on WS call
Message-ID: <19019485.1227220111324.JavaMail.jboss@colo-br-02.atl.jboss.com>

Fixed.  I am now setting BindingProvider.ENDPOINT_ADDRESS_PROPERTY correctly.  >,<

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191062#4191062

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191062


From do-not-reply at jboss.com  Fri Nov 21 10:47:29 2008
From: do-not-reply at jboss.com (bschmoll1)
Date: Fri, 21 Nov 2008 10:47:29 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: replacement of
	REPLACE_WITH_ACTUAL_URL when using annota
Message-ID: <615666.1227282449425.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes, I force it to port 80 using the "webServicePort" property. It seems to be a bit of a kludge since the host is resolved dynamically but the port is static.

My suspicion is that the mod_jk bridge is supplying the -1 port.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191311#4191311

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191311


From do-not-reply at jboss.com  Fri Nov 21 11:09:02 2008
From: do-not-reply at jboss.com (jamicide)
Date: Fri, 21 Nov 2008 11:09:02 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - webservice/client not functioning
	correctly after move from
Message-ID: <15204124.1227283742831.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have deployed an .ear file that runs stably on 4.0.3SP1 to 4.2.2GA.

Following the deployment, most of my webservices operate correctly (using the same client I used with v4.0.3SP1). However when I try to call a webservice which uses a complex type (in this case, arrayType) Jboss throws the following exception:

2008-11-19 14:44:11,912 ERROR [org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC] SOAP request exception
org.jboss.ws.WSException: Cannot obtain attribute: {http://schemas.xmlsoap.org/soap/encoding/}arrayType
        at org.jboss.ws.core.jaxrpc.binding.SOAPArrayDeserializer.getComponentTypeFromAttribute(SOAPArrayDeserializer.java:172)
        at org.jboss.ws.core.jaxrpc.binding.SOAPArrayDeserializer.deserialize(SOAPArrayDeserializer.java:70)
        at org.jboss.ws.core.binding.DeserializerSupport.deserialize(DeserializerSupport.java:60)
        at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:180)
        at org.jboss.ws.core.soap.XMLContent.transitionTo(XMLContent.java:97)
        at org.jboss.ws.core.soap.SOAPContentElement.transitionTo(SOAPContentElement.java:140)
        at org.jboss.ws.core.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:171)
        at org.jboss.ws.core.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:263)
        at org.jboss.ws.core.EndpointInvocation.getRequestParamValue(EndpointInvocation.java:115)
        at org.jboss.ws.core.EndpointInvocation.getRequestPayload(EndpointInvocation.java:135)
        at org.jboss.ws.core.server.DelegatingInvocation.getArgs(DelegatingInvocation.java:82)
        at org.jboss.wsf.container.jboss42.DefaultInvocationHandler.invoke(DefaultInvocationHandler.java:102)
        at org.jboss.wsf.container.jboss42.DefaultInvocationHandlerJAXRPC.invoke(DefaultInvocationHandlerJAXRPC.java:57)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:408)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
        at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        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:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
        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:157)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
        at java.lang.Thread.run(Thread.java:595)


Any suggestions on what might be going on here are most appreciated.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191324#4191324

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191324


From do-not-reply at jboss.com  Fri Nov 21 18:34:47 2008
From: do-not-reply at jboss.com (theraser88)
Date: Fri, 21 Nov 2008 18:34:47 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - A SOAPMessageFactory1_1Impl Classcast
	exception that only ha
Message-ID: <7404046.1227310487493.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, 
I successfully deployed my web service onto jboss application server. But it seems I can only successfully sent requests to my Windows server, and not the UNIX machine(RED HAT 9)

I deployed my Web service using .ear, so I may include SUN metro libraries v1.3
hellometro.ear
--HelloMetro.ear
    --WEB-INF/web.xml
    --WEB-INF/jboss-web.xml
    --WEB-INF/sun-jaxws.xml
--META-INF
    --jboss-app.xml
    --application.xml
--lib
   --webservices-api.jar
   --webservices-extra-api.jar
   --webservices-rt.jar
   --webservices-extra.jar


I got the following exception; I am not sure what to make out of the exception but the soap version # might be wrong. I am using Jboss 4.2.2 GA and Jbossws 3.0.4. The web service code is compile using java 1.5. 

Any help is appropriated. 
Thank you!

java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.ver1_1.Envelope1_1Impl
        at org.jboss.ws.core.soap.SOAPEnvelopeImpl.(SOAPEnvelopeImpl.java:57)
        at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:136)
        at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:96)
        at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:283)
        at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:479)
        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:109)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        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:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
        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:157)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
        at java.lang.Thread.run(Thread.java:595)
16:52:01,754 ERROR [RequestHandlerImpl] Error processing web service request
org.jboss.ws.WSException: java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl
        at org.jboss.ws.WSException.rethrow(WSException.java:68)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:336)
        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:109)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        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:230)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
        at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
        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:157)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
        at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl
        at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.createSOAPMessage(SOAPFaultHelperJAXWS.java:288)
        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:669)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:520)
        at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
        ... 22 more


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191437#4191437

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191437


From do-not-reply at jboss.com  Sat Nov 22 16:20:39 2008
From: do-not-reply at jboss.com (awhitford)
Date: Sat, 22 Nov 2008 16:20:39 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Best Practices for Dates
Message-ID: <13773270.1227388839845.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have a web service that returns Dates.  Imagine something simple like:


  | @WebMethod
  | Date getCurrentBusinessDate()
  | 

In this case, I am only interested in a Date (not a Time or Date Time).  This is by design because otherwise one might go down the road of considering Time Zones, etc. -- and that is not necessary for this case.

When running something like this, we see a full date/time appear in the SOAP result. Sure, the time is zero/midnight, but it also mentions a time zone (which really shouldn't be there, but seems to be impossible to get rid of).

By rights, I really only want to see a Date transmitted (like YYYY-MM-DD).  In JPA, for example, I use a Date type but qualify it with a @Temporal annotation to clarify the TemporalType (Date, Time, DateTime).  I see that JAXB has similar distinctions (xsd:date, xsd:time, xsd:dateTime).

Is there a way to annotate the web method so the return value is clarified to be an xsd:date?


Secondly...  Is there a material difference between using java.util.Date vs. java.util.Calendar?  (Is one really preferred over the other?)  If I am writing Java-first Web Services, should I be using Date or Calendar to represent dates?


Thanks for your help!

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191502#4191502

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191502


From do-not-reply at jboss.com  Sat Nov 22 20:57:07 2008
From: do-not-reply at jboss.com (awhitford)
Date: Sat, 22 Nov 2008 20:57:07 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - How to avoid optional parameters (wsgen)
Message-ID: <13035720.1227405427354.JavaMail.jboss@colo-br-02.atl.jboss.com>

Consider a simple web service method:

  | @WebMethod
  | void foo (@WebParam(name="param") String param)
  | 
When generating the WSDL using wsgen, and inspecting it in SoapUI, I notice that a primitive type (like an int) won't appear as optional, but an object reference does. In some cases, I would like to declare the parameter as required. I thought I could do something like:

  | @WebMethod
  | void foo (@WebParam(name="param") @XmlElement(nillable=false, required=true) String param)
  | 
Alas, this doesn't even compile because I can't use XmlElement for a method parameter...

I'm pretty sure that the optional interpretation is coming from the minOccurs="0" attribute on the xs:element.

Is there a way that I can control this? 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191518#4191518

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191518


From do-not-reply at jboss.com  Mon Nov 24 03:53:42 2008
From: do-not-reply at jboss.com (memaster)
Date: Mon, 24 Nov 2008 03:53:42 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - ERROR [RequestHandlerImpl] Cannot close
	output stream
Message-ID: <8120690.1227516822834.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello,
since some time I get the message 

anonymous wrote : ERROR [RequestHandlerImpl] Cannot close output stream

in my web application. The application is running fine, but it needs more time. What could be the reason for this? How can I solve this issue?

Thanks in advance
memaster

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191621#4191621

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191621


From do-not-reply at jboss.com  Mon Nov 24 05:35:22 2008
From: do-not-reply at jboss.com (gllambi)
Date: Mon, 24 Nov 2008 05:35:22 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - WS-Secure Conversation status?
Message-ID: <6722298.1227522922272.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, if I want to use WS-Secure Conversation with JBossWS, nowadays I've got to use the Metro stack or does the Native one has it's own implementation?

Thanks!
Guzman

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191666#4191666

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191666


From do-not-reply at jboss.com  Mon Nov 24 10:59:33 2008
From: do-not-reply at jboss.com (jamicide)
Date: Mon, 24 Nov 2008 10:59:33 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: webservice/client not functioning
	correctly after move f
Message-ID: <32274748.1227542373138.JavaMail.jboss@colo-br-02.atl.jboss.com>

Noone has seen this error before? :)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191800#4191800

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191800


From do-not-reply at jboss.com  Tue Nov 25 04:15:09 2008
From: do-not-reply at jboss.com (dmitry.kudrenko)
Date: Tue, 25 Nov 2008 04:15:09 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Could not transmit message when 2nd
	time deploying.
Message-ID: <25047660.1227604509761.JavaMail.jboss@colo-br-02.atl.jboss.com>

Greetings,

I have web application deployed on jboss 4.2.2.GA. This application communicates with a web service. It works fine when I deploy the application first time after restarting jboss. But stops work when I deploy it without restarting jboss.

Caused by: java.io.IOException: Could not transmit message
  |         at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:255)
  |         ... 41 more
  | Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker.
  |         at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:333)
  |         ... 44 more
  | Caused by: java.lang.NullPointerException
  |         at org.jboss.ws.core.soap.SOAPElementImpl.<init>(SOAPElementImpl.java:86)

I noticed with WireShark that when I deploy the application second time and try to send request to the web service it sends the SOAP request and response is received.

Also, when I tried to deploy 2 different instances of application in the same time to the jboss only the application who sent SOAP request first is working. The second application faults with the same error as described above.

Have anybody idea what can be a reason of this issue?

Thanks in advance.
--
Dmitry Kudrenko
ARDAS group (http://www.ardas.dp.ua)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191994#4191994

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191994


From do-not-reply at jboss.com  Tue Nov 25 13:00:17 2008
From: do-not-reply at jboss.com (altes-kind)
Date: Tue, 25 Nov 2008 13:00:17 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Converting EJB2.1 to Webservice
Message-ID: <9053929.1227636017605.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi,

I'm pretty new to web services and currently working on an app which has to be migrated from Bea Weblogic 8.1 to JBoss AS 4.2.1.

Currently the app is using the Bea Weblogic specific Ant task servicegen to create the webservice producer out of an EJB2.1 project (see http://edocs.beasys.com/wls/docs81/webserv/anttasks.html#1063540): 
<servicegen
  | 	destEar="${build.dir}/${ejb.jar.name}-ws"
  | 	warName="${ejb.jar.name}-ws.war">
  | 	<service
  | 		ejbJar="${build.dir}/${ejb.jar.name}.jar"
  | 		includeEJBs="ArchiveAccessRemote"
  | 		targetNamespace="de.proactiv"
  | 		serviceName="ArchiveAccess"
  | 		serviceURI="/ArchiveAccess"
  | 		style="document"
  | 		generateTypes="True"
  | 		expandMethods="True">
  | 		<!--client
  | 		packageName="de.proactiv.postbox.services.archiveaccess.webservice"
  | 		clientJarName="${ejb.jar.name}_client.jar"
  | 		/-->
  | 	</service>
  | </servicegen>

Is there a similar Ant taks in JBoss WS to convert EJB2.1 projects to webservices?
I read about wsprovide but it doesn't seem to work with EJB2.1. Is this correct?
I also read about wstool. Is it still supported in JBoss WS? If yes, where can I find the documentation?

Thank you very much! :-)
altes-kind

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192231#4192231

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192231


From do-not-reply at jboss.com  Wed Nov 26 06:12:35 2008
From: do-not-reply at jboss.com (dmitry.kudrenko)
Date: Wed, 26 Nov 2008 06:12:35 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Could not transmit message when 2nd
	time deploying.
Message-ID: <19131865.1227697955308.JavaMail.jboss@colo-br-02.atl.jboss.com>

I checked it with jboss 4.2.3.GA. And have the same situation:

Service port is created successfully, but method invocation fault with NPE exception or ClassCastException.

I plan to play with classpaths. maybe we have conflict between application and jboss library...

Have anybody ideas?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192412#4192412

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192412


From do-not-reply at jboss.com  Thu Nov 27 04:08:10 2008
From: do-not-reply at jboss.com (ops)
Date: Thu, 27 Nov 2008 04:08:10 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Asymmetric encryption with ws-security?
Message-ID: <21292604.1227776890355.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi everybody,

I need to encrypt a web service via ws-security. In every example I found there is always a mutual encryption. This means that both, client and server encode their messages using the public key of their counterpart. But this also means that the jboss web service needs a truststore containing the clients certificate. I wonder if there is no asymmetric way as in SSL, where the client simply donwloads the server certificate and they are able to exchange a secret key to communicate with. I know that it is possible to encrypt the web service request via the web containers SSL capabilities, but I definitely have to use the ws stack. 
Any Ideas?

Thanks in advance,
Oliver.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192686#4192686

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192686


From do-not-reply at jboss.com  Thu Nov 27 05:18:37 2008
From: do-not-reply at jboss.com (bartatamas)
Date: Thu, 27 Nov 2008 05:18:37 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Cannot obtain java type mapping
Message-ID: <30674427.1227781117878.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi!

I'm trying to create a web service from a session bean:

package foo.ejb;

import java.util.logging.Logger;

/**
 * @ejb.bean name="MerchTermWS"
 *           jndi-name="MerchTermWS"
 *           type="Stateless"
 *           view-type="service-endpoint"
 */
public class MerchTermWSBean implements SessionBean {
	public void ejbActivate() throws EJBException {}
        public void ejbPassivate() throws EJBException {}
	public void ejbRemove() throws EJBException {}
	public void setSessionContext(SessionContext arg0) throws EJBException {}

	/**
	 * @ejb.create-method   
	 */
	public void ejbCreate() throws javax.ejb.CreateException {}

	/**
	 * @ejb.interface-method view-type = "service-endpoint" 
	 */
	public void receiveImNotif(ReceiveImNotifIn data) {
	}
}

The wsdl contains only one operation with one input parameter:

...
  
    
      
    
  
...

The input parameter is complex type. from xsd:

...
  <xs:element name="receiveImNotifIn">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="merchTermId" type="xs:int" />
        <xs:element name="merchTrxId" type="xs:int" />
        <xs:element name="bankTrxId" type="xs:int" />
        <xs:element name="bankTrxResult" type="xs:int" />
        <xs:element name="authCode" type="authCodeType" />
        <xs:element minOccurs="0" name="mpiCat" type="xs:int" />
        <xs:element name="isRepeated" type="xs:boolean" />
      </xs:sequence>
    </xs:complexType>
  </xs:element>
...

I generated a Java class for this type, using wsimport tool
(foo.ReceiveImNotifIn)


When I deploy the bean, the JBoss say: 

org.jboss.ws.WSException: Cannot obtain java type mapping for: {http://mf.cellum.com/MerchantManagement}>receiveImNotifIn

Can somebody help me how can I set type mappings?
In the source code of JavaWS I see that a TypeMappingRegistryImpl object is instantiated and returns a newly created TypeMappingImpl for encoding: literal. The LiteralTypeMapping class registers some data types, but I don't know how to add my foo.ReceiveImNotifIn to this. I think the java-type-mapping in wsdl is not good for this problem because it dies earlier.

Thanks, Tamas



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192721#4192721

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192721


From do-not-reply at jboss.com  Thu Nov 27 06:06:20 2008
From: do-not-reply at jboss.com (bartatamas)
Date: Thu, 27 Nov 2008 06:06:20 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Cannot obtain java type mapping
Message-ID: <8312151.1227783980639.JavaMail.jboss@colo-br-02.atl.jboss.com>

It is interesting that when I use java-xml-type-mapping:

 <java-xml-type-mapping>
    <java-type>foo.ReceiveImNotifIn</java-type>
    <root-type-qname xmlns:xs="http://mf.cellum.com/MerchantManagement">xs:receiveImNotifIn</root-type-qname>
    <qname-scope>element</qname-scope>
    <variable-mapping>
        <java-variable-name>receiveImNotifIn</java-variable-name>
        <xml-element-name>receiveImNotifIn</xml-element-name>
    </variable-mapping>
  </java-xml-type-mapping>

The TypesMetaData class logs:

Add type mapping: {http://mf.cellum.com/MerchantManagement}receiveImNotifIn 

The Exception logs:

{http://mf.cellum.com/MerchantManagement}>receiveImNotifIn 


The difference is the ">" character. 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192732#4192732

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192732


From do-not-reply at jboss.com  Thu Nov 27 10:02:14 2008
From: do-not-reply at jboss.com (Gitu)
Date: Thu, 27 Nov 2008 10:02:14 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Wrong minOccurs in wsdl generated by
	Jboss
Message-ID: <6786904.1227798134631.JavaMail.jboss@colo-br-02.atl.jboss.com>

I hope this is the righht forum

Am using JBOSS 4.3.0 with WebService. WSDL is autogenerated by JBOSS.

Issue in wsdl is with minOccurs in WSDL. Even method arguments are optional(minOcuurs="0") 
For E. G  My Method Signature is "getJobByName(String aJobName)" , generated wsdl has aJobName optional. 
For some other methods its mandatory , which I dont understand how as there is hardly any difference .


  |    <xs:complexType name="getJobByName">
  |     <xs:sequence>
  |      <xs:element minOccurs="0" name="aJobName" type="xs:string"/>
  |     </xs:sequence>
  |    </xs:complexType>
  | 
  | 


Also , for some complex type (model object) , some fields are optional , others mandatory like Model (JobBean) which has name , type , version 
Here Name and type will be generated as optional and version as mandatory. How can I fix it ?

Thanks

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192801#4192801

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192801


From do-not-reply at jboss.com  Thu Nov 27 10:05:46 2008
From: do-not-reply at jboss.com (Gitu)
Date: Thu, 27 Nov 2008 10:05:46 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Wrong minOccurs in wsdl generated
	by Jboss
Message-ID: <28005550.1227798346483.JavaMail.jboss@colo-br-02.atl.jboss.com>

This is an EJB3 based webservice

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192803#4192803

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192803


From do-not-reply at jboss.com  Thu Nov 27 11:19:42 2008
From: do-not-reply at jboss.com (awhitford)
Date: Thu, 27 Nov 2008 11:19:42 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Wrong minOccurs in wsdl generated
	by Jboss
Message-ID: <10659350.1227802782035.JavaMail.jboss@colo-br-02.atl.jboss.com>

FYI...  I asked the same question here:  http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146142

As a rule, I think any Java object is treated as minOccurs=0.  The only thing that isn't optional are primitives like int.  Alas, I too am interested in some control over this because some objects are not optional and we should be able to annotate them as such.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192829#4192829

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192829


From do-not-reply at jboss.com  Thu Nov 27 21:56:39 2008
From: do-not-reply at jboss.com (yongz)
Date: Thu, 27 Nov 2008 21:56:39 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: WS-security interoperability
Message-ID: <5521204.1227840999563.JavaMail.jboss@colo-br-02.atl.jboss.com>

Does JBoss have an schedule on when to provide WS-Secure Conversation and WS-Trust support? Thanks.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192912#4192912

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192912


From do-not-reply at jboss.com  Fri Nov 28 00:02:31 2008
From: do-not-reply at jboss.com (troy.sellers)
Date: Fri, 28 Nov 2008 00:02:31 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Help with wsconsume..
Message-ID: <7977764.1227848551767.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi All,

I am trying to build a client from an existing WSDL and am running into these errors..

I am wondering if this has to do with the fact that the existing wsdl is rpc/encoding.... if so, how do i modify this wsdl (have no access to the actual endpoint) so that the wsconsume will work?

C:\Documents and Settings\troy.sellers\Desktop\jbossws-native-bin-dist\deploy\bi
n>wsconsume.bat -k customer.wsdl
parsing WSDL...


[WARNING] src-resolve: Cannot resolve the name 'soapenc:Array' to a(n) 'type def
inition' component.
  line 108 of file:/C:/Documents%20and%20Settings/troy.sellers/Desktop/jbossws-n
ative-bin-dist/deploy/bin/customer.wsdl#types?schema2

[ERROR] undefined simple or complex type 'soapenc:Array'
  line 108 of file:/C:/Documents%20and%20Settings/troy.sellers/Desktop/jbossws-n
ative-bin-dist/deploy/bin/customer.wsdl

[ERROR] undefined attribute 'soapenc:arrayType'
  line 109 of file:/C:/Documents%20and%20Settings/troy.sellers/Desktop/jbossws-n
ative-bin-dist/deploy/bin/customer.wsdl

[ERROR] undefined simple or complex type 'soapenc:Array'
  line 115 of file:/C:/Documents%20and%20Settings/troy.sellers/Desktop/jbossws-n
ative-bin-dist/deploy/bin/customer.wsdl

[ERROR] undefined attribute 'soapenc:arrayType'
  line 116 of file:/C:/Documents%20and%20Settings/troy.sellers/Desktop/jbossws-n
ative-bin-dist/deploy/bin/customer.wsdl

Failed to invoke WsImport
java.lang.NullPointerException
        at com.sun.tools.xjc.reader.internalizer.SCDBasedBindingSet.apply(SCDBas
edBindingSet.java:237)
        at com.sun.tools.xjc.ModelLoader.createXSOM(ModelLoader.java:518)
        at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompiler
Impl.java:232)
        at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompiler
Impl.java:85)
        at com.sun.tools.ws.processor.modeler.wsdl.JAXBModelBuilder.bind(JAXBMod
elBuilder.java:120)
        at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildJAXBModel(WS
DLModeler.java:2173)
        at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.internalBuildMode
l(WSDLModeler.java:173)
        at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLMo
deler.java:119)
        at com.sun.tools.ws.wscompile.WsimportTool.run(WsimportTool.java:148)
        at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumer
Impl.java:187)
        at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(Unknown Source)
        at org.jboss.wsf.spi.tools.cmd.WSConsume.main(Unknown Source)


Hope someone can help with this one? 

Cheers,
Troy


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192920#4192920

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192920


From do-not-reply at jboss.com  Fri Nov 28 05:44:10 2008
From: do-not-reply at jboss.com (ops)
Date: Fri, 28 Nov 2008 05:44:10 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Asymmetric encryption with
	ws-security?
Message-ID: <7284549.1227869050839.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hello again,

sorry, but this question is urgent. I??ve already been trying several things and I??m going mad with this. Is there really no way to "download" the servers public key to the client? In my opinion it should be easy to attach the servers certificate to the soap message. Should I try asking the security forum?

Greets, Oliver

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192972#4192972

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192972



From do-not-reply at jboss.com  Fri Nov 28 08:35:18 2008
From: do-not-reply at jboss.com (Gitu)
Date: Fri, 28 Nov 2008 08:35:18 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Wrong minOccurs in wsdl generated
	by Jboss
Message-ID: <709329.1227879318110.JavaMail.jboss@colo-br-02.atl.jboss.com>

Yes , its the same question and I dont know how I missed it in search ,  but I can see u didnt get any reply so far . Did u get any solution for this ?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193022#4193022

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193022


From do-not-reply at jboss.com  Fri Nov 28 11:24:59 2008
From: do-not-reply at jboss.com (atai)
Date: Fri, 28 Nov 2008 11:24:59 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: consume WS error after update to
	JBossWS 2.0
Message-ID: <1206339.1227889499268.JavaMail.jboss@colo-br-02.atl.jboss.com>

I have a "unit-test" client, which doesn't need JBoss, or any JEE environment. I had JDK5 as my JRE System Library in Eclipse and I got the same problem. Running with JDK6, the problem was solved! 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193069#4193069

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193069


From do-not-reply at jboss.com  Fri Nov 28 12:33:36 2008
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 28 Nov 2008 12:33:36 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - Re: Asymmetric encryption with
	ws-security?
Message-ID: <32440544.1227893616172.JavaMail.jboss@colo-br-02.atl.jboss.com>

As far as I know what you are asking is not possible. There were some discussions about how ws-security works, along with complete examples, a while back: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=127824

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193093#4193093

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193093


From do-not-reply at jboss.com  Sun Nov 30 17:02:18 2008
From: do-not-reply at jboss.com (bschmoll1)
Date: Sun, 30 Nov 2008 17:02:18 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - WS-Security Username Token Password
	Digest
Message-ID: <20536524.1228082538852.JavaMail.jboss@colo-br-02.atl.jboss.com>

I'm having some dfficulty in converting a web service from a cleartext password to using a password digest. Following the directions from http://jbossws.jboss.org/mediawiki/index.php?title=WS-Security_options I've created a "JBossWSDigest" application policy in the login-config.xml 

  |     <application-policy name="JBossWSDigest">
  |   <authentication>
  |     <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required">
  |       <module-option name="usersProperties">props/jbossws-users.properties</module-option>
  |       <module-option name="rolesProperties">props/jbossws-roles.properties</module-option>
  |       <module-option name="hashAlgorithm">SHA</module-option>
  |       <module-option name="hashEncoding">BASE64</module-option>
  |       <module-option name="hashUserPassword">false</module-option>
  |       <module-option name="hashStorePassword">true</module-option>
  |       <module-option name="storeDigestCallback">org.jboss.ws.extensions.security.auth.callback.UsernameTokenCallback</module-option>
  |       <module-option name="unauthenticatedIdentity">anonymous</module-option>
  |     </login-module>
  |   </authentication>
  |     </application-policy>
  | 

The jboss-wsse-server.xml 

  | <?xml version="1.0" encoding="UTF-8"?>
  | <jboss-ws-security xmlns="http://www.jboss.com/ws-security/config"
  |                          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  |                          xsi:schemaLocation="http://www.jboss.com/ws-security/config 
  |                          http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">
  | 	 <config>
  | 		<requires/>
  | 		<username digestPassword="true" useNonce="true" useCreated="true"/> 
  | 		<authenticate>
  | 			<usernameAuth/>
  | 		</authenticate>
  | 		<!-- <timestamp ttl="300"/> -->
  | 	</config>
  | </jboss-ws-security>
  | 

When I call the service via soapUI the following is dumped in the server.log

  | 2008-11-28 12:24:04,065 DEBUG [org.jboss.ejb3.security.Ejb3AuthenticationInterceptor] Authentication failure
  | javax.security.auth.login.LoginException: storeDigestCallback callback failed
  | 	at org.jboss.security.auth.spi.UsernamePasswordLoginModule.createPasswordHash(UsernamePasswordLoginModule.java:409)
  | 	at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:209)
  | 	at org.jboss.security.auth.spi.UsersRolesLoginModule.login(UsersRolesLoginModule.java:152)
  | 	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:597)
  | 	at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
  | 	at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
  | 	at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
  | 	at java.security.AccessController.doPrivileged(Native Method)
  | 	at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
  | 	at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
  | 	at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:603)
  | 	at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:537)
  | 	at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:344)
  | 	at org.jboss.aspects.security.AuthenticationInterceptor.authenticate(AuthenticationInterceptor.java:123)
  | 	at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:66)
  | 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | 	at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:103)
  | 	at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:221)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:466)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134)
  | 	at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  | 	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:230)
  | 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
  | 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
  | 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
  | 	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:157)
  | 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
  | 	at java.lang.Thread.run(Thread.java:619)
  | Caused by: javax.security.auth.callback.UnsupportedCallbackException: Unrecognized Callback
  | 	at org.jboss.security.auth.callback.SecurityAssociationHandler.handle(SecurityAssociationHandler.java:128)
  | 	at javax.security.auth.login.LoginContext$SecureCallbackHandler$1.run(LoginContext.java:955)
  | 	at java.security.AccessController.doPrivileged(Native Method)
  | 	at javax.security.auth.login.LoginContext$SecureCallbackHandler.handle(LoginContext.java:951)
  | 	at org.jboss.security.auth.spi.UsernamePasswordLoginModule.createPasswordHash(UsernamePasswordLoginModule.java:399)
  | 	... 49 more
  | 
It seems like the exception is due to the "Unrecognized Callback" but I don't see what I'm missing in the configuration. 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193274#4193274

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193274


From do-not-reply at jboss.com  Sun Nov 30 17:37:19 2008
From: do-not-reply at jboss.com (peiguo)
Date: Sun, 30 Nov 2008 17:37:19 -0500 (EST)
Subject: [jbossws-users] [JBossWS] - get the native connection underneath
	the web service
Message-ID: <1878043.1228084639627.JavaMail.jboss@colo-br-02.atl.jboss.com>

Hi, 

I have a need to access some outside web services through jboss, and I am behind a firewall, so my jboss has to access that web service through https proxy. 

I knew in general how to set system properties such as https.proxyHost, proxyPort and nonProxyHosts etc. But this way, the setting will bencome global. Is there a way for me to get the actual https connection underneath the web service, so that I can configure that connection and that connection alone to use proxy? 

Thanks in advance! 
Peter
(This was originally posted in ejb3 forum, but I thought this forum is probably more appropriate. Sorry for this reposting.)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193276#4193276

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193276