CI based webservices

Hi ,
I have some doubts regarding the CI based webservices.Can I use the URL
http://your.peoplesoft.server/PSIGW/HttpListeningConnector?Operation=YOUR_OPERATION_NAME.v1&OperationType=Sync
for the CI Based webservice to post the data from the html page.
I am trying to append the emplid and descr field to the above URL as http://your.peoplesoft.server/PSIGW/HttpListeningConnector?Operation=YOUR_OPERATION_NAME.v1&OperationType=Sync&EMPLID=10&DESCR=TEST.
I am getting an error message like
The request string ( data ) is not properly formed. (158,16005)
Please suggest me how to call a CI based webservice from HTML or javascript.
Thanks in advance

I mean we did a workaround in current dev environment -
to rename the node to HRPRD and renaming it back to HRDEV , bouncing the web server did the trick for us.
thanks

Similar Messages

REST BASED WEBSERVICES

Hi,
We Have a Legacy System based on REST BASED WEBSERVICES, that legacy system can understand only HTTP format(it does n't support SOAP ) our scenario is HTTP TO RFC SYNCHRONOUS.
And we have to connect PI with REST BASED WEBSERVICES ?
1---->How can we connect PI with REST BASED WEBSERVICES ?
2---->and how to test those REST BASED WEBSERVICES ?any tool for that?
Thanks,
Nagaraju.

Hi Nagaraju,
you can sent message from PI via [http receiver adapter|http://help.sap.com/saphelp_nw2004s/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm].
For message from legacy to PI use a simple address, what is explained in [SAP help http sender adapter|http://help.sap.com/saphelp_nw2004s/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm]
You can test http messages with Microsoft's tool [Wfetch|http://www.microsoft.com/download/en/details.aspx?id=21625] (in the net are hundreds of free ware http test tool available).
Regards,
Udo

SOURCING10: Passing parameters to a Query Based webservice using JAVA

Hi Experts,
I have been working on consuming a Query based webservice published in Souricng10 in a simple JAVA class. The query has a filter parameter which is not mandatory. I am able to consume the webservice using the GET method and display the content of the webservice. But when i try to POST a value to the filter parameter of the query i am getting the following error:
java.io.IOException : Server returned HTTP response code: 415 for URL: http://sapcild9.web.bc:55000/sourcing/ngservices/rest/query/Z_TEST_WS_QUERY/execute/
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
Following is the code which i have used:
   URL url = new URL("http://sapcild9.web.bc:55000/sourcing/ngservices/rest/query/Z_TEST_WS_QUERY/execute/");
   HttpURLConnection connection = (HttpURLConnection)url.openConnection();
   connection.setRequestProperty("Authorization", "Basic " + authStringEnc);
   connection.setRequestProperty("Content-Type","application/x-www-form-urlencoded; charset=UTF-8");
   connection.setRequestProperty("Content-Length", "" +Integer.toString(urlParameters.getBytes().length));
   connection.setRequestProperty("Content-Language", "en-US");
   connection.setUseCaches (false);
   connection.setDoInput(true);
   connection.setDoOutput(true);
   connection.setAllowUserInteraction(true);
   connection.setInstanceFollowRedirects(false);
   connection.setRequestMethod("POST");
   connection.connect();
   //Send request
   OutputStream out = connection.getOutputStream();
   OutputStreamWriter wr= new OutputStreamWriter(out, "UTF-8");
   wr.write("EXTERNAL_ID");
   wr.write("=");
   wr.write(URLEncoder.encode("temp","UTF-8"));
   wr.close();
   out.close();
   is = connection.getInputStream();
   isr =new InputStreamReader(is);
   BufferedReader bufferReader = new BufferedReader(isr);
   String str; StringBuffer stringBuffer = new StringBuffer();
   while ((str = bufferReader.readLine()) != null) {
   stringBuffer.append(str);
   stringBuffer.append("\n");
   System.out.println(stringBuffer.toString());
   connection.disconnect();
   is.close();
Please Advise how to proceed on this isssue?
Thanks in advance.
Srikanth Emani

Hi Gael,
your URL is made up of :
[ProcedureName]?[parameter1]=[value1]&[parameter2]=[value2]
creating URLs like this can have problems especially with spaces and punctuation.
the answer is a FORM
the following will create a hidden form :
FORM ACTION="[ProcedureName]" METHOD="POST" name="F1"
INPUT type="HIDDEN" name="[parameter1]" value="[value1]"
INPUT type="HIDDEN" name="[parameter2]" value="[value2]"
/FORM
you can set the values in the form using:
document.F1.[parameter1].value="abc123%%&&$$!";
document.F1.submit();
will submit the form and the PL/SQL procedure should receive the text as it was contained in the form.
the only characters that can now cause problems are :
" as it delimits the field.
' as it may cause problems in PL/SQL.
\ as it is a special character.
Regards Michael

SOAP Based Webservices in Apex

Can you please let me if we can create a SOAP Based Webservices in Apex. Apex will be the provider of the webservice and my other 3rd party application will be consumer.

Thanks for the reply.
Now I am slightly understanding about web services. For example, If I place an order for an digital camera from a shopping site, can I route the order information from shopping site to APEX and from APEX can I process it further by integrating with paypal for online payments and get acknowledge from paypal that payment has been made and provide an acknowledgment to shopping site from APEX that order has been shipped to your shipping address. Is this possible? Please let me know regarding this..
Thanks and Regards,
Mahesh

Consume a third party REST Based Webservice from PeopleSoft

We are in tools 8.49.33
Using 'Consume Web Service' component we can only consume a WSDL based webservice I guess. But we have a requirement to consume to a third party webservice, for which we just have to invoke a URL with query string via HTTP GET and receive an XML response. Has anyone done this before?

Three things to check:
#1: Check your errorLog.html file in the PSIGW web app of your PeopleSoft server
#2: Does your app server have to go through a proxy to connect to the internet? If so, did you configure integrationGateway.properties to use a proxy server? You can test this by trying to use ConnectorRequestURL for a plain old HTTP web site. If you get the same error, then it is likely a proxy issue.
#3: If #2 passed, then it might have to do with certificates and you will need to review PeopleBooks for importing certificates for integration broker. I haven't had to do this before, but am pointing it out in case.

How to inject EntityManager in non-EJB based WebService?

Hi,
I want to know how we can inject EntityManager in non-EJB based WebService?
Regards,
imran

I think the way to go would be to actually do use an EJB for the persistence stuff and use that EJB in your webservice. Use the right tool for the job and all that.

WSDL Parser [Is anyone else testing WCF-based webservices?]

I'm encountering the following message when attempting to force the use of the .NET parser when interrogating the WSDL of a new webservice:
Parsing specified wsdl...
Connecting to https://BLAH-BLAH/MobileTerminated.svc?wsdl
Validating https://BLAH-BLAH/MobileTerminated.svc?wsdl
.NET Parser could not parse https://BLAH-BLAH/MobileTerminated.svc?wsdl
Warning:Selected .NET Parser is invalid.
Must installed the .net sdk Framework.
Failed to parse https://BLAH-BLAH/MobileTerminated.svc?wsdl
Am I correct in interpreting this as "you need the .NET SDK installed in order to use the .NET Parser within OATS"?
I already have .NET framework 3.5(SP1) but not the SDK.
[UPDATE] It is probably significant that the webservice I need to test is WCF-based.
Edited by: IHodgetts on May 21, 2010 5:45 PM
Edited by: IHodgetts on Jun 21, 2010 12:07 PM

I know I'm answering my own post here, but a lot of work has gone into this and someone else may as well benefit from my findings...
It would appear that OATSv9.10 does NOT support WCF-based webservices. The problem is apparently down to OpenScript not supporting WS-Addressing (part of Windows Communication Foundation) and this isn't currently scheduled for inclusion in v9.20 (much to my disappointment).
However, I have in the meantime found a workaround. Basically IGNORE what OpenScript populates the request with!
1) Use the OpenScript parser (the .NET parser will not work) to parse the WSDL.
2) Add the method(s) you require to the script.
3) The script will at this stage have two problems but can be used as a starting point.
Problem #1 - The content-type will need to be manually changed from "text/xml;charset=UTF-8" to "application/soap+xml; charset=utf-8". Edit this by right-clicking on the request and selecting "Headers" then "Content-Type".
Problem #2 - The contents of the request will not include the WS-Addressing information. One workaround is to obtain a working packet to replace this e.g. from a test harness for your WCF-webservice. Edit this by right-clicking on the request and selecting "Post Data". Replace the WHOLE string with a valid packet from your test harness.
Hopefully this will assist anyone else trying to get this working :-)

How to develop Asynchronous Document Based WebServices?

Hi gurus,
The scenario is, We are developing an architecture where Asynchronous Document Based WebServices are desired.
As per my knowledge, This architecture includes some
work at JMS side.
Meaning,
Client -
> Calling [WebService] -
> Deletgate --
>JMQ (Java Message Queue)
Would appreciate ur thoughts here...
Regards,
Arvind Kugasia [[email protected]]

Hi Arvind,
this "pattern" - sending JMS message and performing some long asynchronous tasks in MDB is a standard J2EE way.
That should be supported by any j2ee server that at least covers J2EE 1.3 (where MDB-s are introduced). That includes the SAP Web AS as well and its JSM and EJB implementation as well.
The message can be sent from a servlet, web service, etc.
In fact the classic petstore application released from sun as a model for developing J2EE applications uses MDB-s for that purposes :
http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/sample-app/sample-app1.3.1.html
Once you buy the parrot from the petstore, you will see the response page while the MDB will perform asynchonously the sending of the mail, charging of the account, etc.
It doesn't matter if the front end is a web service or a HTTP UI.
In addition you can google for any J2EE tutorial and MDB explanation.
However please note that I am speaking how your application will gather the parameters from the web service call, put them in a JMS message and send the message via several lines of java code.
Perhaps some other frameworks (Apache-Axis, etc.) are doing this automatically for you or are generating the code that sends the message via some wizard.
That up to my knowledge is not supported for SAP WebAS, but that is only a 10 lines of code inside the web service body, that can be easily created.
HTH
Peter

Has anyone deployed JAX-RPC based webservices on WebLogic8.1

Hi all...
I 've been trying to deploy the jaxrpc based webservices on weblogic8.1/6.1....but its not working...it works fine on tomcat server...
so if anyone has deployed and tested the webservices on weblogic successfully...pls help..
thanks
khajaM

Jwenting,
Thanks for your reply.Could you please tell me what should I need to perform to overcome this problem.I have pasted below my client program for your reference.
import org.apache.axiom.om.OMAbstractFactory;
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.OMFactory;
import org.apache.axiom.om.OMNamespace;
import org.apache.axis2.Constants;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.client.Options;
import org.apache.axis2.client.ServiceClient;
import org.apache.axis2.context.MessageContext;
public class AxisBasedClientForJWS {
private static EndpointReference targetEPR =
new EndpointReference("http://localhost:7001/final/IntegWebservice");
private static OMElement getResponse(String symbol) {
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs = fac.createOMNamespace("http://IntegratorWebservices.org/wsdl","");//"http://IntegratorWebservices.org/wsdl", "tns");
OMElement method = fac.createOMElement("add", omNs);
OMElement value = fac.createOMElement("symbol", omNs);
value.addChild(fac.createOMText(value, symbol));
method.addChild(value);
return method;
public static void main(String[] args) {
try {
OMElement getResponse = getResponse("WSO");
Options options = new Options();
options.setTo(targetEPR);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
ServiceClient sender = new ServiceClient();
sender.setOptions(options);
OMElement result1 = sender.sendReceive(getResponse);
String response1 = result1.getFirstElement().getText();
System.err.println("Current price of WSO: " + response1);
} catch (Exception e) {
e.printStackTrace();
System.out.println(e);
With regards
Ramesh.G

Securing REST based Webservices using OSB

Can anyone please lead me to any pointers on securing the REST based webservices.
Thanks,
KC

REST is more or less, a pure HTTP service so it is as secure as that. From my perspective transport security (basic authentication, SSL) is the basic security requirement for a REST based web-service. As far as message security is concerned, you may use custom HTTP headers to pass the tokens/digest but again it requires transmission over SSL to become an effective solution.
If you really have tight requirement from message security perspective, then I would suggest going to SOAP rather than using REST.
Regards,
Anuj

Rest based webservices from plsql procedures/packages

Guyz.
Please let me know How to create Rest based webservices in jdeveloper tool from plsql procedures/packages.
Im very much in need
Thanks,

Hi User ,
Welcome to OTN !!
You can refer to these links and figure out -
http://docs.oracle.com/cd/E16162_01/user.1112/e17455/dev_web_services.htm#CHDJIFAE
http://theblasfrompas.blogspot.com/2011/03/developing-restful-web-services-from.html
Also for calling pl/sql packages from Java , use soemthing like this - http://www.coderanch.com/t/302171/JDBC/databases/execute-PL-SQL-program-Java

Developing SOAP based Webservice using Axis 2 Eclipse plugin

Hi,
I want to develop a SOAP based Webservice which connects to the PostgreSQL DB , by fetching the data for the employeeId entered and display the results in the browser. I'm using using JDK 1.6, Tomcat 6.0, Axis 2.0 , with Axis 2 Eclipse Plugin. Please send me a sample code of how to build it, i am able find some examples on the internet, but none of them are related to connecting to the DB and fetching the data. It will be great if you guys can provide the sample application which does have the same functionality as mine. Please do respond as this is urgent. Thanks in advance..
Thanks,
Rithu

Thanks Adhir Mehtaji, This is what i have come up with, developing a webservices based on SAAJ and deploying that in Tomcat server, here is the Webservice and the other related files:-
public class EmployeeService {
     * This method returns the Employee Name
     * @param empId String
     public void getEmployeeName(SOAPEnvelope req, SOAPEnvelope resp) throws javax.xml.soap.SOAPException {
          System.out.println("Inside the getEmployeeName in Employee Service");
          IEmployeeDAO employeeDAO= null;
          employeeDAO = new EmployeeDAOImpl();
          SOAPBody body = resp.getBody();
          String empId = null;
          NodeList empIdNodeList = req.getBody().getElementsByTagName("empId");
          for( int i=0; i < empIdNodeList.getLength(); i++ ) {
               Element empIdElementElement = (Element) empIdNodeList.item(i);
               Node empIdNode = empIdElementElement.getChildNodes().item(0);
               empId = empIdNode.getNodeValue();
               System.out.println("the empId in the employee service is:::"+empId);
          addNode(body,"empName",employeeDAO.getEmployeeName(empId));
          //addNode(body,"segmentName1",custSegmentDAO.getSegmentName(ZipCode));
     private static void addNode(SOAPBody body,String nodeName,String nodeValue) throws SOAPException{
          body.addChildElement(nodeName).addTextNode(nodeValue);
     This Service is exposed as a Webservice which connects to the DAO and get the response for the EmpId.
     This is the client file:-
     public class GetEmployeeNameClient {
          public static void main(String[] args) throws Exception {
               // Invoking the Webservice endpoint which is hosted (deployed) in Tomcat by passing the SOAP Message request
               // Get the SOAP Message response , which contains the employee name for the empId 100
               // Parse the SOAP Message response to get the employee name (response from the WS)
               String[] nodeNames = { "empId" };
               String[] nodeValues = { "100" };
               SOAPMessage message = GetEmployeeNameClient.getMessageFactory(
                         "getEmployeeName", nodeNames, nodeValues);
               SOAPConnection conn = SOAPConnectionFactory.newInstance()
                         .createConnection();
               SOAPMessage response = conn.call(message,
                         "http://localhost:8080/axis/services/EmployeeService");
               // If the response is not null then everything is fine with the WS.
               System.out.println("the response is what???"+response);
               System.out.println("\n Soap response:\n");
               System.out.println("\nXML response\n");
               // Create transformer
               TransformerFactory tff = TransformerFactory.newInstance();
               Transformer tf = tff.newTransformer();
               // Get reply content
               Source sc = response.getSOAPPart().getContent();
               // Set output transformation
               StreamResult result = new StreamResult(System.out);
               tf.transform(sc, result);
               System.out.println();
               // For these to work we need to connect to the DB - jdbc:oracle:thin:@ora-b2cd:6473:b2cd to get the segment name
               SOAPBody soapBody = response.getSOAPBody();
               System.out.println("the soapBody is what???"+soapBody);
               NodeList empNameNodeList = soapBody.getElementsByTagName("empName");
               System.out.println("the empNameNodeList.getLength is::"+empNameNodeList.getLength());
               for (int i = 0; i < empNameNodeList.getLength(); i++) {
                    System.out.println("inside the loop");
                    Element empNameElement = (Element) empNameNodeList.item(i);
                    System.out.println("the empNameElement is what???"+empNameElement);
                    Node empNameNode = empNameElement.getChildNodes().item(0);
                    System.out.println("the empNameNode is what???"+empNameNode);
                    System.out.println("Employee Name For empId is ...... "
                              + empNameNode.getNodeValue());
          // Construct the SOAP Message request by passing the empId 100(should come from UI)
          private static SOAPMessage getMessageFactory(String methodName,
                    String[] nodeNames, String[] nodeValues) throws SOAPException {
               SOAPMessage message = null;
               try {
                    System.out.println("Inside the getMessageFactory");
                    MessageFactory messageFactory = MessageFactory.newInstance();
                    message = messageFactory.createMessage();
                    SOAPPart soapPart = message.getSOAPPart();
                    SOAPEnvelope envelope = soapPart.getEnvelope();
                    SOAPBody body = envelope.getBody();
                    SOAPElement bodyElement = body.addChildElement(envelope
                              .createName(methodName));
                    for (int index = 0; index < nodeNames.length; index++) {
                         bodyElement.addChildElement(nodeNames[index]).addTextNode(
                                   nodeValues[index]);
                    message.saveChanges();
                    // View input
                    System.out.println("\n Soap request:\n");
                    message.writeTo(System.out);
                    System.out.println();
               } catch (Exception e) {
                    e.printStackTrace();
               return message;
     This client will send a SOAPMessage with EmpId (100) as a request and get the response from the Webservice as SOAPMessage , which
     contains the empname for the respective empid which is passed.
I tested this service in the browser, it is up and running through the URL : http://localhost:8080/axis/services
But when i try to access the webservice to get the response from my client program, i am getting the following SOAP Fault string:-
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body><soapenv:Fault>
<faultcode>
soapenv:Server.userException
</faultcode>
<faultstring>
org.xml.sax.SAXNotRecognizedException: Feature: http://xml.org/sax/properties/lexical-handler
</faultstring>
<detail>
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">
user-15bbc0db6e
</ns1:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
My client path contains :-
axis.jar;
jaxrpc.jar;
saaj.jar;
commons-logging.jar;
commons-discovery.jar;
wsdlj4.jar;
axis-ant.jar;
log4j-1.2.4.jar
xerces.jar
activation.jar
mail.jar
Similary the in the d:/tomcat/webapps/axis/WEB-INF/lib,contains the same as that in client path.
I am using Tomcat 6.0 , JDK 1.6, I have googled and found that the expection is due to "Xerces.jar" not in Tomcat/webapps/axis/WEB-INF/lib.
I have copied xerces.jar in the said path, still the error persists. Please do provide a solution to this. Where i have gone wrong.
I have one more query, If i have to rest a "list" as a response from the server (webservice), how i can add the list into the SOAPMessage? Whether i need to parse it and add the values one by one in the SOAPMessage? like
<empname> xxxx</empname> <empage>25</empage>
<empname> yyyy</empname> <empage>26</empage>
Please answer these queries.
Thanks,
Rithu

Document based webservice failed

Hello:
I am trying to invoke a document style webservice
I am getting this error any idea why I am getting this.
I am returning a Document object which I created using DOM
Failed to invoke service:
java.util.EmptyStackException at java.util.Stack.peek(Stack.java:79) at
java.util.Stack.pop(Stack.java:61) at
weblogic.xml.babel.stream.DOMNodeWriter.write(DOMNodeWriter.java:125) at
weblogic.xml.babel.stream.DOMNodeWriter.write
regards
Boney Jose

Hello,
This error is unfamiliar and there is not enough information in your
post to ascertain the cause. Have you tried the examples of document
based webservices that Manoj has [1]? I think they would be helpful in
your efforts.
Regards,
Bruce
[1]
http://manojc.com/?sample13
http://manojc.com/?sample14
http://manojc.com/?sample31
http://manojc.com/?sample43
Boney Jose wrote:
>
Hello:
I am trying to invoke a document style webservice
I am getting this error any idea why I am getting this.
I am returning a Document object which I created using DOM
Failed to invoke service:
java.util.EmptyStackException at java.util.Stack.peek(Stack.java:79) at
java.util.Stack.pop(Stack.java:61) at
weblogic.xml.babel.stream.DOMNodeWriter.write(DOMNodeWriter.java:125) at
weblogic.xml.babel.stream.DOMNodeWriter.write
regards
Boney Jose

Message based webservice

Hi all,
Is there any way to write message based webservice in weblogic like in AXIS(not
JMS based)

Hello,
JAXM is not part of J2EE and not supported.
SAAJ [1] provides much of the same functionality (javax.xml.soap
package) and is supported by WLS.
Regards,
Bruce
[1]
http://java.sun.com/xml/saaj/
santosh wrote:
>
Hi all,
Is there any way to write message based webservice in weblogic like in AXIS(not
JMS based)

Possible to create a JAX-WS, session-bean-based webservice for WebLogic 10?

All,
sorry - but I'm going a bit crazy here. I have been unable to figure out the secret hand-shakes for developing a session-bean-based web service that will run properly under Weblogic 10.0. There are examples out there on how to create webservices that exists within a war file - but none that I can find that reside within a session bean (an ear file).
I can't even figure out how to do with this Bea Workshop for WebLogic Platform 10.0! Is this possible? I can't find any examples anywhere on how to do this. I must be missing something...
Does WebLogic 10.0 support web services within session beans? I've figured out how to do this with JBoss, Sun App Server, and Glassfish - but no luck so far with WebLogic.
If anyone can please point me in the proper direction it would be very appreciated. My company likes WebLogic, but we have to be able to do this in order to continue using it.
Thanks,
-john

Yeah - I've tried that. Everything builds fine - but when I deploy to WebLogic 10, I get the stack below. It looks like it is looking for the class examples.webservices.jaxws.jaxws.SayHello - but there isn't such a class in the example...
Any thoughts? I'm completely stuck!
<Apr 16, 2007 4:15:45 PM PDT> <Error> <HTTP> <BEA-101216> <Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
Truncated. see log file for complete stacktrace
>
<Apr 16, 2007 4:15:45 PM PDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1176765341457' for task '0'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
[HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
[HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:440)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
Truncated. see log file for complete stacktrace
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
Truncated. see log file for complete stacktrace
>
<Apr 16, 2007 4:15:46 PM PDT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application '_appsdir_WL6_ear'.>
<Apr 16, 2007 4:15:46 PM PDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application '_appsdir_WL6_ear'.>
<Apr 16, 2007 4:15:46 PM PDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
[HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:440)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
Truncated. see log file for complete stacktrace
class: examples.webservices.jaxws.jaxws.SayHello could not be found
at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
Truncated. see log file for complete stacktrace
>

CI based webservices

Similar Messages

Maybe you are looking for