Netbeans Web Service GUI
Hi everyone,
I'd really appreciate any help on this matter. I'm trying to build a GUI for a web service. I want the GUI to accept input from the user which is converted to a soap request which is then sent to a server to be processed, and a response is sent back. I want to format the response so that it is readable by the end user. So basically, the server does all the processing; all I have to do is produce the soap request, send it by soap over http and then parse the response from the server.
I've made a project in Netbeans with WDSL, BPEL mapper etc. I don't really know how to contact the server to send the soap request.
Could someone please give me some guidelines on how to do this? I'm completely new to Java but I have a basic understanding of WSDL, XML schema etc.
Again, any help much appreciated,
Ruth
hey sabatier,
I haven't done webservices with netbeans, but I have done it with Eclipse (using xfire), and here is what I can tell you.
Let's say you create a webservice that takes an string input. On the client side, after the user puts in whatever string this is, you build the call to the webservice by using the webservice stubs. It will then wrap the user input to the soap message and send it. It should be as simply as that. With all the tech out today, you shouldn't have to write your own soap messages.
Whatever your webservice returns, if it is a string result, again, it should be returned to you only as a string. All the work of extracting the return from the soap message should happen under the hood.
Similar Messages
-
Multiple references to web services in EJBs
Hi
Would like to know if its possible to reference EJB web services dynamically from fields in a database. Basically, I would have the EJB installed on multiple servers and need to be able to invoke it after looking up the address of the server in the database. Currently I'm using a NetBeans Web Service Reference in a JSP project to call the EJB.
Regards
LionelHere [it is|http://blog.vinodsingh.com/2008/09/building-jax-ws-web-service.html] with source code.
-
Creating Web Services using Netbeans GUI only
Hi all,
Creating, deploying & testing simple web-services through Netbeans point-n-click interface is quite simple (demo at: http://download.java.net/javaee5/screencasts/hello-simple-glassfish/). The demo shows a very simple service creation scenario, accepting and returning String types only. The service can easily be tested using the GUI option 'Test Web Service', which simply test the service through a simple web page at http://localhost:8080/MyWebApplication/MyWebService?Tester
In a similar manner, I am trying to implement a web service (a little complex one, accepting and returning custom types) using Netbeans GUI only. Versioning information I am using are as follows:
NetBeans IDE 6.1
Sun Java System Application Server 9.1_02 (build b04-fcs)
JAX-WS 2.1.3.1
Roughly speaking, the service's method signature I am using is shown below:
public abstract myclass.X MyService.serviceMethod( myclass.X )
Since it uses a custom type in parameter and return-types, the web-based test doesn't work any more. I wrote a separate client class to invoke the service using client-side stub classes (suppose to be generated by JAX-WS generated classes). The client code looks like as follows:
public class ServiceClient {
public static void main(String[] args) {
MyService srv = new MyService ().getMyServicePort();
X xin= new X();
X xout= srv.serviceMethod( xin );
System.out.println( "Result: "+ xout.toString());
Netbeans shows a compiler error on "MyService srv = new MyService ().getMyServicePort();
Is it possible to get it resolved without making use of ant scripts for generating client-side artifacts (stubs etc.)?
Thanks,
irfanHello Sandy,
Have you installed the Sun Java System App Server or JWSDP? If so, please make sure that one of the libraries in your Netbeans project contains the jaxrpc-api and jaxrpc-impl jars (which seem to be necessary to run wscompile).
Netbeans ("standalone") doesn't seem to install the jaxrpx libraries and other jars required to compile and run webservices.
Regards,
Jonatan -
Trying to create a web service in NetBeans
Hi Folks let's cut right to the chase
I've followed the demos / tutorials and built a few simple web services running on glassfish / mysql / netBeans IDE. All well and good. What I really want now is to be able to return an XML document or a string with xml data from my service.
I tried building an XML document using xerces / document builder (hopefully this is familiar to you) Unfortunately, the results I get back are not XML encoded, and also as I add elements & attributes to my document, it often creates a transformException (which I don't get when doing it from the console). I also get an exception if I try to add two elements as children to the same parent, as indicated in the code snippet below - I don't know what I'm doing wrong there.
Document doc = DocumentBuilderFactory.newInstance().newDocumentBuilder().newDocument();
doc.createElement("Word");
Element top = doc.createElement("myapp");
Element word = doc.createElement("word");//new Element("word");
//Attr attr = doc.createAttribute("testval");
word.setAttribute("test", "חֹשֶׁך");
//word.setNodeValue("חֹשֶׁך");
word.setTextContent("חֹשֶׁך");
doc.appendChild(top);
top.appendChild(word);
Element word2 = doc.createElement("word");
top.appendChild(word2);So I redid my web service just using a PrintWriter / StringWriter, and at the end replacing '<' and '>' with < > That's all well and good, and I get back the proper response, with the xml tags showing. But I still get an error message: Service invocation threw an exception with message :
" com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 2 of 2-byte UTF-8 sequence.; Refer to the server log for more details"
(more details at the very bottom). As you may have noticed in the code snippet I posted above, I'm using strings of hebrew characters.
I don't understand how I can get a response back and STILL get a Service invocation exception message.
I also don't know how to fix whatever's causing the exception. Anyone dealt with this kind of thing before?
Thanks! (Code below)
private static void addWord(PrintWriter pw, Words w, List<Definition> definitions) {
//Element word = doc.createElement("word");//new Element("word");
pw.append("<Word>");
pw.append("<HW>" + w.getWord() + "</HW>");
// word.setTextContent(w.getWord());
// doc.appendChild(word);
for (Definition def : definitions) {
// Element definition = doc.createElement("Definition");
pw.append("<Definition>" + def.getDefinition() + "</Definition>");
// definition.setTextContent(def.getDefinition());
String pos = def.getPos();
if (pos == null) pos = "";
String stem = def.getStem();
if (stem == null) stem = "";
pw.append("<POS>" + pos + "</POS>");
pw.append("<Stem>" + stem + "</Stem>");
// Element posElem = doc.createElement("POS");
// posElem.setTextContent(pos);
// Element stemElem = doc.createElement("Stem");
// stemElem.setTextContent(stem);
// definition.setAttribute("POS", def.getPos());
// definition.setAttribute("stem", def.getStem());
// word.appendChild(definition);
// word.appendChild(posElem);
// word.appendChild(stemElem);
pw.append("</Word>");
}SOAP Response
Service invocation threw an exception with message : com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 2 of 2-byte UTF-8 sequence.; Refer to the server log for more details
Exceptions details : javax.xml.transform.TransformerException: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 2 of 2-byte UTF-8 sequence.
javax.servlet.ServletException: javax.xml.transform.TransformerException: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 2 of 2-byte UTF-8 sequence. at org.glassfish.webservices.monitoring.WebServiceTesterServlet.doPost(WebServiceTesterServlet.java:330) at org.glassfish.webservices.monitoring.WebServiceTesterServlet.invoke(WebServiceTesterServlet.java:106) at org.glassfish.webservices.EjbWebServiceServlet.service(EjbWebServiceServlet.java:114) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at com.sun.grizzly.http.servlet.ServletAdapter$FilterChainImpl.doFilter(ServletAdapter.java:1002) at com.sun.grizzly.http.servlet.ServletAdapter$FilterChainImpl.invokeFilterChain(ServletAdapter.java:942) at com.sun.grizzly.http.servlet.ServletAdapter.doService(ServletAdapter.java:404) at com.sun.grizzly.http.servlet.ServletAdapter.service(ServletAdapter.java:354) at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:168) at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:234) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59) at com.sun.grizzly.ContextTask.run(ContextTask.java:71) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513) at java.lang.Thread.run(Thread.java:662) Caused by: javax.xml.transform.TransformerException: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 2 of 2-byte UTF-8 sequence. at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:719) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:313) at org.glassfish.webservices.monitoring.WebServiceTesterServlet.dumpMessage(WebServiceTesterServlet.java:362) at org.glassfish.webservices.monitoring.WebServiceTesterServlet.doPost(WebServiceTesterServlet.java:320) ... 24 more Caused by: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 2 of 2-byte UTF-8 sequence. at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.invalidByte(UTF8Reader.java:684) at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.read(UTF8Reader.java:369) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1742) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipChar(XMLEntityScanner.java:1416) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2792) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transformIdentity(TransformerImpl.java:609) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:707)Okay I think I get what's happening this is just a problem with NetBeans printing the SOAP response. So I think I'm good
-
How to change the web service address of NetBeans generated WS client
I am currently experimenting with web services using netbeans and Sun Application Server.
Basically I am creating simple web services using net beans and then deploy them on the app server and then create another pfoject with web service reference to that web service to invoke the service.
My problem is when a project is deliverd to the production site the the client applications web service reference will need to be configured to refer to the production web service address. But when I looked at the generated web service client code the address is hard coded.
How can I change the address to the web service of a web service reference created in net beans either using some configuration file (without having to recompile the client) or at runtime.
Thanks in advancebump...
-
Error when creating web service client in netbeans
i tried to create a web service client from a wsdl and an error pops up:
web service client can not be created by jaxws:wsimport utility.
reason: com.sun.tools.xjc.api.schemacompiler.resetschema()v
There might be a problem during java artifacts creation: for example a name conflict in generated classes.
To detect the problem see also the error messages in output window.
You may be able to fix the problem in WSDL Customization dialog
(Edit Web Service Attributes action)
or by manual editing of the local wsdl or schema files, using the JAXB customization
(local wsdl and schema files are located in xml-resources directory).
end of error message
I am using netbeans 6.0 RC 2 and the bundled tomcat 6.0.13. Please help me.Hi Yatan
The error is mostly there may be some Duplicate variable/schema element decalared in the wsdl or the xsd referred in the wsdl. Like in WSDL for any Operations, most of the times, we use input and outputs as complex xsd element. We declare these xsd in the same file or in another file and import that in the .wsdl file. So check or validate your XSD file for any Duplicates.
In JDeveloper itself, I think, you can open XSD or WSDL and validate it from right click menu options like that.
Thanks
Ravi Jegga -
Import jax-ws web service created in netbeans 6.5
Hello,
I have seen a few posts on this but without a result, so trying again in case there has been some progress. First of all I ran the UsWeather example, imported the webservices etc. and this works. I then tried the same for my web service, jax-ws create via netbeans and this doesn't work. It is a simple calc function that should accept two integer, i and j and return the sum. From what I can make out it is because the parameters are somehow wrapped and are not visible via the creates action scripts
So when I run this sort of thing:
private var calc:CalcWSService = new CalcWSService;
var req:Add_request = new Add_request();
req.i = 2;
req.j = 3;
calc.add_request_var = req;
// Invoke the method
calc.add_send();
I get the error message
TypeError: Error #1009: Cannot access a property or method of a null object reference.
at Test/getMyCalc2()[Y:\FlexWorkspaces\TestWorkSpace\Test\src\Test.mxml:64]
at Test/___Test_Button4_click()[Y:\FlexWorkspaces\TestWorkSpace\Test\src\Test.mxml:92]
If I reference my web service as follows
<mx:WebService id="webService" wsdl="http://localhost:8080/CalcWSProject/CalcWSService?wsdl" >
<mx:operation name="add" resultFormat="object" result="display(event);">
<mx:request xmlns="" >
<i>2</i>
<j>4</j>
</mx:request>
</mx:operation>
</mx:WebService>
and run
webService.add.send();
then it works
The generated CalcWSService.as add function looks like this(i.e.the parameters appear to be hidden
public function add(add:Add):AsyncToken
var _internal_token:AsyncToken = _baseService.add(add);
_internal_token.addEventListener("result",_add_populate_results);
_internal_token.addEventListener("fault",throwFault);
return _internal_token;
Any way to get around the problem when importing the web services via the wizard?Result after navigating to: http://localhost:8084/HelloWS/HelloWS?xsd=1
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://hi.me.org/" version="1.0">
<xs:element xmlns:ns1="http://hi.me.org/" type="ns1:add" name="add"/>
<xs:complexType name="add">
<xs:sequence>
<xs:element type="xs:int" minOccurs="0" name="arg0"/>
<xs:element type="xs:int" minOccurs="0" name="arg1"/>
</xs:sequence>
</xs:complexType>
<xs:element xmlns:ns2="http://hi.me.org/" type="ns2:addResponse" name="addResponse"/>
<xs:complexType name="addResponse">
<xs:sequence>
<xs:element type="xs:int" minOccurs="0" name="return"/>
</xs:sequence>
</xs:complexType>
</xs:schema> -
National ID System Web Services (Netbeans)
Hi;
I want connect JAXRPC Web Services with NetBeans over https.
I have tried the exapmle at http://users.skynet.be/pascalbotte/rcx-ws-doc/jaxrpchandler.htm
It gives error = "port: {http://kps.nvi.gov.tr/WS}KPSSoap does not contain operation: ilListesiGetir"
Code:
URL url = new URL("https://kps.nvi.gov.tr/Mernis.KPS.Web.SI/KPS.asmx?WSDL");
QName serviceName=new QName("http://kps.nvi.gov.tr/WS", "KPS");
QName portName = new QName("http://kps.nvi.gov.tr/WS", "KPSSoap");
ServiceFactory factory = ServiceFactory.newInstance();
Service service = factory.createService( url, serviceName);
HandlerRegistry hr = service.getHandlerRegistry();
List handlerChain = hr.getHandlerChain(portName);
HandlerInfo hi = new HandlerInfo();
hi.setHandlerClass( KpsSecurityHandler.class);
handlerChain.add(hi);
//this line gives error
KPSSoap port = (KPSSoap) service.getPort(portName, KPSSoap.class);
ArrayOfIlBilgisi ilListesi = port.ilListesiGetir();
List liste=ilListesi.getIlBilgisi();
for (int i = 0; i < liste.size(); i++)
out.println( liste.indexOf(i) + "\n");
Note: I can connect "KPS" service and "KPSSoap" port succesfuly. But when i tried to connect operation "ilListesiGetir" it gives the error port: {http://kps.nvi.gov.tr/WS}KPSSoap does not contain operation: ilListesiGetir
NetBeans Version 6.1
Please help us.
Thanks.<%@ page language="java" import="java.util.*, java.io.*, javax.mail.*, java.net.*, org.apache.soap.util.xml.*, org.apache.soap.encoding.soapenc.BeanSerializer, org.apache.soap.encoding.*,org.apache.soap.*, org.apache.soap.rpc.*"%>
<%
try
out.println ("Starting");
System.out.println("heree");
Call call = new Call ();
System.out.println("here");
SOAPMappingRegistry soap = new SOAPMappingRegistry();
call.setTargetObjectURI ("http://tempuri.org/");
call.setMethodName ("EarnNValue");
call.setEncodingStyleURI("http://schemas.xmlsoap.org/soap/encoding/");
Vector params = new Vector ();
params.addElement (new Parameter("customer_id", String.class, "gauravbehl",Constants.NS_URI_SOAP_ENC));
params.addElement (new Parameter("channel_id", String.class, "C0002",Constants.NS_URI_SOAP_ENC));
params.addElement (new Parameter("category_id", String.class, "club",Constants.NS_URI_SOAP_ENC));
params.addElement (new Parameter("transaction_date", String.class, "16/07/04 14:41:20",Constants.NS_URI_SOAP_ENC));
params.addElement (new Parameter("parameter_id", String.class, "login",Constants.NS_URI_SOAP_ENC));
params.addElement (new Parameter("parameter_value", String.class, "1",Constants.NS_URI_SOAP_ENC));
call.setParams (params);
Response resp = call.invoke(new URL("http://203.199.76.2/api/earnnvalue.asmx"), "http://tempuri.org//EarnNValue") ;
if (resp.generatedFault ())
Fault fault = resp.getFault ();
System.out.println ("Something is wrong");
System.out.println (" Fault Code = " + fault.getFaultCode ());
System.out.println (" Fault String = " + fault.getFaultString ());
else
Parameter result = resp.getReturnValue ();
System.out.println (result.getValue ());
out.println (result.getValue ());
catch (Exception e)
System.out.println ("********Exception*******");
System.out.println (e);
out.println ("Ending");
%> -
Standalone Web Service clients in NetBeans with WSIT security
I'm having a problem create a secure app with NetBeans, any help would be appreciated, here's what I did:
Following the WSIT tutorial (http://java.sun.com/webservices/reference/tutorials/wsit/doc/index.html) I was able to create a Web Service with (for example) Username Authentication with Symmetric Key. I select the keystore as being the either the default development settings (I installed V3 certificates previously) or what I imagine are the same as them: keystore from domain1, alias xws-server and a username and password that I've created in the glassfish admin console. All good so far.
I then create a new web app servlet client, configuring the Web Service client with the corresponding cacerts keystore, alias xws-security-server from domain1 and the correct username and password. Deploy that and bingo, it works.
Try that again with a standalone Java client configuring the client reference in exactly the same way and using:
try { // Call Web Service Operation
uk.ac.ox.sddag.glassfish.server.SecureWSService service = new uk.ac.ox.sddag.glassfish.server.SecureWSService();
uk.ac.ox.sddag.glassfish.server.SecureWS port = service.getSecureWSPort();
int x = 1200;
int y = 36;
int result = port.add(x, y);
System.out.println("Result = "+result);
} catch (Exception ex) {
System.out.println("Exception:");
ex.printStackTrace();
}but this time, it doesn't work:
Exception:
javax.xml.ws.soap.SOAPFaultException: ERROR: No security header found in the message
at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:188)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
at $Proxy29.add(Unknown Source)
at securestandaloneclient.Main.main(Main.java:26)
Caused by: javax.xml.ws.soap.SOAPFaultException: ERROR: No security header found in the message
at com.sun.xml.ws.security.opt.impl.util.SOAPUtil.getSOAPFaultException(SOAPUtil.java:171)
at com.sun.xml.wss.provider.wsit.WSITServerAuthContext.validateRequest(WSITServerAuthContext.java:277)
at com.sun.xml.wss.provider.wsit.WSITServerAuthContext.validateRequest(WSITServerAuthContext.java:179)
at com.sun.enterprise.webservice.CommonServerSecurityPipe.processRequest(CommonServerSecurityPipe.java:168)
at com.sun.enterprise.webservice.CommonServerSecurityPipe.process(CommonServerSecurityPipe.java:129)
at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
at com.sun.enterprise.webservice.JAXWSServlet.doPost(JAXWSServlet.java:176)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:272)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:341)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:263)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:214)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)I'm assuming that it's something to do with the WSDL being used to create the request, here's what the source view for the web service reference says:
<?xml version="1.0" encoding="UTF-8"?><!-- Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3.1-hudson-417-SNAPSHOT. --><!-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3.1-hudson-417-SNAPSHOT. --><definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://server.glassfish.sddag.ox.ac.uk/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://server.glassfish.sddag.ox.ac.uk/" name="SecureWSService">
<ns1:Policy xmlns:ns1="http://schemas.xmlsoap.org/ws/2004/09/policy" wsu:Id="SecureWSPortBindingPolicy">
<ns1:ExactlyOne>
<ns1:All>
<ns4:SignedSupportingTokens xmlns:ns4="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns4:UsernameToken ns4:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient">
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns4:WssUsernameToken10></ns4:WssUsernameToken10>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns4:UsernameToken>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns4:SignedSupportingTokens>
<ns5:SymmetricBinding xmlns:ns5="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns5:AlgorithmSuite>
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns5:Basic128></ns5:Basic128>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns5:AlgorithmSuite>
<ns5:IncludeTimestamp></ns5:IncludeTimestamp>
<ns5:Layout>
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns5:Strict></ns5:Strict>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns5:Layout>
<ns5:OnlySignEntireHeadersAndBody></ns5:OnlySignEntireHeadersAndBody>
<ns5:ProtectionToken>
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns5:X509Token ns5:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/Never">
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns5:RequireIssuerSerialReference></ns5:RequireIssuerSerialReference>
<ns5:WssX509V3Token10></ns5:WssX509V3Token10>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns5:X509Token>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns5:ProtectionToken>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns5:SymmetricBinding>
<ns6:Wss11 xmlns:ns6="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<ns1:Policy>
<ns1:ExactlyOne>
<ns1:All>
<ns6:MustSupportRefEncryptedKey></ns6:MustSupportRefEncryptedKey>
<ns6:MustSupportRefIssuerSerial></ns6:MustSupportRefIssuerSerial>
<ns6:MustSupportRefThumbprint></ns6:MustSupportRefThumbprint>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
</ns6:Wss11>
<ns7:UsingAddressing xmlns:ns7="http://www.w3.org/2006/05/addressing/wsdl" ns1:Optional="true"></ns7:UsingAddressing>
</ns1:All>
</ns1:ExactlyOne>
</ns1:Policy>
<ns8:Policy xmlns:ns8="http://schemas.xmlsoap.org/ws/2004/09/policy" wsu:Id="SecureWSPortBinding_add_Input_Policy">
<ns8:ExactlyOne>
<ns8:All>
<ns9:EncryptedParts xmlns:ns9="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<ns9:Body></ns9:Body>
</ns9:EncryptedParts>
<ns10:SignedParts xmlns:ns10="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<ns10:Body></ns10:Body>
<ns10:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
<ns10:Header Namespace="http://www.w3.org/2005/08/addressing" Name="To"></ns10:Header>
<ns10:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
<ns10:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
<ns10:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
<ns10:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
<ns10:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"></ns10:Header>
<ns10:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="AckRequested"></ns10:Header>
<ns10:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="CreateSequence"></ns10:Header>
<ns10:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="Sequence"></ns10:Header>
<ns10:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="SequenceAcknowledgement"></ns10:Header>
</ns10:SignedParts>
</ns8:All>
</ns8:ExactlyOne>
</ns8:Policy>
<ns11:Policy xmlns:ns11="http://schemas.xmlsoap.org/ws/2004/09/policy" wsu:Id="SecureWSPortBinding_add_Output_Policy">
<ns11:ExactlyOne>
<ns11:All>
<ns12:EncryptedParts xmlns:ns12="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<ns12:Body></ns12:Body>
</ns12:EncryptedParts>
<ns13:SignedParts xmlns:ns13="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<ns13:Body></ns13:Body>
<ns13:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
<ns13:Header Namespace="http://www.w3.org/2005/08/addressing" Name="To"></ns13:Header>
<ns13:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
<ns13:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
<ns13:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
<ns13:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
<ns13:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing"></ns13:Header>
<ns13:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="AckRequested"></ns13:Header>
<ns13:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="CreateSequence"></ns13:Header>
<ns13:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="Sequence"></ns13:Header>
<ns13:Header Namespace="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" Name="SequenceAcknowledgement"></ns13:Header>
</ns13:SignedParts>
</ns11:All>
</ns11:ExactlyOne>
</ns11:Policy>
<types>
<xsd:schema>
<xsd:import namespace="http://server.glassfish.sddag.ox.ac.uk/" schemaLocation="http://localhost:8080/SecureApplication/SecureWSService?xsd=1"></xsd:import>
</xsd:schema>
</types>
<message name="add">
<part name="parameters" element="tns:add"></part>
</message>
<message name="addResponse">
<part name="parameters" element="tns:addResponse"></part>
</message>
<portType name="SecureWS">
<operation name="add">
<input message="tns:add"></input>
<output message="tns:addResponse"></output>
</operation>
</portType>
<binding name="SecureWSPortBinding" type="tns:SecureWS">
<ns14:PolicyReference xmlns:ns14="http://schemas.xmlsoap.org/ws/2004/09/policy" URI="#SecureWSPortBindingPolicy"></ns14:PolicyReference>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"></soap:binding>
<operation name="add">
<soap:operation soapAction="add"></soap:operation>
<input>
<ns15:PolicyReference xmlns:ns15="http://schemas.xmlsoap.org/ws/2004/09/policy" URI="#SecureWSPortBinding_add_Input_Policy"></ns15:PolicyReference>
<soap:body use="literal"></soap:body>
</input>
<output>
<ns16:PolicyReference xmlns:ns16="http://schemas.xmlsoap.org/ws/2004/09/policy" URI="#SecureWSPortBinding_add_Output_Policy"></ns16:PolicyReference>
<soap:body use="literal"></soap:body>
</output>
</operation>
</binding>
<service name="SecureWSService">
<port name="SecureWSPort" binding="tns:SecureWSPortBinding">
<soap:address location="http://localhost:8080/SecureApplication/SecureWSService"></soap:address>
</port>
</service>
</definitions>The contents of META-INF (The WSDL):
<?xml version="1.0" encoding="UTF-8"?><!-- Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3.1-hudson-417-SNAPSHOT. --><!-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3.1-hudson-417-SNAPSHOT. --><definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://server.glassfish.sddag.ox.ac.uk/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://server.glassfish.sddag.ox.ac.uk/" name="SecureWSService" xmlns:wsp="http://www.w3.org/ns/ws-policy" xmlns:sc="http://schemas.sun.com/2006/03/wss/client" xmlns:wspp="http://java.sun.com/xml/ns/wsit/policy">
<types>
<xsd:schema>
<xsd:import namespace="http://server.glassfish.sddag.ox.ac.uk/" schemaLocation="http://localhost:8080/SecureApplication/SecureWSService?xsd=1"></xsd:import>
</xsd:schema>
</types>
<message name="add">
<part name="parameters" element="tns:add"></part>
</message>
<message name="addResponse">
<part name="parameters" element="tns:addResponse"></part>
</message>
<portType name="SecureWS">
<operation name="add">
<input message="tns:add"></input>
<output message="tns:addResponse"></output>
</operation>
</portType>
<binding name="SecureWSPortBinding" type="tns:SecureWS">
<wsp:PolicyReference URI="#SecureWSPortBindingPolicy"/>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"></soap:binding>
<operation name="add">
<soap:operation soapAction="add"></soap:operation>
<input>
<soap:body use="literal"></soap:body>
</input>
<output>
<soap:body use="literal"></soap:body>
</output>
</operation>
</binding>
<service name="SecureWSService">
<port name="SecureWSPort" binding="tns:SecureWSPortBinding">
<soap:address location="http://localhost:8080/SecureApplication/SecureWSService"></soap:address>
</port>
</service>
<wsp:Policy wsu:Id="SecureWSPortBindingPolicy">
<wsp:ExactlyOne>
<wsp:All>
<sc:CallbackHandlerConfiguration wspp:visibility="private">
<sc:CallbackHandler default="example1" name="usernameHandler"/>
<sc:CallbackHandler default="password1" name="passwordHandler"/>
</sc:CallbackHandlerConfiguration>
<sc:TrustStore wspp:visibility="private" type="JKS" storepass="changeit" location="/Applications/NetBeans/glassfish-v2ur2/domains/domain1/config/cacerts.jks" peeralias="xws-security-server"/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
</definitions>The wsit-client:
<?xml version="1.0" encoding="UTF-8"?>
<definitions
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" name="mainclientconfig"
>
<import location="SecureWSService.xml" namespace="http://server.glassfish.sddag.ox.ac.uk/"/>
</definitions>This bug still isn't fixed.
Thank you, adding Glassfish's webservices-rt.jar does fix it. -
Objects, web services and netbeans
I am trying to make a web service that returns an array of objects (where each object is a small number of strings). I shall list what I have done, if you just want to read the problem skip to <PROBLEM>.
1) Wrote .wsdl file [1]
In netbeans:
2) Generated web service from WSDL:
A) New web application, using the sun application server
B) New Web Service From WSDL (this gives an error, Illegal character in path at index 18: file:/<path of wsdl file>)
C) Right click on web service, Refreash service. No error
D) Run project, test web service, seems to work, returns null.
3) Consumed service:
A) New general application,
B) In main method, right click / Web Service Client Resources / Call Web Service Operation
C) Select method (getparams(String))
D) Add import org.impress.PortType; as prompted
E) Run project, Result = null
Now I want to add some data to what I am passing. First I return a new namespace.webservice._new.Paramarrayel (what netbeans decided the method should return). The client now shows that something is returned (org.impress.Paramarrayel@1bb5c09).
<PROBLEM>
Now this is where I get stuck. I want to add the data, the client knows there should be a .getGetparamreturns() function in the returned org.impress.Paramarrayel object but I cannot figure out how to add it in the server. I have tryed extending the namespace.webservice._new.Paramarrayel and namespace.webservice._new.Paramreturns, and adding a Paramreturns as a member variable of Paramarrayel but .getGetparamreturns() returns null in the client.
Anyone able to help?
[1]
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2007 rel. 3 sp1 (http://www.altova.com) by andrew (Medical Research Council) -->
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://new.webservice.namespace" targetNamespace="http://new.webservice.namespace">
<wsdl:types>
<xs:schema targetNamespace="http://new.webservice.namespace" elementFormDefault="qualified" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<xs:element name="paramimpressidstring" type="xs:string"/>
<xs:complexType name="paramreturns">
<xs:sequence>
<xs:element name="name" nillable="true" type="xs:string"/>
<xs:element name="value" nillable="true" type="xs:string"/>
</xs:sequence>
</xs:complexType>
<xs:element name="paramarrayel">
<xs:complexType>
<xs:sequence>
<xs:element name="getparamreturns" nillable="true" type="tns:paramreturns"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</wsdl:types>
<wsdl:message name="getparamsRequest">
<wsdl:part name="impressid" element="tns:paramimpressidstring"/>
</wsdl:message>
<wsdl:message name="getparamsResponse">
<wsdl:part name="paramsarray" element="tns:paramarrayel"/>
</wsdl:message>
<wsdl:portType name="portType">
<wsdl:operation name="getparams">
<wsdl:input message="tns:getparamsRequest"/>
<wsdl:output message="tns:getparamsResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="impressBinding" type="tns:portType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="getparams">
<soap:operation soapAction="urn:#getparams"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="impress">
<wsdl:port name="impressport" binding="tns:impressBinding">
<soap:address location="http://impress.publicdevelopment.har.mrc.ac.uk/server.php"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>Yes it's true but Netbeans uses one of the existing SOAP implementations to do it. I'm almost sure that it uses one of the most popular implementations JAX-WS RI or Axis by default.
Regards,
Sławomir Wojtasiak -
NetBeans 5.5 and creating web services top-down
Is it possible to take a pre-written WDSL and create a web service from this in NetBeans 5.5. I've had a look at the NetBeans website but can't seem to find anything relevant to this. It only specifies how to create a web service bottom up from a Java class.
Thanks.SoapUI is only really used for testing web services i.e. you give it a WSDL and it'll generate sample requests with which you can then make calls to the web service.
I was thinking more along the lines of what Eclispse WTP allows you to do i.e. import an existing WSDL into your web project then generate the Java code for the web service (not client). This way the WSDL could be developed first before any code is written. -
Creating web service client with WSDL in NetBeans
NetBeans: 5.5
Java: 1.6
WSDL: http://jira.atlassian.com/rpc/soap/jirasoapservice-v2?wsdl
Using netbeans, I can't seem to successfully generate the stubs for a client based on the WSDL file above.
SoapUI ( www.soapui.org ) has no problems receiving and creating the client stubs using the same WSDL file.
The error I'm getting in the dialog is "Illegal attempt to exit early".
Further details from the output window reads as follows:
-=-
warning: src-resolve: Cannot resolve the name 'impl:ArrayOf_tns2_RemoteEntity' to a(n) 'type definition' component.
line 0 of file:/C:/Documents%20and%20Settings/Alexander%20Trauzzi/JavaApplication2/xml-resources/web-service-references/jirasoapservice-v2/wsdl/jira.atlassian.com/rpc/soap/jirasoapservice-v2.wsdl#types?schema2
warning: src-resolve: Cannot resolve the name 'soapenc:Array' to a(n) 'type definition' component.
line 0 of file:/C:/Documents%20and%20Settings/Alexander%20Trauzzi/JavaApplication2/xml-resources/web-service-references/jirasoapservice-v2/wsdl/jira.atlassian.com/rpc/soap/jirasoapservice-v2.wsdl#types?schema3
error: undefined simple or complex type 'soapenc:Array'
line 0 of file:/C:/Documents%20and%20Settings/Alexander%20Trauzzi/JavaApplication2/xml-resources/web-service-references/jirasoapservice-v2/wsdl/jira.atlassian.com/rpc/soap/jirasoapservice-v2.wsdl#types?schema3
-=-
And on and on...
What is going on? Why can't I generate my web service client? Any help is greatly appreciated!There is a bug in the processLauncher for deploytool. The workaround is to edit the processLauncher.xml located under <AS_INSTALL>/lib/processLauncher.xml and add
add xalan.jar and mail.jar to the classpath includes of the s1as-deploytool process:
includes="appserv-assemblytool.jar,activation.jar,appserv-admin.jar,appserv-cmp.jar,appserv-rt.jar,j2ee.jar,jaxrpc-impl.jar,appserv-ext.jar,deployhelp.jar,admin-cli.jar,dom.jar,xercesImpl.jar, xalan.jar, mail.jar"
The web service wizard should now work. -
Error starting web service with netbeans and tomcat
Hi i'm trying to test a web service connection with mysql i follow all the steps showed here:
http://jaxenter.com/from-database-to-restful-web-service-to-html5-in-five-minutes-48908.html
the log :
Using CATALINA_BASE: "D:\Users\investigacion01\AppData\Roaming\NetBeans\8.0\apache-tomcat-8.0.3.0_base"
Using CATALINA_HOME: "C:\Program Files\Apache Software Foundation\Apache Tomcat 8.0.3"
Using CATALINA_TMPDIR: "D:\Users\investigacion01\AppData\Roaming\NetBeans\8.0\apache-tomcat-8.0.3.0_base\temp"
Using JRE_HOME: "C:\Program Files\Java\jdk1.8.0_11"
Using CLASSPATH: "C:\Program Files\Apache Software Foundation\Apache Tomcat 8.0.3\bin\bootstrap.jar;C:\Program Files\Apache Software Foundation\Apache Tomcat 8.0.3\bin\tomcat-juli.jar"
17-Sep-2014 10:48:22.880 INFO [main] org.apache.catalina.core.AprLifecycleListener.init La biblioteca nativa de Apache Tomcat basada en ARP que permite un rendimiento óptimo en entornos de desarrollo no ha sido hallada en java.library.path: C:\Program Files\Java\jdk1.8.0_11\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;D:\Users\investigacion01\Desktop\adt-bundle-windows-x86_64-20140702\sdk\tools;D:\Users\investigacion01\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools;C:\Windows\System32;C:\Program Files (x86)\nodejs;C:\Program Files (x86)\Git\bin;D:\Users\investigacion01\AppData\Roaming\npm;D:\Kony\ImageMagick;D:\Kony\Ant\bin;C:\Program Files\apache-ant-1.9.4\bin;C:\Program Files\Java\jdk1.8.0_11\bin;D:\Users\investigacion01\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools;D:\Users\investigacion01\Desktop\adt-bundle-windows-x86_64-20140702\sdk\tools;.
17-Sep-2014 10:48:23.062 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8084"]
17-Sep-2014 10:48:23.086 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
17-Sep-2014 10:48:23.088 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-8009"]
17-Sep-2014 10:48:23.090 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
17-Sep-2014 10:48:23.090 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 523 ms
17-Sep-2014 10:48:23.113 INFO [main] org.apache.catalina.core.StandardService.startInternal Arrancando servicio Catalina
17-Sep-2014 10:48:23.113 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.3
17-Sep-2014 10:48:23.120 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Desplieque del descriptor de configuración D:\Users\investigacion01\AppData\Roaming\NetBeans\8.0\apache-tomcat-8.0.3.0_base\conf\Catalina\localhost\HelloWorldWebService.xml
17-Sep-2014 10:48:23.153 WARNING [localhost-startStop-1] org.apache.catalina.startup.SetContextPropertiesRule.begin [SetContextPropertiesRule]{Context} Setting property 'antiJARLocking' to 'true' did not find a matching property.
17-Sep-2014 10:48:23.180 SEVERE [localhost-startStop-1] org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/HelloWorldWebService]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:726)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:702)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:697)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:579)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1744)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [org.apache.catalina.webresources.StandardRoot@2b6fe9b5]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4841)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4966)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 10 more
Caused by: java.lang.IllegalArgumentException: The main resource set specified [D:\Users\investigacion01\Documents\HelloWorldWebService\build\web] is not valid
at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:627)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 13 more
17-Sep-2014 10:48:23.181 SEVERE [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Error durante el despliegue del descriptor de configuración D:\Users\investigacion01\AppData\Roaming\NetBeans\8.0\apache-tomcat-8.0.3.0_base\conf\Catalina\localhost\HelloWorldWebService.xml
java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/HelloWorldWebService]]
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:729)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:702)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:697)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:579)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1744)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
17-Sep-2014 10:48:23.182 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Desplieque del descriptor de configuración D:\Users\investigacion01\AppData\Roaming\NetBeans\8.0\apache-tomcat-8.0.3.0_base\conf\Catalina\localhost\manager.xml
17-Sep-2014 10:48:23.462 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars Al menos un JAR, que se ha explorado buscando TLDs, aún no contenía TLDs. Activar historial de depuración para este historiador para una completa lista de los JARs que fueron explorados y de los que nos se halló TLDs. Saltarse JARs no necesarios durante la exploración puede dar lugar a una mejora de tiempo significativa en el arranque y compilación de JSP .
17-Sep-2014 10:48:23.871 INFO [localhost-startStop-1] org.apache.catalina.util.SessionIdGenerator.createSecureRandom Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [347] milliseconds.
17-Sep-2014 10:48:23.899 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Desplieque del descriptor de configuración D:\Users\investigacion01\AppData\Roaming\NetBeans\8.0\apache-tomcat-8.0.3.0_base\conf\Catalina\localhost\prueba.xml
17-Sep-2014 10:48:23.902 WARNING [localhost-startStop-1] org.apache.catalina.startup.SetContextPropertiesRule.begin [SetContextPropertiesRule]{Context} Setting property 'antiJARLocking' to 'true' did not find a matching property.
17-Sep-2014 10:48:25.055 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars Al menos un JAR, que se ha explorado buscando TLDs, aún no contenía TLDs. Activar historial de depuración para este historiador para una completa lista de los JARs que fueron explorados y de los que nos se halló TLDs. Saltarse JARs no necesarios durante la exploración puede dar lugar a una mejora de tiempo significativa en el arranque y compilación de JSP .
17-Sep-2014 10:48:25.061 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDescriptor Desplieque del descriptor de configuración D:\Users\investigacion01\AppData\Roaming\NetBeans\8.0\apache-tomcat-8.0.3.0_base\conf\Catalina\localhost\ROOT.xml
17-Sep-2014 10:48:25.158 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars Al menos un JAR, que se ha explorado buscando TLDs, aún no contenía TLDs. Activar historial de depuración para este historiador para una completa lista de los JARs que fueron explorados y de los que nos se halló TLDs. Saltarse JARs no necesarios durante la exploración puede dar lugar a una mejora de tiempo significativa en el arranque y compilación de JSP .
17-Sep-2014 10:48:25.166 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8084"]
17-Sep-2014 10:48:25.185 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"]
17-Sep-2014 10:48:25.186 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 2096 ms
17-Sep-2014 10:48:27.370 INFO [http-nio-8084-exec-3] org.apache.catalina.startup.HostConfig.undeploy Repliegue (undeploy) de la aplicación web que tiene como trayectoria de contexto /prueba
17-Sep-2014 10:48:27.411 INFO [http-nio-8084-exec-1] org.apache.catalina.startup.HostConfig.deployDescriptor Desplieque del descriptor de configuración D:\Users\investigacion01\AppData\Roaming\NetBeans\8.0\apache-tomcat-8.0.3.0_base\conf\Catalina\localhost\prueba.xml
17-Sep-2014 10:48:27.414 WARNING [http-nio-8084-exec-1] org.apache.catalina.startup.SetContextPropertiesRule.begin [SetContextPropertiesRule]{Context} Setting property 'antiJARLocking' to 'true' did not find a matching property.
17-Sep-2014 10:48:28.345 INFO [http-nio-8084-exec-1] org.apache.jasper.servlet.TldScanner.scanJars Al menos un JAR, que se ha explorado buscando TLDs, aún no contenía TLDs. Activar historial de depuración para este historiador para una completa lista de los JARs que fueron explorados y de los que nos se halló TLDs. Saltarse JARs no necesarios durante la exploración puede dar lugar a una mejora de tiempo significativa en el arranque y compilación de JSP .
17-Sep-2014 10:48:28.374 INFO [http-nio-8084-exec-1] org.apache.catalina.util.LifecycleBase.start The start() method was called on component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/prueba]] after start() had already been called. The second call will be ignored.This message comes up for me when i run a project that is different than what's indicated in the error message. In fact, the project has been deleted, yet, it still is referenced during the "run" step.
-
Fault Handling a netbeans generated web service fault
Hi, we have been unsuccessful in creating a simple example where a bpel process could handle an exception thrown be a web service deployed in a EJBModule created in netbeans 5.5.
The fault handling of fault thrown be other bpel process seems to work fine, but in the case of a web service fault the process dies.
We come to realise that the soap message of a fault is different for a bpel thrown fault and a web service one. Dont know if it has something to do with the problem...
Note that there is no example of fault handling of a netbeans created webservice in a bpel process (at least we didn't find one).
Has someone been able to do this kind of fault handling?
Maybe someone could post a link to an example?
Any help is appreciatedWhat BPEL expects is a WS fault. The fault has to be defined on the WSDL operation that the BPEL invokes. If the EJB sent a soap fault, and that is the contract between the EJB and the BC, then i would say it is the resposibility of the SOAP BC to translate it into a WSDL operation defined fault and pass it on to the BPEL engine.
If the BC just hints that a fault has happened but doesn't give enough information that is necessary for the fault handling, the process will surely terminate.
If in the process you define a catchAll around the EJB invoke, you would be able to handle the fault from the BC.
I know of this one example, but not sure if they handle faults
http://blogs.sun.com/gopalan/page/gopalan?entry=ts_3175_building_a_service
The following link may be of some use.
https://blueprints.dev.java.net/bpcatalog/ee5/soa/ -
Netbeans 6.1: Can not create Web Service Client
Hi
I am trying to create a Web Service Client in Netbeans 6.1. The error message is:
Web Service Client can not be created by JAXWS:wsimport utility.
Reason: Could not initialize class com.sun.xml.ws.api.addressing.AddressingVersion
Does someone have an idea what problems is? Note that I have created web service clients many times before without problems.
Thanks in advance for any help
RalfHi
It works now... I rebooted the workstation.
Regards,
Ralf
Maybe you are looking for
-
Adding Header Elements in Jdev 11g
Hi ll, Using Jdev 11g and created a SOA application. My input xml has 5 header elements (versionNo, ServiceName etc), that I want to ultimately pass to the webservice I am invoking. Question: How do I create a XSD which will include these 5 Header el
-
Still looking for an answer to my boot up problem. Computer starts and the lights on the dbracket stop at the first green light. I get no video,keyboard or mouse and I have to use the power supply switch to turn it off. I assembled the board with
-
Reloading software - says serial number not valid?
Help needed. I have the original disc and container. Premier Elements 4. Tried the serial number -- exactly correct -- several times. I am restoring my system after a hard drive crash and this in the only remaining issue. This is what I get...
-
Problems installing Configuration Profile
We're deploying iPhones at the plant, and I'm trying to pre-configure them, using the iPhone Configuration Utility. I've created a couple of Configuration Profiles, but cant seem to get them to install. The test phone is an iPhone 4, running IOS 5.Th
-
If I try to rotate a photo in the Finder menu I get the never ending spinning color wheel?
If I try to rotate a photo in the Finder menu I get the never ending spinning color wheel?