December 2007 - jbossws-dev - Jboss List Archives

[Fwd: Re: [jbossws-dev] 2.0.3 Release planning]

by Alessio Soldano

This was sent to Heiko only, sorry. What do you think about jbws-1505? -------- Messaggio Originale -------- Oggetto: Re: [jbossws-dev] 2.0.3 Release planning Data: Mon, 10 Dec 2007 23:20:17 +0100 Da: Alessio Soldano <asoldano(a)redhat.com> A: Heiko Braun <hbraun(a)redhat.com> Referenze: <1197296930.6981.24.camel(a)localhost.localdomain> Hi Folks, > * End of this week (14.12) is JIRA freeze. Please take a look > at your current assignments and make sure it meets your dev planning. > I'll take a deeper look at my jira issues tomorrow, however I see JBWS-1505 has been assigned to me and currently passes with JAX-WS, it's a JAX-RPC only issue. Do we really want to work on this or is the community supposed to fix it ? Cheers Alessio

17 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: Test org.jboss.test.webservice.jbws309.JBWS309TestCase

by anil.saldhana＠jboss.com

After the first run of the target, your JACC server config is created, so you can follow the regular procedure, if you wish from the second time onwards: | ./run.sh -b your_ip_address -c jacc | In the test suite module. | ant -Dtest=org.jboss.test.webservice.jbws309.JBWS309TestCase one-test | You know the drill. :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112822#4112822 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112822

17 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Test org.jboss.test.webservice.jbws309.JBWS309TestCase

by anil.saldhana＠jboss.com

Thomas, this test case has been there since JBoss 4.0. It is run under the JACC configuration. Currently there are issues when the JBoss instance is bound to an IP address. I am wondering if you can take a look at the deployment descriptors for this test case in AS5 test suite to see if it is tied to localhost..... The way to start the jacc target is summarized in the first post of the following thread. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=125875 Your test is the last in the list. The entire suite of tests take around 8-10m. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112821#4112821 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112821

17 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: Contents of the SOAP request

by alessio.soldano＠jboss.com

An explanation that may help, hope it's not too late. The reason why your first approach results in your handler being called before the wsse one is that the latter is configured as a post-handler while yours is an endpoint-handler. You would need your handler to be a post-handler, however afaik this can only be achieved editing the jbossws configurations in standard-jaxws-client-config.xml. Speaking of the second approach, where did you do that call? where is the handlerChain instance from? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112677#4112677 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112677

17 years, 1 month

1
0
0 / 0

Limited connectivity

by Heiko Braun

I am at Javapolis the next two days. Therefore connectivity may be limited, so bare with be. I'll try to check my mails regularly. Regards, Heiko

17 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM client examples

by richard.opalka＠jboss.com

Hi Team/Comunity The client side architecture documentation is here: http://jbws.dyndns.org/mediawiki/index.php?title=WS_Reliable_Messaging Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111312#4111312 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111312

17 years, 1 month

2
1
0 / 0

[Design of JBoss Web Services] - org.jboss.axis.ConfigurationException: No engine configurati

by dfillis

Hi All, I am trying to access a deployed webservice on JBoss-4.0.3SP1 and get the following error - org.jboss.axis.ConfigurationException: No engine configuration file - aborting! I know that this error has been fixed jbossws in jboss-4.2.x However I am unable to migrate to jboss-4.2.x due to a dependency. I would appreciate it very much if someone can help me with a workaround on JBoss-4.0.3SP1. An extract from the log file follows I am very desperate for a solution so your help would be dearly appreciated!! Best regards Denzil org.jboss.axis.ConfigurationException: No engine configuration file - aborting! at org.jboss.axis.configuration.FileProvider.configureEngine(FileProvider.java:222) at org.jboss.axis.AxisEngine.init(AxisEngine.java:150) at org.jboss.axis.AxisEngine.(AxisEngine.java:132) at org.jboss.axis.client.AxisClient.(AxisClient.java:88) at org.jboss.axis.client.Service.getAxisClient(Service.java:370) at org.jboss.axis.client.Service.(Service.java:144) at com.mpilo.fourier.dms.wsmanager.subscriber.OKMAuthServiceLocator.(OKMAuthServiceLocator.java:10) at com.mpilo.fourier.dms.wsmanager.AuthModuleWSManager.login(AuthModuleWSManager.java:63) at com.mpilo.fourier.dms.web.action.SaveOrCreateDocumentAction.execute(SaveOrCreateDocumentAction.java:66) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:482) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) at org.jboss.axis.configuration.FileProvider.configureEngine(FileProvider.java:222) at org.jboss.axis.AxisEngine.init(AxisEngine.java:150) at org.jboss.axis.AxisEngine.(AxisEngine.java:132) at org.jboss.axis.client.AxisClient.(AxisClient.java:88) at org.jboss.axis.client.Service.getAxisClient(Service.java:370) at org.jboss.axis.client.Service.(Service.java:144) at com.mpilo.fourier.dms.wsmanager.subscriber.OKMAuthServiceLocator.(OKMAuthServiceLocator.java:10) at com.mpilo.fourier.dms.wsmanager.AuthModuleWSManager.login(AuthModuleWSManager.java:63) at com.mpilo.fourier.dms.web.action.SaveOrCreateDocumentAction.execute(SaveOrCreateDocumentAction.java:66) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:482) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110645#4110645 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110645

17 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM client examples

by richard.opalka＠jboss.com

Hi team/community the WS-RM public API - org.jboss.ws.extensions.wsrm.api.* was simplified and javadoc was added there. Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110457#4110457 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110457

17 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: Proxy Thread Safety

by thomas.diesler＠jboss.com

anonymous wrote : | More computing sins are committed in the name of efficiency (without necessarily achieving it) than for any other single reason - including blind stupidity. | - W.A. Wulf View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110129#4110129 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110129

17 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: Proxy Thread Safety

by richard.opalka＠jboss.com

anonymous wrote : Thomas Diesler said: | | The proxy holds state that is related to the invocation itself e.g. attachment parts, unbound header values, etc, thus it can't be shared via multiple threads. | Thanks Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110125#4110125 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110125

17 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev December 2007