December 2006 - jbossws-users - Jboss List Archives

[JBossWS] - Re: Does JBoss WS use any Swing or AWT classes?

by zurchman

You mean a non-descript, default java icon shows up in the dock? I've noticed that happening. In fact, I've got one in my dock right now I don't think the behavior is specific to JBossWS, though, and I'm not sure you could call it a problem. I think you may be able to observe this behavior after running any JBoss application for any length of time. Related to output/logging maybe? OS X 10.4.8/JDK 1.5.0_06/JBoss 4.0.5 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994324#3994324 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994324

19 years, 4 months

1
0
0 / 0

[JBossWS] - Does JBoss WS use any Swing or AWT classes?

by chris.laprun＠jboss.com

I'm using OS X and each time my app does something WS-related a new application named org.jboss.Main pops up. Is anyone else experiencing the same problem? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994318#3994318 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994318

19 years, 4 months

1
0
0 / 0

[JBossWS] - Re: JSR-181 Endpoint ClassCastException

by becalvert

jhudson, how did you get the NullPointerException to go away? I have the same problem with requesting the WSDL for a simple service too. Thanks in advance! --- HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception javax.servlet.ServletException: Servlet.init() for servlet SearchService threw exception org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) java.lang.Thread.run(Thread.java:595) root cause java.lang.NullPointerException org.jboss.ws.server.ServiceEndpointManagerFactory.getServiceEndpointManager(ServiceEndpointManagerFactory.java:51) org.jboss.ws.server.StandardEndpointServlet.initServiceEndpointManager(StandardEndpointServlet.java:136) org.jboss.ws.server.StandardEndpointServlet.init(StandardEndpointServlet.java:61) org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) java.lang.Thread.run(Thread.java:595) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994297#3994297 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994297

19 years, 4 months

1
0
0 / 0

[JBossWS] - Re: JBossWS 1.0.4 compatibility issues with Java SE 6.0?

by heiko.braun＠jboss.com

It's not yet been tested. Our current target JDK are 1.4 and 1.5. I guess JBossWS will not be the only component affected by this upgrade. However it would interesting if you could share your experiences with us here. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994178#3994178 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994178

19 years, 4 months

1
0
0 / 0

[JBossWS] - Re: Upgrading 4.0.4 to 4.0.5

by heiko.braun＠jboss.com

Looks like you are using stale sampeles. Where did you get those? The current AS versions ship with JBossWS a replacement for the Axis based one. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994174#3994174 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994174

19 years, 4 months

1
0
0 / 0

[JBossWS] - Run-time mapping problem (4.0.3)

by orfordi

I'm working on a project that's using JBoss 4.0.3. This version does not come with "wstools". The documentation talks about using JWSDP's "wscompile", but that gave me some exceptions (no public constructors on some of the enum-type classes), so I'm using "wstools" from an installation of the latest JBoss and WS addon. So, I've got my soap definition xml file and have used wstools to generate my wsdl and my mapping xml files. I've added the dummy servlet definition to web.xml and have also created the webservices.xml file that refers to my mapping file. The server now exposes the wsdl under ?wsdl which is good. I've imported this into VS.NET and am trying to call the method. I get a mapping exception. I had to use "document" style SOAP rather than "rpc" because VS2003 could not understand the WSDL when I tried "rpc". So I'm trying to work out what's happening with my mapping. Note that the file is not called "jaxrpc-mapping.xml", I've prefixed it with something else, but I've checked that it's in WEB-INF and my WEB-INF\webservices.xml file refers to the correctly named mapping file. Any suggestions? Thanks in advance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994157#3994157 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994157

19 years, 4 months

1
0
0 / 0

[JBossWS] - Re: Upgrading 4.0.4 to 4.0.5

by bobstopper

I'm having the same issue, but simply trying to run through the tutorial (Duke's Bank, section 5.2). Unfortunately, I get: java.lang.NoClassDefFoundError: org/jboss/axis/wsdl/Java2WSDL when I try to build using the wsdl target. I've seen some mention of a wstool[s] target, but cannot locate this anywhere. Please help! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994022#3994022 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994022

19 years, 4 months

1
0
0 / 0

[JBossWS] - question on JBoss Classpath & JBossWS4EE

by Yueh2k6

Hi, For each application (WAR, or EAR) you deploy on JBoss, how do you specify classpath PER application ? or is it not possible? there must be some config file you can set to specify the right JARs for each application? According to the webservice stack listed at http://wiki.jboss.org/wiki/Wiki.jsp?page=WebServiceStacks JBoss 4.0 supports JBOssWS4EE. How do you use JBossWS4EE to generate java stubs from WSDLs (similar to the WSDL2JAVA tool used by Axis). These questions are urgent, any answers are greatly appreciated !! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994007#3994007 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994007

19 years, 4 months

1
0
0 / 0

[JBossWS] - Request didn't include a SOAP Message

by bertrand.njiipwo

Sorry for doppelt posting. I don't know if this issue is related to the jbpm or the JBossWS forum. My problem: when a running BPEL process call a web service. There is no SOAPMessage in the request send to the web service. How is this possible inside a workflow with jPBM-BPEL ? The service is well running and sending a SOAP Message to the service regarding his WSDL-specification is successfull. Is this issue related to the specification of the location of the soap:address-Element in the service.imp.wsdl? I mean the location of the wsdl file and the soap:adress-Refence are two things different not? If i specify the soap:adress-Refence as http://127.0.0.1:8089/context/serviceName i mean it's also OK. The SOAP message i'm sending will be included insinde the HTTP-Request to this resource. Where is the problem hier? can some one help me please ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993933#3993933 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993933

19 years, 4 months

1
0
0 / 0

[JBossWS] - JBossWS 1.0.4 compatibility issues with Java SE 6.0?

by rayymlai

I had the JSR181EJB3 example from JBossWS 1.0.3/1.0.4 running well on JBoss AS 4.0.4/4.0.5 (after some painful patches). After I upgrade my JDK to 6.0, the same example generates the exception UnsupportedOperationException. I try to remove the javax.xml.SOAPMessage*.class from the jbossws-client.jar and let the example uses Java SE 6.0's JAX-WS API. but it seems that there are more APIs impacted. Java SE 6.0 provides amazing JAXWS 2.0 support. You can use its embedded HTTP web server to publish web services. New JAXWS 2.0 APIs are provided. I'd assume the current JBossWS 1.0.4's JAXWS API is not sync up with the latest JAXWS 2.0 yet. similar issue posted at http://www.jboss.org/index.html?module=bb&op=viewtopic&t=95479 Perhaps JBossWS team can advise the compatibility issue. thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993911#3993911 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993911

19 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-users December 2006