October 2007 - jbossws-users - Jboss List Archives

[JBossWS] - Re: Deployed service statistics

by oskar.carlstedt

Hi! Just take a look in the source code for the jbossws web application and you´re up and running. It's really simple when you find the correct source. Anyway, here is a code snippet ... | // get SPI provider and endpoint registry | SPIProvider spiProvider = SPIProviderResolver.getInstance() | .getProvider(); | EndpointRegistry epRegistry = spiProvider.getSPI( | EndpointRegistryFactory.class).getEndpointRegistry(); | | // loop over all endpoints | Set<ObjectName> objectNames = epRegistry.getEndpoints(); | for (ObjectName objectName : objectNames) { | | // get the endpoint by using its name | Endpoint endpoint = epRegistry.getEndpoint(objectName); | | ... | } | Cheers, Oskar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097413#4097413 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097413

18 years

1
0
0 / 0

[JBossWS] - AOP with web service

by abdujaparov

Hi I heve developed a web service for jbossws and I would apply an aspect to the methods of this web service. I have written the aspect code and the xml file for jbossaop and I have installed jboss aop on jboss4.2.1 following the jboss aop instruction (I've copied this directory jboss-aop-jdk50.deployer in the deploy directory of jboss4.2.1). My war file is composed so: directory META-INF: directory WEB-INF: -file web.xml; -file jboss-aop.xml; +directory classes: -file jboss-aop.xml; +directory xml: -XMLJDomWriterStat.class -XMLSaxReaderStat.class +directory services: -ServiceAOP.class; -ServiceAOPAspect.class. My web.xml file is so composed: | <?xml version="1.0" encoding="UTF-8"?> | | <web-app version="2.5" | 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 http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"> | | <servlet> | <servlet-name>ServiceAOP</servlet-name> | <servlet-class>service.ServiceAOP</servlet-class> | </servlet> | | <servlet-mapping> | <servlet-name>ServiceAOP</servlet-name> | <url-pattern>/*</url-pattern> | </servlet-mapping> | | </web-app> | My jboss-aop.xml is the following: | <?xml version="1.0" encoding="UTF-8" standalone="yes"?> | <aop> | <aspect class="service.ServiceAOPAspect" scope="PER_VM"/> | <bind pointcut="execution(public double service.ServiceAOP->fattoriale(int))"> | <advice aspect="service.ServiceAOPAspect" name="statistics"/> | </bind> | </aop> | What have I to do for running aop on web service? Thanks all, bye bye. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097400#4097400 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097400

18 years

1
0
0 / 0

[JBossWS] - Re: How to handle namespace generation?

by cch＠jboss

*push* Nobody has any hint for me? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097386#4097386 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097386

18 years

1
0
0 / 0

[JBossWS] - org.jboss.ws.WSException: Cannot find java method

by ZazzaZ

Hi, I used wscompile to generate a webservice starting from a correct WSDL. Deploy went OK, but when I run the client class to test the service I got the following exception in server-side log. | | org.jboss.ws.WSException: Cannot find java method: controlloAccessoOperation | at org.jboss.ws.metadata.OperationMetaData.getJavaMethod(OperationMetaData.java:213) | at org.jboss.ws.binding.EndpointInvocation.getJavaMethod(EndpointInvocation.java:82) | at org.jboss.ws.server.ServiceEndpointInvokerJSE.invokeServiceEndpoint(ServiceEndpointInvokerJSE.java:87) | at org.jboss.ws.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:115) | at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:209) | at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:355) | at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:115) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) | at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:76) | 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:96) | 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.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) | at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) | 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:869) | at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) | 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) | | | | I generated the files with the following files: wscompile input | | <?xml version="1.0" encoding="UTF-8"?> | <configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config"> | <wsdl location="src/main/resources/web/wsdl/ControlloAccesso.wsdl" | packageName="org.jbpm.bpel.login"> |  | </wsdl> | </configuration> | | WSDL file | | <?xml version="1.0" encoding="UTF-8"?> | <definitions name="ControlloAccesso" targetNamespace="http://j2ee.netbeans.org/wsdl/ControlloAccesso" | xmlns="http://schemas.xmlsoap.org/wsdl/" | xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" | xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" | xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://j2ee.netbeans.org/wsdl/ControlloAccesso" xmlns:ns="http://xml.netbeans.org/schema/LoginTypes" xmlns:plink="http://schemas.xmlsoap.org/ws/2004/03/partner-link/"> | <types> | <xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/ControlloAccesso"> | <xsd:import namespace="http://xml.netbeans.org/schema/LoginTypes" schemaLocation="types.xsd"/> | </xsd:schema> | </types> | <message name="ControlloAccessoOperationRequest"> | <part name="part1" type="ns:Credenziali"/> | </message> | <message name="ControlloAccessoOperationReply"> | <part name="part1" type="ns:Identificato"/> | </message> | <portType name="ControlloAccessoPortType"> | <operation name="ControlloAccessoOperation"> | <input name="input1" message="tns:ControlloAccessoOperationRequest"/> | <output name="output1" message="tns:ControlloAccessoOperationReply"/> | </operation> | </portType> | <binding name="ControlloAccessoBinding" type="tns:ControlloAccessoPortType"> | <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/> | <operation name="ControlloAccessoOperation"> | <soap:operation/> | <input name="input1"> | <soap:body use="literal" namespace="http://j2ee.netbeans.org/wsdl/ControlloAccesso"/> | </input> | <output name="output1"> | <soap:body use="literal" namespace="http://j2ee.netbeans.org/wsdl/ControlloAccesso"/> | </output> | </operation> | </binding> | <service name="ControlloAccessoService"> | <port name="ControlloAccessoPort" binding="tns:ControlloAccessoBinding"> | <soap:address location="http://localhost:18181/ControlloAccessoService/ControlloAccessoPort"/> | </port> | </service> | <plink:partnerLinkType name="ControlloAccessoPartner"> |  | <plink:role name="ControlloAccessoPortTypeRole" portType="tns:ControlloAccessoPortType"/> | </plink:partnerLinkType> | </definitions> | | Imported schema | | <?xml version="1.0" encoding="UTF-8"?> | | <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" | targetNamespace="http://xml.netbeans.org/schema/LoginTypes" | xmlns:tns="http://xml.netbeans.org/schema/LoginTypes"> | <xsd:complexType name="Credenziali"> | <xsd:sequence> | <xsd:element name="nome" type="xsd:string"></xsd:element> | <xsd:element name="password" type="xsd:string"></xsd:element> | </xsd:sequence> | </xsd:complexType> | <xsd:complexType name="Identificato"> | <xsd:sequence> | <xsd:element name="Esito" type="xsd:string"></xsd:element> | </xsd:sequence> | </xsd:complexType> | </xsd:schema> | | web.xml file | | <?xml version="1.0" encoding="UTF-8"?> | <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee | http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"> | |  | <servlet> | <servlet-name>controlloServlet</servlet-name> | <servlet-class> | org.jbpm.bpel.login.Impl | </servlet-class> | </servlet> | <servlet-mapping> | <servlet-name>controlloServlet</servlet-name> | <url-pattern>/controllo</url-pattern> | </servlet-mapping> | | </web-app> | | And finally the webservices.xml file | | <?xml version="1.0" encoding="UTF-8"?> | <webservices version="1.1" xmlns="http://java.sun.com/xml/ns/j2ee" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee | http://java.sun.com/xml/ns/j2ee/j2ee_web_services_1_1.xsd"> | | <webservice-description> | | <webservice-description-name> | Controllo Autenticazione | </webservice-description-name> | <wsdl-file>WEB-INF/wsdl/ControlloAccesso.wsdl</wsdl-file> | <jaxrpc-mapping-file>WEB-INF/jaxrpc-mapping.xml</jaxrpc-mapping-file> | | <port-component> | | <port-component-name>ControlloAccessoPort</port-component-name> | <wsdl-port xmlns:portNS="http://j2ee.netbeans.org/wsdl/ControlloAccesso">portNS:ControlloAccessoPort</wsdl-port> | <service-endpoint-interface> | org.jbpm.bpel.login.ControlloAccessoPortType | </service-endpoint-interface> | <service-impl-bean> | <servlet-link>controlloServlet</servlet-link> | </service-impl-bean> | | </port-component> | | </webservice-description> | | </webservices> | | I hope my information are enought to get a solution. Bye View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097381#4097381 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097381

18 years

1
0
0 / 0

[JBossWS] - Re: avoid lazy-initialization exceptions

by thomas.diesler＠jboss.com

Hi John, please show us your SLSB and one of your entities. The JAXB default is to bind all public members. Please have a look at the JAXB spec for finer control. e.g. @XMLAccessType View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097369#4097369 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097369

18 years

1
0
0 / 0

[JBossWS] - Re: Deployed service statistics

by alessio.soldano＠jboss.com

Hi, unfortunately no tutorial available on this right now; however, once you understand a bit about JMX, it's quite straightforward. I suggest you to search a bit about jmx technology on the Internet. A brief JMX-console introduction is available here: http://wiki.jboss.org/wiki/Wiki.jsp?page=JMXConsole For sure in future we'll enhance our documentation covering this issues too, as said in the productivity threads mentioned above. If you think something in particular should be done, feel free to comment there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097359#4097359 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097359

18 years

1
0
0 / 0

[JBossWS] - Re: Deployed service statistics

by abdujaparov

Hi Alessio, I've read what you have highlited but I don't understand a lot. Does a tutorial/guide exist? If yes, where can I find it? With that informations I remain at the beginning point. Thanks, bye bye. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097354#4097354 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097354

18 years

1
0
0 / 0

[JBossWS] - Re: web service not found

by richard.opalka＠jboss.com

Hi, check your JBoss AS server log if there is some problem report available. Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097339#4097339 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097339

18 years

1
0
0 / 0

[JBossWS] - Re: Cannot obtain wsdl service (problem in JBoss 4.2 used to

by burakbayramli

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

18 years

1
0
0 / 0

[JBossWS] - Re: Schema generation with jboss jaxb

by richard.opalka＠jboss.com

Hi Gennady, currently there's no such commandline tool available in JBossWS. The only way how to get the XML schema generated via our tools is to provide java web service interface and use our wsprovide.sh(.bat) tool with --wsdl option. It will generate the wsdl file where's the types section. There you can find the schema generated via our tools. To provide you the implementation detail, our wsprovide tool uses com.sun.xml.bind.api.JAXBRIContext.generateSchema() method internally. So you can write such tool on your own using this knowledge or join our dev discussion here: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=121127 and report the tools you are missing in JBossWS. Your contribution is welcomed ;-) Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097336#4097336 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097336

18 years

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-users October 2007