April 2008 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Re: webservices ejb3 api usage

by heiko.braun＠jboss.com

In general the reason why the code resides with the EJB3 project is that WS just specifies the requirements (a bunch of interfaces) and _initially_ implements it in the EJB3 code base. Subsequent changes however should be implemented and verified (WS test suite) by the EJB3 team. Maybe I don't understand you correctly, but I still don't see a reason why any of the upcoming changes, may it be deployment or injection should affect the API in place. If you still see something missing please document the lacking features in terms of test cases. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144180#4144180 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144180

16 years, 5 months

1
0
0 / 0

[Design of EJB 3.0] - Re: webservices ejb3 api usage

by heiko.braun＠jboss.com

anonymous wrote : | Deployment handling should be done by an intermediate deployer. How | does the webservice meta data merge with the ejb3 meta data? | IMO there is no such thing as dedicated WS metadata. It's all part of the Ejb3 meta data. So this will be handled by whatever component parses the Ejb3 meta data. The WebServiceDeclaration interface addresses this. You can move it around, deprecate your sources or implement a new metadata representation. Just make sure the interface is offered to WS deployers. anonymous wrote : | As for injection. That should have happened before method invocation. I was thinking about a ThreadLocalStack construction which is injected during construction and set during invocation. | Right, that makes sense. Let's regard two pieces: 1) a web service invocation (SOAP, hit's jbossws) 2) an endpoint (i.e. EJB3) invocation that derives from 1 Currently the ws invocation model offers a callback (InvocationContexCallback) to access WS injection properties. This is passed on to the StatelessContainer (implements ServiceEndpointContainer). To me the order of injection vs. method invocation is an implementation detail of the EJB3 domain. If I understand you correctly we speak about dependency injection before the bean becomes method-ready, right? So I'd say leave ServiceEndpointContainer interface in place and get Ejb3 problems sorted internally. Up to now I don't see why this should affect the WS-EJB3 API in place. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144179#4144179 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144179

16 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Cluster Singleton listeners

by tfennelly

"Welle" wrote : Making the Quartz singleton/clustered aware should fix it for ScheduledListeners. Perhaps add a flag indicating if the listener really should be singleton or not. I think it would be configured on the schedule instance and all schedule listeners "listening" to that schedule would then pick it up. "Welle" wrote : Perhaps all other listeners that uses intervalls etc (for example FTP) should then extend the ScheduledListener so we get the same functionality, or? Now that you say it... I think they already do :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144178#4144178 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144178

16 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - ConfigurationException:axis.deployment.wsdd.WSDDException

by aneesh62003

WE are having a webservice client in our application. During the deplyment time we are facing an issue. Our jboss version is. Jboss 4.02 Rc1 Axis version. Implementation-Version: 1.2RC3 2236 February 28 2005 we have put the jboss-net-client.jar in the lib path from the docs Now we are getting a Classcastexception while trying to create a call to the webservice. ExceptionStrackTrace is as shown below. org.apache.axis.deployment.wsdd.WSDDException: java.lang.ClassCastException java.lang.ClassCastException at org.apache.axis.encoding.ser.BaseSerializerFactory.createFactory(BaseSerializerFactory.java:261) at org.apache.axis.deployment.wsdd.WSDDDeployment.deployMapping(WSDDDeployment.java:341) at org.apache.axis.deployment.wsdd.WSDDDeployment.getTypeMappingRegistry(WSDDDeployment.java:520) at org.apache.axis.configuration.FileProvider.getTypeMappingRegistry(FileProvider.java:292) at org.apache.axis.AxisEngine.getTypeMappingRegistry(AxisEngine.java:359) at org.apache.axis.MessageContext.getTypeMappingRegistry(MessageContext.java:452) at org.apache.axis.client.Call.getTypeMapping(Call.java:2156) at org.apache.axis.client.Call.registerTypeMapping(Call.java:2191) at org.apache.axis.client.Call.registerTypeMapping(Call.java:2234) at com.eppsClient.ShowPPCWSBindingStub.createCall(Unknown Source) at com.eppsClient.ShowPPCWSBindingStub.showPPC(Unknown Source) at com.eppsClient.ShowPPCWSClient.getBalance(Unknown Source) at com.epps.FrontController.service(Unknown Source) 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.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:147) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:53) 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:825) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:743) 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:534) at org.apache.axis.deployment.wsdd.WSDDDeployment.deployMapping(WSDDDeployment.java:360) at org.apache.axis.deployment.wsdd.WSDDDeployment.getTypeMappingRegistry(WSDDDeployment.java:520) at org.apache.axis.configuration.FileProvider.getTypeMappingRegistry(FileProvider.java:292) at org.apache.axis.AxisEngine.getTypeMappingRegistry(AxisEngine.java:359) at org.apache.axis.MessageContext.getTypeMappingRegistry(MessageContext.java:452) at org.apache.axis.client.Call.getTypeMapping(Call.java:2156) at org.apache.axis.client.Call.registerTypeMapping(Call.java:2191) at org.apache.axis.client.Call.registerTypeMapping(Call.java:2234) at com.eppsClient.ShowPPCWSBindingStub.createCall(Unknown Source) at com.eppsClient.ShowPPCWSBindingStub.showPPC(Unknown Source) at com.eppsClient.ShowPPCWSClient.getBalance(Unknown Source) at com.epps.FrontController.service(Unknown Source) 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.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:147) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:53) 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:825) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:743) 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:534) at org.apache.axis.deployment.wsdd.WSDDDeployment.deployMapping(WSDDDeployment.java:360) at org.apache.axis.deployment.wsdd.WSDDDeployment.getTypeMappingRegistry(WSDDDeployment.java:520) at org.apache.axis.configuration.FileProvider.getTypeMappingRegistry(FileProvider.java:292) at org.apache.axis.AxisEngine.getTypeMappingRegistry(AxisEngine.java:359) at org.apache.axis.MessageContext.getTypeMappingRegistry(MessageContext.java:452) at org.apache.axis.client.Call.getTypeMapping(Call.java:2156) at org.apache.axis.client.Call.registerTypeMapping(Call.java:2191) at org.apache.axis.client.Call.registerTypeMapping(Call.java:2234) at com.eppsClient.ShowPPCWSBindingStub.createCall(Unknown Source) at com.eppsClient.ShowPPCWSBindingStub.showPPC(Unknown Source) at com.eppsClient.ShowPPCWSClient.getBalance(Unknown Source) at com.epps.FrontController.service(Unknown Source) 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.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:147) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:53) 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:825) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:743) 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:534) 2008-04-15 14:00:14,321 ERROR [com.epps.FrontController] PPC Inquiry Unknown Exception AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException faultSubcode: faultString: Failure trying to get the Call object; nested exception is: java.lang.NullPointerException faultActor: faultNode: faultDetail: Failure trying to get the Call object; nested exception is: java.lang.NullPointerException at com.eppsClient.ShowPPCWSBindingStub.createCall(Unknown Source) at com.eppsClient.ShowPPCWSBindingStub.showPPC(Unknown Source) at com.eppsClient.ShowPPCWSClient.getBalance(Unknown Source) Expecting ur help.. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144175#4144175 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144175

16 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Cluster Singleton listeners

by Welle

Making the Quartz singleton/clustered aware should fix it for ScheduledListeners. Perhaps add a flag indicating if the listener really should be singleton or not. Perhaps all other listeners that uses intervalls etc (for example FTP) should then extend the ScheduledListener so we get the same functionality, or? /AW View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144173#4144173 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144173

16 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Where to create your tests

by thomas.diesler＠jboss.com

Folks, on our road to pluggable WS stacks we migrated most jaxws tests over to framework (i.e. our common jaxws testsuite) http://jira.jboss.org/jira/browse/JBWS-2096 When you create a new test, please first decide whether the test addresses #1 a general jaxws issues that should apply to all stacks #2 a issue that is specific to the native code base Stuff we know it will not work across stacks but should, should still go to framework. In that way we have excludes for all stacks the do not support a certain functionality that in turn will make it into our release notes. Bottom Line: jaxws tests added to native should be rare View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144172#4144172 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144172

16 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: ClassLoader behaviour on remote clustering tests

by kabir.khan＠jboss.com

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

16 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1316 - Add support for a configurable time toleranc

by thomas.diesler＠jboss.com

Yes, its fine. Please monitor hudson when your change becomes effective View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144162#4144162 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144162

16 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Cluster Singleton listeners

by tfennelly

Hi Anders. Sorry for not responding to the original post. So wrt the ScheduledListeners, I think the way to make them clusterable is by making the underlying Quartz schedule jobs clusterable. I already created a JIRA for this... JBESB-1646. As far as the other transports are concerned... JMS Queues are clustered by nature if you configure the destinations and the JMS providers properly. HTTP endpoints... a load balancer FTP etc... then you might be into a shared cash type solution ala your JGroups suggestion View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144161#4144161 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144161

16 years, 5 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1316 - Add support for a configurable time toleranc

by richard.opalka＠jboss.com

I don't see any problems to commit this to the trunk ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144158#4144158 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144158

16 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2008