Code webservices in WLS 6.1 sp2 using apache soap servlet

Please let me know the steps necessary to use the soap servlet from apache while
coding the webservices.
Thanks
Vaneet

Similar Messages

WLS 6.1 SP2 and Apache 1.3.26 Windows NT/2000

Hi,
Is there an Apache plugin available for WLS 6.1 (SP2) and Apache 1.3.26 running
on Windows NT/2000?
thanks

I've solved my own problem. I learned that there was a sp4 (let alone a
sp3) for WLS. Installed that and the problem went away. Sorry for the
noise.
-Phil
Philip Bower <[email protected]> wrote in
news:[email protected]:
When I try to deploy the struts-example.war or if I add the struts.jar
to any other web app I've created, I get this error when I start WLS
and it tries to deploy that war.
java.lang.StringIndexOutOfBoundsException
at weblogic.servlet.internal.WebAppHelper.resolveManifestName
(WebAppHelper.java:469)
I'm using version 1.1b3 of struts. I'm having no problems with
version 1.0.2 of struts.
I'm guessing its complaining about the manifest file in struts.jar,
but I don't understand why.
Here's my version info and the stack trace (my web app is called
findme in this example). Thanks in advance.
-Phil
Server BuildWebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
All Server Product VersionsWebLogic Server 6.1 SP2 12/18/2001
11:13:46 #154529 WebLogic XML Module 6.1 SP2 12/18/2001 11:28:02
#154529
<Feb 11, 2003 7:45:25 AM EST> <Error> <J2EE> <Error deploying
application findme: Could not load findme>
<Feb 11, 2003 7:45:25 AM EST> <Error> <Management> <ApplicationManager
starting Config caught throwable
java.lang.reflect.UndeclaredThrowableException:
java.lang.StringIndexOutOfBoundsException: String index out of range:
-1
at java.lang.String.substring(String.java:1525)
at
weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper
.jav a:469)
at
weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.j
ava: 234)
at
weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebApp
Serv letContext.java:3407)
at
weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServlet
Cont ext.java:3376)
at
weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContex
t.ja va:862)

PLEASE HELP! Using Apache SOAP with WL61

Hi,
I am trying to run the Apache soap within the WL61.
I have the Apache soap servlet deployed under WL61.
I am trying to use org.apache.soap.server.ServiceManagerClient
to deploy the sample AddressBook service. I get the following error: "Unable to
resolve namespace URI for 'xsd'".
Now, the Apache SOAP faq says, I need to use the 1.3.0 xeces.jar
on both server and client to solve this problem.
However, WL61 server wont come up with the 1.3.0 xerces.jar file
I am in a catch 22 situation, please help.
thanks

I had exactly this problem and by following the advice below I got it to work using
crimson.jar from apache.
Step 1: put crimson.jar frst in classpath
Step 2: put the following in config.xml
<XMLRegistry DocumentBuilderFactory="org.apache.crimson.jaxp.DocumentBuilderFactoryImpl"
Name="Xerces JAXP" SAXParserFactory="org.apache.crimson.jaxp.SAXParserFactoryImpl"
/>
Step 3: updated Server entry in config.xml to point to "Xerces JAXP" as explained
below.
I know this does not add a lot to the idea below but it is an alternative.
Thanks,
George
Manoj Cheenath <[email protected]> wrote:
>
This is something i found in apache soap mailing list:
------- Original Message --------That fixed it! Thanks, Stefan!
-----Original Message-----
From: Stefan Dube [mailto:[email protected]]
Sent: Wednesday, June 13, 2001 4:15 AM
To: [email protected]
Subject: RE: compatibility with weblogic 6.1 beta
Hi!
I believe the problem is that SOAP 2.2 uses JAXP and WL uses their
bundled
xerces as JAXP parser.
To override this you have to modify the config.xml like this: (or
use the web
console)
Add following element as child of the <Domain> element:
<XMLRegistry
DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"
Name="Xerces JAXP"
SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl"
/>
and modify the <Server> element like this:
<Server
InstrumentStackTraceEnabled="true"
ListenPort="80"
LogRemoteExceptionsEnabled="true"
Name="myServer"
NativeIOEnabled="true"
XMLRegistry="Xerces JAXP" <-- only this line is important
>
Hope that helps,
-sd
-----Original Message-----
From: Erik Onnen [mailto:[email protected]]
Sent: Wednesday, June 13, 2001 1:33 AM
To: '[email protected] '
Subject: RE: compatibility with weblogic 6.1 beta
The "unable to resolve namespace" problem is because BEA in
their infinite
wisdom chose to mesh Xerces into their own libraries.
Unfortunately they
used an old version and because it is so embedded, you can't
just replace a
JAR. I was able to get 2.1 working on 6.0 sp1 by moving
Xerces to the front
of the classpath in the startup script. Ed, when WL won't
start, what is the
error you get? I haven't heard of that happening before.
Steve, when you say
Xerces is in your classpath, is it at the front, before weblogic.jar?
-----Original Message-----
From: Steve Livingston
To: [email protected]
Sent: 6/12/01 6:46 PM
Subject: RE: compatibility with weblogic 6.1 beta
1) I get the same error (with NT, soap-2.2 and wl-6.1beta) andhave
found no solution:
E:\apache\soap-2_2\samples\addressbook>java
org.apache.soap.server.ServiceManagerClient
http://slivings:7001/soap/servlet/rpcrouter list
Deployed Services:
E:\apache\soap-2_2\samples\addressbook>java
org.apache.soap.server.ServiceManagerClient
http://slivings:7001/soap/servlet/rpcrouter deploy dd.xml
Ouch, the call failed:
Fault Code = SOAP-ENV:Client
Fault String = Unable to resolve namespace URI for 'ns2'.
2) My wl-6.1b will start with xerces in classpath, but same error
occurs.
Can anyone help?
Steve
-----Original Message-----
From: Ed Keen [mailto:[email protected]]
Sent: Monday, June 11, 2001 6:36 PM
To: '[email protected]'
Subject: compatibility with weblogic 6.1 beta
Has anyone gotten Apache soap version 2.2 to work with Weblogic6.1
beta?
There seems to be a xerces incompatibility. The weblogic.jarfile
contains
the xerces library. If you put xerces.jar first in the classpath,
weblogic
won't even start. However, if you put weblogic.jar first in the
classpath,
you get this error when attempting to deploy services using the
ServiceManagerClient: "Unable to resolve namespace URI for 'ns2.'"
This obviously seems to be a xerces parsing issue. Does
anyone know of
a
workaround for this?
Thanks,
EdSanjeev Hegde wrote:
Hi,
I am trying to run the Apache soap within the WL61.
I have the Apache soap servlet deployed under WL61.
I am trying to use org.apache.soap.server.ServiceManagerClient
to deploy the sample AddressBook service. I get the following error:"Unable to
resolve namespace URI for 'xsd'".
Now, the Apache SOAP faq says, I need to use the 1.3.0 xeces.jar
on both server and client to solve this problem.
However, WL61 server wont come up with the 1.3.0 xerces.jar file
I am in a catch 22 situation, please help.
thanks

Invocation of SOAP Sender Adapter using Apache SOAP

Hi,
I'm trying to invoke the XI SOAP Sender Adapter using the Apache SOAP API. It seems that my message header is missing a few parameters (see exception below). Does anybody know which to set?
Regards,
Heiko
==========
Exception:
<?xml version='1.0'?>

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Body>
    <SOAP:Fault>
      <faultcode>SOAP:Server</faultcode>
      <faultstring>Server Error</faultstring>
      <detail>
        <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
          <context>XIAdapter</context>
          <code>Exception</code>
          <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:502)
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
     at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)
     at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
     at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:162)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:507)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:392)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged1(Native Method)
     at java.security.AccessController.doPrivileged(AccessController.java:321)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: java.lang.Exception: Bubble configuration error: parameter 'XI.InterfaceNamespace' is missing
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.getParaRequired(XISOAPAdapterBean.java:895)
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.createDefaultMessageHeader(XISOAPAdapterBean.java:942)
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.setup(XISOAPAdapterBean.java:214)
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:496)
     ... 22 more
          ]]></text>
        </s:SystemError>
      </detail>
    </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Hi Heiko,
You are missing the Namespace Parameter in the sender soap adapter configuration in XI3.0
Thanks
Prasad

Linkage Error when using Apache SOAP 2.2 with Weblogic 6.1

Has anyone seen this error before? Apparently I've got some incompatible versions of xerces being loaded. I tried putting different versions of xerces.jar in the front of my classpath, and creating an XML Registry to point to org.apache.xerces.jaxp..., but I always get the same error message.
D:\soap>java -classpath "/soap-2_2/lib/soap.jar;activation.jar;mail.jar;xerces.jar;." org.apache.soap.server.Servic
eManagerClient http://localhost:8001/App/servlet/rpcrouter list
Ouch, the call failed:
Fault Code = SOAP-ENV:Server.Exception:
Fault String = loader constraints violated when linking org/xml/sax/InputSource class

Has anyone seen this error before? Apparently I've got some incompatible versions of xerces being loaded. I tried putting different versions of xerces.jar in the front of my classpath, and creating an XML Registry to point to org.apache.xerces.jaxp..., but I always get the same error message.
D:\soap>java -classpath "/soap-2_2/lib/soap.jar;activation.jar;mail.jar;xerces.jar;." org.apache.soap.server.Servic
eManagerClient http://localhost:8001/App/servlet/rpcrouter list
Ouch, the call failed:
Fault Code = SOAP-ENV:Server.Exception:
Fault String = loader constraints violated when linking org/xml/sax/InputSource class

Ignoring Http basic authentication header in wls 7.0.sp2 web service servlet (weblogic.webservice.server.servlet.WebServiceServlet)

Hi!
We need to implement authentication using our own methods, and the authentication
information is provided to the web service implementation in a basic authentication
header. The problem is, that the servlet
weblogic.webservice.server.servlet.WebServiceServlet, which handles web services
in
wls 7.0.sp2, always attempts to perform authentication, if the header is present.
Is there any way to circumvent this, because we want to implement authentication
on our own?
I already know two workarounds:
The best would of course be to implement a custom security realm for our own
authentication system. This is not an option, implementing an own security
realm is overkill for this specific web service.
The other way would be to route the requests by way of a custom servlet, which
would
remove the basic authentication header, and put the authentication info in custom
headers, such as x-auth: <user:password>, or smthng similar, and after successful
authentication, make a call to bea's servlet weblogic.webservice.server.servlet.WebServiceServlet.
But still, I'd like to know if there is any way to tell bea's servlet to ignore
the basic
authentication header?
Oh yeah, by the way, this is URGENT, as always. (really!! ;)
Toni Nykanen

Currently there is no option to turn off security check.
I think you can use a servlet filter mapped to the URL
of your service, instead of a proxy servlet?
Regards,
-manoj
http://manojc.com
"Toni Nykanen" <[email protected]> wrote in message
news:3ef1577b$[email protected]..
>
Hi!
We need to implement authentication using our own methods, and theauthentication
information is provided to the web service implementation in a basicauthentication
header. The problem is, that the servlet
weblogic.webservice.server.servlet.WebServiceServlet, which handles webservices
in
wls 7.0.sp2, always attempts to perform authentication, if the header ispresent.
Is there any way to circumvent this, because we want to implementauthentication
on our own?
I already know two workarounds:
The best would of course be to implement a custom security realm for ourown
authentication system. This is not an option, implementing an own security
realm is overkill for this specific web service.
The other way would be to route the requests by way of a custom servlet,which
would
remove the basic authentication header, and put the authentication info incustom
headers, such as x-auth: <user:password>, or smthng similar, and aftersuccessful
authentication, make a call to bea's servletweblogic.webservice.server.servlet.WebServiceServlet.
>
But still, I'd like to know if there is any way to tell bea's servlet toignore
the basic
authentication header?
Oh yeah, by the way, this is URGENT, as always. (really!! ;)
Toni Nykanen

LDAPRealm Failover in WLS 6.0 SP2

We have WLS 6.0 SP2 using a Netware LDAP server to authenticate. Given recent problems with the LDAP server, we have to build in failover capability. As far as I know 6.0 does not support failover for LDAP. Is there any way around this apart from building another jar file? We want to avoid having to manually restart the weblogic server each time with different config setting.
thanks
Bavini

We have WLS 6.0 SP2 using a Netware LDAP server to authenticate. Given recent problems with the LDAP server, we have to build in failover capability. As far as I know 6.0 does not support failover for LDAP. Is there any way around this apart from building another jar file? We want to avoid having to manually restart the weblogic server each time with different config setting.
thanks
Bavini

"invalid request" when calling Apache Soap 2.2 webservice using 8.1.1

I have tried setting soap-style to RPC as advised in the documentation but keep
getting this same error. Server is Apache Soap 2.2. Another test client using
Apache Soap 2.3.1 got the same error. I am trying to call a webservice in a WLI
process flow. I have generated the web service control from the wsdl. Error follows:
<01-Oct-2003 11:04:04 o'clock EST> <Warning> <WLW> <000000> <Id=bank_so_11; Meth
od=processes.bank_so_1.GetNextAccountNumber(); Failure=com.bea.control.ServiceCo
ntrolException: SOAP-ENV:Clientinvalid request>
<01-Oct-2003 11:04:04 o'clock EST> <Warning> <WLW> <000000> <Id=top-level; Metho
d=processes.TestWSBank_wf.$__clientRequest(); Failure=com.bea.wli.bpm.runtime.Un
handledProcessException: Unhandled process exception [ServiceException]>
<01-Oct-2003 11:04:04 o'clock EST> <Error> <WLW> <000000> <Failure=com.bea.wli.b
pm.runtime.UnhandledProcessException: Unhandled process exception [ServiceExcept
ion]>

Hi Jerry,
There is not much to go on here to help solve your problem. Can you
successfully invoke the external service from Workshop's Test View? If
this works OK you might ask your question to the integration newsgroup
and see if they have some insight:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.integration
Hope this helps,
Bruce
Jerry Shea wrote:
>
I have tried setting soap-style to RPC as advised in the documentation but keep
getting this same error. Server is Apache Soap 2.2. Another test client using
Apache Soap 2.3.1 got the same error. I am trying to call a webservice in a WLI
process flow. I have generated the web service control from the wsdl. Error follows:
<01-Oct-2003 11:04:04 o'clock EST> <Warning> <WLW> <000000> <Id=bank_so_11; Meth
od=processes.bank_so_1.GetNextAccountNumber(); Failure=com.bea.control.ServiceCo
ntrolException: SOAP-ENV:Clientinvalid request>
<01-Oct-2003 11:04:04 o'clock EST> <Warning> <WLW> <000000> <Id=top-level; Metho
d=processes.TestWSBank_wf.$__clientRequest(); Failure=com.bea.wli.bpm.runtime.Un
handledProcessException: Unhandled process exception [ServiceException]>
<01-Oct-2003 11:04:04 o'clock EST> <Error> <WLW> <000000> <Failure=com.bea.wli.b
pm.runtime.UnhandledProcessException: Unhandled process exception [ServiceExcept
ion]>

WLS 7.0 sp2 - Servlet Problems with SOAP messages

          I'm using Weblogic 7.0 SP2 and trying to create a Servlet to receive SOAP wrapped
          XML messages. I'm getting the following error. Is this a problem with WLS7.0sp2's
          support of JAXM? The System.out.println's indicate I have successfully received
          the incoming SOAP request and then successfully formatted the SOAP response, but
          upon returning saving the response it appears to blow up. Does anyone have any
          suggestions?
          I need to do the following in a servlet:
          - receive an incoming SOAP request with an embedded XML message
          - perform some processing
          - return a SOAP response with an embedded XML message
          Should I be using JAXM? Or can I do this same task easily with JAX-RPC?
          <Feb 24, 2004 4:10:42 PM AST> <Error> <HTTP> <101017> <[ServletContext(id=260434
          7,name=isd.war,context-path=)] Root cause of ServletException
          java.lang.Error: NYI
          at weblogic.webservice.core.soap.SOAPMessageImpl.saveRequired(SOAPMessag
          eImpl.java:360)
          at javax.xml.messaging.JAXMServlet.doPost(Unknown Source)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
          (ServletStubImpl.java:1058)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
          pl.java:401)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
          pl.java:306)
          at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
          n.run(WebAppServletContext.java:5445)
          at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
          eManager.java:780)
          at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
          rvletContext.java:3105)
          at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
          pl.java:2588)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
          >
          I've stripped the code down so that all it does is verifies the incoming SOAP/XML
          request and creates a hard-coded response... be gentle... I'm a novice at this
          import javax.xml.soap.*;
          import javax.servlet.*;
          import javax.servlet.http.*;
          // import javax.xml.transform.*;
          import java.util.*;
          import java.io.*;
          public class RegisterServlet extends HttpServlet
          static MessageFactory fac = null;
          static
          try
          fac = MessageFactory.newInstance();
          catch (Exception ex)
          ex.printStackTrace();
          public void init(ServletConfig servletConfig) throws ServletException
          super.init(servletConfig);
          public void doPost(HttpServletRequest req, HttpServletResponse resp) throws ServletException,
          IOException
          try
          System.out.println("** Note: doPost() Entering req = " + req);
          // Get all the headers from the HTTP request
          MimeHeaders headers = getHeaders(req);
          // Get the body of the HTTP request
          InputStream is = req.getInputStream();
          // Now internalize the contents of a HTTP request
          // and create a SOAPMessage
          SOAPMessage msg = fac.createMessage(headers, is);
          System.out.println("** Note: doPost() Step A");
          SOAPMessage reply = null;
          reply = onMessage(msg);
          System.out.println("** Note: doPost() Step B reply = " + reply);
          if (reply != null)
          * Need to call saveChanges because we're
          * going to use the MimeHeaders to set HTTP
          * response information. These MimeHeaders
          * are generated as part of the save.
          if (reply.saveRequired())
          System.out.println("** Note: doPost() Step C reply.saveRequired()");
          reply.saveChanges();
          resp.setStatus(HttpServletResponse.SC_OK);
          putHeaders(reply.getMimeHeaders(), resp);
          // Write out the message on the response stream
          OutputStream os = resp.getOutputStream();
          System.out.println("** Note: doPost() Step D os = " + os);
          reply.writeTo(os);
          os.flush();
          else
          resp.setStatus(HttpServletResponse.SC_NO_CONTENT);
          catch (Exception ex)
          throw new ServletException("** Error: SAAJ POST failed: " + ex.getMessage());
          static MimeHeaders getHeaders(HttpServletRequest req)
          Enumeration enum = req.getHeaderNames();
          MimeHeaders headers = new MimeHeaders();
          while (enum.hasMoreElements())
          String headerName = (String)enum.nextElement();
          String headerValue = req.getHeader(headerName);
          StringTokenizer values =
          new StringTokenizer(headerValue, ",");
          while (values.hasMoreTokens())
          headers.addHeader(headerName,
          values.nextToken().trim());
          return headers;
          static void putHeaders(MimeHeaders headers, HttpServletResponse res)
          Iterator it = headers.getAllHeaders();
          while (it.hasNext())
          MimeHeader header = (MimeHeader)it.next();
          String[] values = headers.getHeader(header.getName());
          if (values.length == 1)
          res.setHeader(header.getName(),
          header.getValue());
          else
          StringBuffer concat = new StringBuffer();
          int i = 0;
          while (i < values.length)
          if (i != 0)
          concat.append(',');
          concat.append(values[i++]);
          res.setHeader(header.getName(), concat.toString());
          // This is the application code for handling the message.
          public SOAPMessage onMessage(SOAPMessage message)
          SOAPMessage replymsg = null;
          try
          System.out.println("** Note: OnMessage() Entering msg = " + message);
          //Extract the ComputerPart element from request message and add to reply SOAP
          message.
          SOAPEnvelope reqse = message.getSOAPPart().getEnvelope();
          SOAPBody reqsb = reqse.getBody();
          //System.out.println("** Note: OnMessage() Step B");
          System.out.println("** Note: OnMessage () Step A Soap Request Message Body = "
          + reqsb);
          //Create a reply mesage from the msgFactory of JAXMServlet
          System.out.println("** Note: OnMessage () Step B");
          replymsg = fac.createMessage();
          SOAPPart sp = replymsg.getSOAPPart();
          SOAPEnvelope se = sp.getEnvelope();
          SOAPBody sb = se.getBody();
          System.out.println("** Note: OnMessage () Step C Soap Reply Before Message Body
          = " + sb);
          se.getBody().addBodyElement(se.createName("RegisterResponse")).addChildElement(se.createName("ErrorCode")).addTextNode("000");
          System.out.println("** Note: OnMessage () Step D Soap Reply After Message Body
          = " + sb);
          replymsg.saveChanges();
          System.out.println("** Note: OnMessage() Exiting replymsg = " + (replymsg));
          catch (Exception ex)
          ex.printStackTrace();
          return replymsg;


Michael,
I got the same error on WLS8.1/Win2K professional and apache FOP (old version).
After digging into the WLS code and FOP(old version). i found the conflict happens
on
the "org.xml.sax.parser" system property. In WLS code, they hard coded like the
following when startup weblogic server:
System.setProperty("org.xml.sax.parser", "weblogic.xml.jaxp.RegistryParser");
But the FOP code try to use the "org.xml.sax.parser" system property to find the
sax parser then conlict happens.
Here is the response from BEA support :
"I consulted with our developers regarding the question of whether we can change
the hard-coded value for the java system property: org.xml.sax.parser by using
a configuration parameter and I found that unfortunately there is no specific
setting to change the value. As you had mentioned in your note the org.xml.sax.parser
system property can be changed programmatically in your application code."
I solve my problem by using newer apache FOP (it never use the system property:org.xml.sax.parser
any more) and XML Registy for WLS8.1.
Good luck.
David Liu
Point2 Technologies Inc.
"p_michael" <[email protected]> wrote:
>
Help.
When we migrated from WLS 6.1 to WLS 7.0 SP2 when encountered a problem
with XML
parsing that did not previously exist.
We get the error "weblogic.xml.jaxp.RegistryParser is not a SAX driver".
What does this mean? And, what should we do about it.
p_michael

[WLS 8.1] - AbstractMethodError using javax.sql.DataSource getConnection()

[WLS 8.1.3] I'm getting an error while trying to execute the getConnection() method of javax.sql.DataSource.
The same code, test data, WLS JDBC connection & data source runs fine on HP-UX but when I try to run it on XP, I get an error.(see below) Our code calls the getConnection() method several times and it actually works the first few times in the transaction but then fails after the 5th or 6th call. We're using the weblogic.jdbc.oci.Driver in both HP-UX & XP and the JDBC settings are identical. I've tried the same query in SQLPLUS as what's being used in the prepared statement and it works fine.
The error message is as follows:
Transaction BEA1-0002AD72C454EBACDA96 not active anymore. tx status = Marked rollback. [Reason=java.lang.AbstractMethodError: weblogic.xml.schema.binding.BeanCodecBase.getCompositor()Lweblogic/xml/schema/binding/ModelGroupCompositor;]>
The code snippet that gets the error:
Context ctx = new InitialContext();
ds = (javax.sql.DataSource) ctx.lookup ("com.xxxx.yyyy.zzzz");
conn = ds.getConnection();
Any ideas what could cause this error?

I turned JDBC logging on but the only SQLExceptions I could find in the JDBC log where some "java.sql.SQLException: Result set already closed" errors. Not ideal but the db calls actually worked and those errors were not in the same place in the code. I'm looking into why these are occurring but I don't think this is the root problem of the AbstractMethodError as the same SQLException occurs in the JDBC logs on UNIX where the AbstractMethodError is not being thrown. I can include a stack trace of the SQLException if you still think it might help.
While searching the logs, I found other occurrences of the AbstractMethodError. I also noticed there is a JDK version difference between the WLS 8.1.3 for XP and the one for HP-UX. The XP version has JDK 142_04 and the HP-UX has 142_03.
Here's a stack trace of the other AbstractMethodError I found from one of the EJB's:
####<Oct 6, 2004 6:41:35 AM PDT> <Info> <EJB> <JEAGLEMXP> <lnppiServer> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<anonymous>> <BEA1-00009C0656BCEBACDA96> <BEA-010051> <EJB Exception occurred during invocation from home: com.qwest.lnppi.business.port.PortedTnEjb_rn88fn_HomeImpl@26d560 threw exception: java.lang.AbstractMethodError: weblogic.xml.schema.binding.BeanCodecBase.getCompositor()Lweblogic/xml/schema/binding/ModelGroupCompositor;
java.lang.AbstractMethodError: weblogic.xml.schema.binding.BeanCodecBase.getCompositor()Lweblogic/xml/schema/binding/ModelGroupCompositor;
     at weblogic.xml.schema.binding.BeanCodecBase.gatherContents(BeanCodecBase.java:299)
     at weblogic.xml.schema.binding.CodecBase.serializeFill(CodecBase.java:285)
     at weblogic.xml.schema.binding.CodecBase.serialize_internal(CodecBase.java:222)
     at weblogic.xml.schema.binding.CodecBase.serialize(CodecBase.java:181)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:188)
     at weblogic.xml.schema.binding.RuntimeUtils.invoke_serializer(RuntimeUtils.java:174)
     at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:324)
     at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:297)
     at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:645)
     at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:206)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:443)
     at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:290)
     at com.qwest.lnppi.portedTNservice.PortedTelephoneNumber_Stub.getPortedTelelphoneNumber(Unknown Source)
     at com.qwest.lnppi.business.port.PortedTnBean.portedTnWS(Unknown Source)
     at com.qwest.lnppi.business.port.PortedTnBean.portedTn(Unknown Source)
     at com.qwest.lnppi.business.port.PortedTnEjb_rn88fn_EOImpl.portedTn(PortedTnEjb_rn88fn_EOImpl.java:98)
     at com.qwest.lnppi.business.svc.GetCurrentServiceProviderSwitch.getCurrentServiceProviderSwitch(Unknown Source)
     at com.qwest.lnppi.business.svc.LnppiServiceBean.getPortingOptions(Unknown Source)
     at com.qwest.lnppi.business.svc.LnppiServiceEjb_tk1dpv_EOImpl.getPortingOptions(LnppiServiceEjb_tk1dpv_EOImpl.java:46)
     at com.qwest.lnppi.web.lnppiTester.Tester.CallTheBean(Unknown Source)
     at com.qwest.lnppi.web.lnppiTester.Tester.TestIt(Unknown Source)
     at jsp_servlet.__tester._jspService(__tester.java:157)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
     at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:312)
     at com.qwest.lnppi.web.lnppiTester.pgMgr.doTestIt(Unknown Source)
     at com.qwest.lnppi.web.lnppiTester.pgMgr.service(Unknown Source)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6452)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3661)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2630)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
>

XMLSPY Special Edition for BEA WebLogic 8.1 and WLS 8.1 sp2

Hi,
I'm a newbie for WebLogic Server. I started with WLS 8.1 sp2 since I got the book "J2EE Applications and BEA WebLogic Server 2nd Edition" which was written for WLS 8.1.
While XMLSPY Special Edition for BEA WebLogic (version 5.4 something, built in 2003) is indeed packaged with WLS 8.1 sp2 and can be installed, but it'll pop up a window (ALTOVA License Manager) everytime when I try to use it. This window pops up because the license key is not installed during the installation and therefore can't be used unless a valid key is provided.
I wonder whether I really need to get XMLSPY Special Edition for BEA WebLogic 8.1 working in order to use WLS 8.1 just for the purpose of learning. If so, can someone share with me the the key-code for XMLSPY Special Edition for BEA WebLogic 8.1 please?
BTW, I tried to find something useful to this question/problem at ALTOVA website, no luck at all.
Thank you very much.
JF

Hi Ravi,
Thanks very much for your very helpful reply.
I got into the problem with xmlspy while I was trying to figure out why the WLS admin console missing the left pane/sidebar. There was only one non-expandable dot sign at the lefttop in the admin console. When I right-click on that little dot icon, the pulldown menu shows one option is to use XMLSPY to check (something along that line). Also, I see the XMLSPY button at the left bottom of my W2003 windows (just next to IE button). So, either way when I invoked XMLSPY I would get that pop up window which tells me there choices: type in a key-code, request for a trial key, or buy a license key. But eventually, I figured out the way to fix my problem - installing a newer version of j2sdk code. However, I wasn't sure whether the xmlspy issue would a hidden problem further down the road for me to learn WLS 8.1.
You're absoluately right commenting on the the right version of WLS to use at the beginning of learning WLS.
I have been VMWare Workstation for several months. I've created a CentOS 5.4 VM with WLS 11g installed. I played with with WLS 11g for a while and even followed through an Oracle online tutorial for that version. But I'm just used to learn something with a hard copy of book and I happen to have this old book on WLS 8.1 which seems to be highly rated before. I may continue to go through this book quickly if I can. However, if I experience too many hard problems down the road, I won't waste too much more time on this path. My long term goal is of course to learn more and better about WLS 11g and other Oracle related framework and tools. There is too much to learn. But the good thing is that Oracle provides everything free to learn. Also, I'm very encouraged by the quality of the Oracle tech group where I can turn for very useful help.
Thanks again and best regards,
JF

Problem starting wls 6.1 sp2

Hi
I have developed an appliaction using wls 6.1 sp2 on w2k, which I want to migrate
to Solaris 8.
I have modified my windows statup scripts to Solaris, but I get a strange error
when starting weblogic. I am starting the server as root and my weblogic.policy
file is modified according to my installation.
Has anybody encountered anything similar?
<Feb 20, 2002 12:08:09 PM CET> <Critical> <Management> <Unable to deploy an internal
management web application - <all-internal-apps>. Managed servers may be unable
to start.
java.io.FileNotFoundException: ./config/Certifikat/.wlstaging/wl_management_internal2.war
(No such file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
at java.io.FileOutputStream.<init>(FileOutputStream.java:62)
at java.io.FileOutputStream.<init>(FileOutputStream.java:132)
at weblogic.management.mbeans.custom.ApplicationManager.stageGlobalWarFile(ApplicationManager.java:398)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:334)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy35.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
at weblogic.management.Admin.finish(Admin.java:561)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
at weblogic.Server.main(Server.java:35)
>
My startup script is as follows
bash-2.03$ more startWeblogic.sh
#!/usr/bin/bash
# Set user-defined variables.
export PROJECT=postdanmark
export ENVIRONMENT=test
export RELEASE_DIR=/opt/projects/$PROJECT/$ENVIRONMENT/lib
export JAVA_HOME=/opt/jdk/j2sdk1_3_1_02
export WEBLOGIC_HOME=/opt/bea/weblogic/6.1
export PATH=$WEBLOGIC_HOME/bin:$JAVA_HOME/jre/bin:$JAVA_HOME/bin:.:$PATH
export CLASSPATH=$RELEASE_DIR/internal/util/1.0/Util.jar
export CLASSPATH=$CLASSPATH:$WEBLOGIC_HOME/lib/weblogic.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/sun/jaxb/1.0ea/lib/jaxb-rt-1.0-ea.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/postdanmark/1.0/PostDanmarkPC.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/EntrustCAEjb/1.0/EntrustCAEjb.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/websupport/1.0/WebSupport.jar
export CLASSPATH=$CLASSPATH:/opt/projects/$PROJECT/$ENVIRONMENT/batch/properties
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/corba/interfaces/entrustca/1.2/EntrustCA.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/mysql/jdbc/2.0.4/mm.mysql-2.0.4-bin.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entbase.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entuser.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entp7.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entmisc.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entcertlist.jar
echo off
echo *********************************************
echo * Starting weblogic application server *
echo *********************************************
# Set WLS_PW equal to your system password for no password prompt server startup.
export WLS_PW=certifikat
# Set Production Mode. When set to true, the server starts up in production mode.
When set to false, the server starts up i
n development mode. The default is false.
export STARTMODE=false
export WEBLOGIC_OPTIONS='-Dweblogic.Domain=Certifikat'
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.Name=PostDanmarkServer"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.discover=false"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dbea.home=/opt/bea/weblogic/6.1"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.home=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.dir=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.password=$WLS_PW"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.ProductionModeEnabled=$STARTMODE"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.security.policy=$WEBLOGIC_HOME/lib/weblogic.policy"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.RootDirectory=/opt/projects/$PROJECT/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.util.logging.config.file=/opt/projects/$PROJECT/$ENVIRONMENT/batch/proper
ties/logging.properties"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.library.path=$WEBLOGIC_HOME/lib/solaris:$WEBLOGIC_HOME/lib/solaris/oci816
_8"
export JAVA_OPTIONS='-hotspot -ms64m -mx64m -classpath '
export JAVA_OPTIONS=${JAVA_OPTIONS}$CLASSPATH
echo on
echo "using JAVA OPTIONS : "$JAVA_OPTIONS"
echo "using WEBLOGIC OPTIONS : "$WEBLOGIC_OPTIONS"
"$JAVA_HOME/bin/java" $JAVA_OPTIONS $WEBLOGIC_OPTIONS weblogic.Server

Hi.
Try placing the wl_management_internal2.war file from the mydomain/.wlstaging directory into the directory your server is expecting.
Regards,
Michael
Peter Buus wrote:
Hi
I have developed an appliaction using wls 6.1 sp2 on w2k, which I want to migrate
to Solaris 8.
I have modified my windows statup scripts to Solaris, but I get a strange error
when starting weblogic. I am starting the server as root and my weblogic.policy
file is modified according to my installation.
Has anybody encountered anything similar?
<Feb 20, 2002 12:08:09 PM CET> <Critical> <Management> <Unable to deploy an internal
management web application - <all-internal-apps>. Managed servers may be unable
to start.
java.io.FileNotFoundException: ./config/Certifikat/.wlstaging/wl_management_internal2.war
(No such file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
at java.io.FileOutputStream.<init>(FileOutputStream.java:62)
at java.io.FileOutputStream.<init>(FileOutputStream.java:132)
at weblogic.management.mbeans.custom.ApplicationManager.stageGlobalWarFile(ApplicationManager.java:398)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:334)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy35.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
at weblogic.management.Admin.finish(Admin.java:561)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
at weblogic.Server.main(Server.java:35)
>
My startup script is as follows
bash-2.03$ more startWeblogic.sh
#!/usr/bin/bash
# Set user-defined variables.
export PROJECT=postdanmark
export ENVIRONMENT=test
export RELEASE_DIR=/opt/projects/$PROJECT/$ENVIRONMENT/lib
export JAVA_HOME=/opt/jdk/j2sdk1_3_1_02
export WEBLOGIC_HOME=/opt/bea/weblogic/6.1
export PATH=$WEBLOGIC_HOME/bin:$JAVA_HOME/jre/bin:$JAVA_HOME/bin:.:$PATH
export CLASSPATH=$RELEASE_DIR/internal/util/1.0/Util.jar
export CLASSPATH=$CLASSPATH:$WEBLOGIC_HOME/lib/weblogic.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/sun/jaxb/1.0ea/lib/jaxb-rt-1.0-ea.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/postdanmark/1.0/PostDanmarkPC.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/EntrustCAEjb/1.0/EntrustCAEjb.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/websupport/1.0/WebSupport.jar
export CLASSPATH=$CLASSPATH:/opt/projects/$PROJECT/$ENVIRONMENT/batch/properties
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/corba/interfaces/entrustca/1.2/EntrustCA.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/mysql/jdbc/2.0.4/mm.mysql-2.0.4-bin.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entbase.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entuser.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entp7.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entmisc.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entcertlist.jar
echo off
echo *********************************************
echo * Starting weblogic application server *
echo *********************************************
# Set WLS_PW equal to your system password for no password prompt server startup.
export WLS_PW=certifikat
# Set Production Mode. When set to true, the server starts up in production mode.
When set to false, the server starts up i
n development mode. The default is false.
export STARTMODE=false
export WEBLOGIC_OPTIONS='-Dweblogic.Domain=Certifikat'
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.Name=PostDanmarkServer"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.discover=false"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dbea.home=/opt/bea/weblogic/6.1"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.home=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.dir=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.password=$WLS_PW"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.ProductionModeEnabled=$STARTMODE"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.security.policy=$WEBLOGIC_HOME/lib/weblogic.policy"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.RootDirectory=/opt/projects/$PROJECT/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.util.logging.config.file=/opt/projects/$PROJECT/$ENVIRONMENT/batch/proper
ties/logging.properties"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.library.path=$WEBLOGIC_HOME/lib/solaris:$WEBLOGIC_HOME/lib/solaris/oci816
_8"
export JAVA_OPTIONS='-hotspot -ms64m -mx64m -classpath '
export JAVA_OPTIONS=${JAVA_OPTIONS}$CLASSPATH
echo on
echo "using JAVA OPTIONS : "$JAVA_OPTIONS"
echo "using WEBLOGIC OPTIONS : "$WEBLOGIC_OPTIONS"
"$JAVA_HOME/bin/java" $JAVA_OPTIONS $WEBLOGIC_OPTIONS weblogic.Server--
Michael Young
Developer Relations Engineer
BEA Support

Deploying a webservice on WLS 9.1 and got an wsdl error.

Hi,
I hoped it is then right usergroup to publish the following question.
I'm trying to deploy a EJB webservice on a WLS 9.1.
But I got the following error message:
[java] port component "SystemServiceEndpointPort" is not found in wsdl.
It's simple JAX-RPC based webservice where a SessionBean method is used as
the service implementation. The same configuration (webservice.xml,
jaxrpc-mapping-SystemService.xml, SystemService.wsdl) works fine under JBoss 4.0, but not with
WLS 9.1. Maybe it's a simple configuration error and I hope someone can help.
I haved remembered the namespace in the webservices.xml file: <wsdl-port>wsdl:SystemServiceEndpointPort</wsdl-port> and also defined et in the top of the file.
Regards
Torben
<b>webservices.xml</b>
<webservices
xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:wsdl="http://www.organisator.dk"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/j2ee_web_services_1_1.xsd"
version="1.1">
<webservice-description>
<icon></icon>
<webservice-description-name>SystemService</webservice-description-name>
<wsdl-file>META-INF/wsdl/SystemService.wsdl</wsdl-file>
<jaxrpc-mapping-file>META-INF/jaxrpc-mapping-SystemService.xml</jaxrpc-mapping-file>
<port-component>
<icon></icon>
<port-component-name>SystemServiceEndpointPort</port-component-name>
<wsdl-port>wsdl:SystemServiceEndpointPort</wsdl-port>
<service-endpoint-interface>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint</service-endpoint-interface>
<service-impl-bean>
<ejb-link>SCSystem</ejb-link>
</service-impl-bean>
</port-component>
</webservice-description>
</webservices>
<b>weblogic-webservices.xml</b>
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-webservices xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<webservice-description>
<webservice-description-name>SystemService</webservice-description-name>
<port-component>
<port-component-name>SystemServiceEndpointPort</port-component-name>
<service-endpoint-address>
<webservice-contextpath>/winnie</webservice-contextpath>
<webservice-serviceuri>/SystemService</webservice-serviceuri>
</service-endpoint-address>
</port-component>
</webservice-description>
</weblogic-webservices>
<b>ejb-jar.xml</b>
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd" version="2.1">
<description><![CDATA[No Description.]]></description>
<display-name>Generated by XDoclet</display-name>
<enterprise-beans>

<session >
<description><![CDATA[System information handler]]></description>
<display-name>SCSystem</display-name>
<ejb-name>SCSystem</ejb-name>
<home>dk.organisator.winnie.system.ejbsystem.services.SCSystemHome</home>
<remote>dk.organisator.winnie.system.ejbsystem.services.SCSystemRemote</remote>
<service-endpoint>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint</service-endpoint>
<ejb-class>dk.organisator.winnie.system.ejbsystem.services.SCSystemBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
<b>SystemService.wsdl</b>
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="SystemService" targetNamespace="http://organisator.dk/winnie/wsdl" xmlns:tns="http://organisator.dk/winnie/wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns2="http://organisator.dk/winnie/types" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types>
<schema targetNamespace="http://organisator.dk/winnie/types" xmlns:tns="http://organisator.dk/winnie/types" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema">
<complexType name="getXxxxxxxxx">
<sequence>
<element name="String_1" type="string" nillable="true"/></sequence></complexType>
<complexType name="getXxxxxxxxxResponse">
<sequence>
<element name="result" type="string" nillable="true"/></sequence></complexType>
<complexType name="ping">
<sequence/></complexType>
<complexType name="pingResponse">
<sequence>
<element name="result" type="int"/></sequence></complexType>
<complexType name="setXxxxxxxx">
<sequence>
<element name="String_1" type="string" nillable="true"/></sequence></complexType>
<complexType name="setXxxxxxxxResponse">
<sequence/></complexType>
<element name="getXxxxxxxxx" type="tns:getXxxxxxxxx"/>
<element name="getXxxxxxxxxResponse" type="tns:getXxxxxxxxxResponse"/>
<element name="ping" type="tns:ping"/>
<element name="pingResponse" type="tns:pingResponse"/>
<element name="setXxxxxxxx" type="tns:setXxxxxxxx"/>
<element name="setXxxxxxxxResponse" type="tns:setXxxxxxxxResponse"/></schema></types>
<message name="SystemServiceEndpoint_getXxxxxxxxx">
<part name="parameters" element="ns2:getXxxxxxxxx"/></message>
<message name="SystemServiceEndpoint_getXxxxxxxxxResponse">
<part name="result" element="ns2:getXxxxxxxxxResponse"/></message>
<message name="SystemServiceEndpoint_ping">
<part name="parameters" element="ns2:ping"/></message>
<message name="SystemServiceEndpoint_pingResponse">
<part name="result" element="ns2:pingResponse"/></message>
<message name="SystemServiceEndpoint_setXxxxxxxx">
<part name="parameters" element="ns2:setXxxxxxxx"/></message>
<message name="SystemServiceEndpoint_setXxxxxxxxResponse">
<part name="result" element="ns2:setXxxxxxxxResponse"/></message>
<portType name="SystemServiceEndpoint">
<operation name="getXxxxxxxxx">
<input message="tns:SystemServiceEndpoint_getXxxxxxxxx"/>
<output message="tns:SystemServiceEndpoint_getXxxxxxxxxResponse"/></operation>
<operation name="ping">
<input message="tns:SystemServiceEndpoint_ping"/>
<output message="tns:SystemServiceEndpoint_pingResponse"/></operation>
<operation name="setXxxxxxxx">
<input message="tns:SystemServiceEndpoint_setXxxxxxxx"/>
<output message="tns:SystemServiceEndpoint_setXxxxxxxxResponse"/></operation></portType>
<binding name="SystemServiceEndpointBinding" type="tns:SystemServiceEndpoint">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="getXxxxxxxxx">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/></input>
<output>
<soap:body use="literal"/></output></operation>
<operation name="ping">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/></input>
<output>
<soap:body use="literal"/></output></operation>
<operation name="setXxxxxxxx">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/></input>
<output>
<soap:body use="literal"/></output></operation></binding>
<service name="SystemService">
<port name="SystemServiceEndpointPort" binding="tns:SystemServiceEndpointBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/></port></service></definitions>
<b>jaxrpc-mapping-SystemService.xml</b>
<?xml version="1.0" encoding="UTF-8"?>
<java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.1" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
<package-mapping>
<package-type>dk.organisator.winnie.system.ejbsystem.services</package-type>
<namespaceURI>http://organisator.dk/winnie/types</namespaceURI>
</package-mapping>
<package-mapping>
<package-type>dk.organisator.winnie.system.ejbsystem.services</package-type>
<namespaceURI>http://organisator.dk/winnie/wsdl</namespaceURI>
</package-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_ping_ResponseStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:pingResponse</root-type-qname>
<qname-scope>complexType</qname-scope>
<variable-mapping>
<java-variable-name>result</java-variable-name>
<xml-element-name>result</xml-element-name>
</variable-mapping>
</java-xml-type-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_getXxxxxxxxx_RequestStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:getXxxxxxxxx</root-type-qname>
<qname-scope>complexType</qname-scope>
<variable-mapping>
<java-variable-name>String_1</java-variable-name>
<xml-element-name>String_1</xml-element-name>
</variable-mapping>
</java-xml-type-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_setXxxxxxxx_ResponseStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:setXxxxxxxxResponse</root-type-qname>
<qname-scope>complexType</qname-scope>
</java-xml-type-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_setXxxxxxxx_RequestStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:setXxxxxxxx</root-type-qname>
<qname-scope>complexType</qname-scope>
<variable-mapping>
<java-variable-name>String_1</java-variable-name>
<xml-element-name>String_1</xml-element-name>
</variable-mapping>
</java-xml-type-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_ping_RequestStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:ping</root-type-qname>
<qname-scope>complexType</qname-scope>
</java-xml-type-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_getXxxxxxxxx_ResponseStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:getXxxxxxxxxResponse</root-type-qname>
<qname-scope>complexType</qname-scope>
<variable-mapping>
<java-variable-name>result</java-variable-name>
<xml-element-name>result</xml-element-name>
</variable-mapping>
</java-xml-type-mapping>
<service-interface-mapping>
<service-interface>dk.organisator.winnie.system.ejbsystem.services.SystemService</service-interface>
<wsdl-service-name xmlns:serviceNS="http://organisator.dk/winnie/wsdl">serviceNS:SystemService</wsdl-service-name>
<port-mapping>
<port-name>SystemServiceEndpointPort</port-name>
<java-port-name>SystemServiceEndpointPort</java-port-name>
</port-mapping>
</service-interface-mapping>
<service-endpoint-interface-mapping>
<service-endpoint-interface>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint</service-endpoint-interface>
<wsdl-port-type xmlns:portTypeNS="http://organisator.dk/winnie/wsdl">portTypeNS:SystemServiceEndpoint</wsdl-port-type>
<wsdl-binding xmlns:bindingNS="http://organisator.dk/winnie/wsdl">bindingNS:SystemServiceEndpointBinding</wsdl-binding>
<service-endpoint-method-mapping>
<java-method-name>getXxxxxxxxx</java-method-name>
<wsdl-operation>getXxxxxxxxx</wsdl-operation>
<wrapped-element/>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message xmlns:wsdlMsgNS="http://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_getXxxxxxxxx</wsdl-message>
<wsdl-message-part-name>String_1</wsdl-message-part-name>
<parameter-mode>IN</parameter-mode>
</wsdl-message-mapping>
</method-param-parts-mapping>
<wsdl-return-value-mapping>
<method-return-value>java.lang.String</method-return-value>
<wsdl-message xmlns:wsdlMsgNS="http://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_getXxxxxxxxxResponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
<service-endpoint-method-mapping>
<java-method-name>ping</java-method-name>
<wsdl-operation>ping</wsdl-operation>
<wrapped-element/>
<wsdl-return-value-mapping>
<method-return-value>int</method-return-value>
<wsdl-message xmlns:wsdlMsgNS="http://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_pingResponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
<service-endpoint-method-mapping>
<java-method-name>setXxxxxxxx</java-method-name>
<wsdl-operation>setXxxxxxxx</wsdl-operation>
<wrapped-element/>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message xmlns:wsdlMsgNS="http://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_setXxxxxxxx</wsdl-message>
<wsdl-message-part-name>String_1</wsdl-message-part-name>
<parameter-mode>IN</parameter-mode>
</wsdl-message-mapping>
</method-param-parts-mapping>
</service-endpoint-method-mapping>
</service-endpoint-interface-mapping>
</java-wsdl-mapping>

the problem is with the xmlns:wsdl="http://www.organisator.dk" line in your webservices.xml. It does not match the namespace of the corresponding PortType in your wsdl: targetNamespace="http://organisator.dk/winnie/wsdl"

Deploying an EJB WebService under WLS 9.1 - port component "Hello" is not found in wsdl.

Hi,
I'm trying to deploy a simple EJB webservice example on WLS 9.1. The appc
compile works fine, but the server deployment throw the following error
message:
[java] port component "Hello" is not found in wsdl.
It's simple JAX-RPC based webservice where a SessionBean method is used as
the service implementation. The same configuration (webservice.xml,
mapping.xml and HelloService.wsdl) works fine under JBoss 4.0, but not with
WLS 9.1. Maybe it's a simple configuration error and someone can help.
Regards
Guido
Appendix
webservice.xml
<webservices xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1\.xsd"
version="1.1">
<webservice-description>
<webservice-description-name>HelloService</webservice-description-name>
<wsdl-file>META-INF/wsdl/HelloService.wsdl</wsdl-file>
<jaxrpc-mapping-file>META-INF/mapping.xml</jaxrpc-mapping-file>
<port-component>
<port-component-name>Hello</port-component-name>
<wsdl-port>HelloPort</wsdl-port>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<service-impl-bean>
<ejb-link>HelloBean</ejb-link>
</service-impl-bean>
</port-component>
</webservice-description>
</webservices>
mapping.xml
<?xml version="1.0" encoding="UTF-8"?>
<java-wsdl-mapping version="1.1" xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/types</namespaceURI>
</package-mapping>
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/</namespaceURI>
</package-mapping>
<service-interface-mapping>
<service-interface>com.jcoffee.components.ws.HelloService</service-interface
>
<wsdl-service-name
xmlns:serviceNS="http://ws.components.jcoffee.com/">serviceNS:HelloService</
wsdl-service-name>
<port-mapping>
<port-name>HelloPort</port-name>
<java-port-name>HelloPort</java-port-name>
</port-mapping>
</service-interface-mapping>
<service-endpoint-interface-mapping>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<wsdl-port-type
xmlns:portTypeNS="http://ws.components.jcoffee.com/">portTypeNS:Hello</wsdl-
port-type>
<wsdl-binding
xmlns:bindingNS="http://ws.components.jcoffee.com/">bindingNS:HelloBinding</
wsdl-binding>
<service-endpoint-method-mapping>
<java-method-name>hello</java-method-name>
<wsdl-operation>hello</wsdl-operation>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_hello</w
sdl-message>
<wsdl-message-part-name>String_1</wsdl-message-part-name>
<parameter-mode>IN</parameter-mode>
</wsdl-message-mapping>
</method-param-parts-mapping>
<wsdl-return-value-mapping>
<method-return-value>java.lang.String</method-return-value>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_helloRes
ponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
</service-endpoint-interface-mapping>
</java-wsdl-mapping>
HelloService.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="HelloService"
targetNamespace="http://ws.components.jcoffee.com/"
xmlns:tns="http://ws.components.jcoffee.com/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types/>
<message name="Hello_hello">
<part name="String_1" type="xsd:string"/>
</message>
<message name="Hello_helloResponse">
<part name="result" type="xsd:string"/>
</message>
<portType name="Hello">
<operation name="hello" parameterOrder="String_1">
<input message="tns:Hello_hello"/>
<output message="tns:Hello_helloResponse"/>
</operation>
</portType>
<binding name="HelloBinding" type="tns:Hello">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="hello">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</input>
<output>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</output>
</operation>
</binding>
<service name="HelloService">
<port name="HelloPort" binding="tns:HelloBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/>
</port>
</service>
</definitions>
and last but not least the ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
<display-name>JCoffee web service sample</display-name>
<enterprise-beans>
<session>
<ejb-name>HelloBean</ejb-name>
<service-endpoint>com.jcoffee.components.ws.Hello</service-endpoint>
<ejb-class>com.jcoffee.components.ws.HelloBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<method-permission>
<unchecked/>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
<container-transaction>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

Hi again,
I got it - i've forgot the namespace prefix for the wsdl-port.
Now it works.
Thanks!
"Ben" <[email protected]> schrieb im Newsbeitrag
news:[email protected]...
Hi,
I'm trying to deploy a simple EJB webservice example on WLS 9.1. The appc
compile works fine, but the server deployment throw the following error
message:
[java] port component "Hello" is not found in wsdl.
It's simple JAX-RPC based webservice where a SessionBean method is used as
the service implementation. The same configuration (webservice.xml,
mapping.xml and HelloService.wsdl) works fine under JBoss 4.0, but notwith
WLS 9.1. Maybe it's a simple configuration error and someone can help.
Regards
Guido
Appendix
webservice.xml
<webservices xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1\.xsd"
version="1.1">
<webservice-description>
<webservice-description-name>HelloService</webservice-description-name>
<wsdl-file>META-INF/wsdl/HelloService.wsdl</wsdl-file>
<jaxrpc-mapping-file>META-INF/mapping.xml</jaxrpc-mapping-file>
<port-component>
<port-component-name>Hello</port-component-name>
<wsdl-port>HelloPort</wsdl-port>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<service-impl-bean>
<ejb-link>HelloBean</ejb-link>
</service-impl-bean>
</port-component>
</webservice-description>
</webservices>
mapping.xml
<?xml version="1.0" encoding="UTF-8"?>
<java-wsdl-mapping version="1.1" xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/types</namespaceURI>
</package-mapping>
<package-mapping>
<package-type>com.jcoffee.components.ws</package-type>
<namespaceURI>http://ws.components.jcoffee.com/</namespaceURI>
</package-mapping>
<service-interface-mapping>
<service-interface>com.jcoffee.components.ws.HelloService</service-interface
>>
<wsdl-service-name
xmlns:serviceNS="http://ws.components.jcoffee.com/">serviceNS:HelloService</
wsdl-service-name>
<port-mapping>
<port-name>HelloPort</port-name>
<java-port-name>HelloPort</java-port-name>
</port-mapping>
</service-interface-mapping>
<service-endpoint-interface-mapping>
<service-endpoint-interface>com.jcoffee.components.ws.Hello</service-endpoin
t-interface>
<wsdl-port-type
xmlns:portTypeNS="http://ws.components.jcoffee.com/">portTypeNS:Hello</wsdl-
port-type>
<wsdl-binding
xmlns:bindingNS="http://ws.components.jcoffee.com/">bindingNS:HelloBinding</
wsdl-binding>
<service-endpoint-method-mapping>
<java-method-name>hello</java-method-name>
<wsdl-operation>hello</wsdl-operation>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_hello</w
sdl-message>
<wsdl-message-part-name>String_1</wsdl-message-part-name>
<parameter-mode>IN</parameter-mode>
</wsdl-message-mapping>
</method-param-parts-mapping>
<wsdl-return-value-mapping>
<method-return-value>java.lang.String</method-return-value>
<wsdl-message
xmlns:wsdlMsgNS="http://ws.components.jcoffee.com/">wsdlMsgNS:Hello_helloRes
ponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
</service-endpoint-interface-mapping>
</java-wsdl-mapping>
HelloService.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="HelloService"
targetNamespace="http://ws.components.jcoffee.com/"
xmlns:tns="http://ws.components.jcoffee.com/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types/>
<message name="Hello_hello">
<part name="String_1" type="xsd:string"/>
</message>
<message name="Hello_helloResponse">
<part name="result" type="xsd:string"/>
</message>
<portType name="Hello">
<operation name="hello" parameterOrder="String_1">
<input message="tns:Hello_hello"/>
<output message="tns:Hello_helloResponse"/>
</operation>
</portType>
<binding name="HelloBinding" type="tns:Hello">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="rpc"/>
>
>
<operation name="hello">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</input>
<output>
<soap:body use="literal" namespace="http://ws.components.jcoffee.com/"/>
</output>
</operation>
</binding>
<service name="HelloService">
<port name="HelloPort" binding="tns:HelloBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/>
</port>
</service>
</definitions>
and last but not least the ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
<display-name>JCoffee web service sample</display-name>
<enterprise-beans>
<session>
<ejb-name>HelloBean</ejb-name>
<service-endpoint>com.jcoffee.components.ws.Hello</service-endpoint>
<ejb-class>com.jcoffee.components.ws.HelloBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<method-permission>
<unchecked/>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
<container-transaction>
<method>
<ejb-name>HelloBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

Wls 8.1 sp2: weblogic.jspc complains about struts-html tags

          Hi,
          I am trying to compile jsps with weblogic.jspc, which use struts' html tags. However,
          the compilation fails with the following message:
          [java] Translation of /views/viewPageBody.jsp failed: (line 3): Error in using
          tag library uri='/tags/struts-html' prefix='html': The Tag class 'org.apache.struts.taglib.html.BaseTag'
          has no setter method corresponding to TLD declared attribute 'server', (JSP 1.1
          spec, 5.4.1)
          I opened the BaseTag class from the struts jar and found the setter exists for
          the attribute 'server' of html tld. So does the property 'server'. The property
          'server' is a string and the parameter in the setter is a string. I read about
          the jspc errors in wls 8.1 about the setter parameter being of different type
          than the property. However, that is not the case here. I tried using both Sun's
          and BEA's jdk. None of them help. Btw, there is another attribute mentioned in
          the html tld, which is 'target'. The compiler doesn't complain yet about this.:(
          Also, I happened to compile other apps which have struts logic tags.
          My environment:
          OS: Win2k sp3
          WLS: 8.1 sp2
          JDK: Sun's 1.4.2 sp4 / Bea's 1.4.1 sp5 (tried both)
          Ant: 1.5.3 (I had an issue earlier with ant until I found that Bea officially
          without any mention supports only ant 1.5.3.)
          I would appreciate any help in this regard.
          Thanks,
          Abbas


          What version of Struts are you trying to use?
          Are you certain you're not encountering a different instance of that class in
          an unexpected location in your classpath?
          "Abbas" <[email protected]> wrote:
          >
          >Hi,
          >I am trying to compile jsps with weblogic.jspc, which use struts' html
          >tags. However,
          >the compilation fails with the following message:
          >
          >[java] Translation of /views/viewPageBody.jsp failed: (line 3): Error
          >in using
          >tag library uri='/tags/struts-html' prefix='html': The Tag class 'org.apache.struts.taglib.html.BaseTag'
          >has no setter method corresponding to TLD declared attribute 'server',
          >(JSP 1.1
          >spec, 5.4.1)
          >
          >I opened the BaseTag class from the struts jar and found the setter exists
          >for
          >the attribute 'server' of html tld. So does the property 'server'. The
          >property
          >'server' is a string and the parameter in the setter is a string. I read
          >about
          >the jspc errors in wls 8.1 about the setter parameter being of different
          >type
          >than the property. However, that is not the case here. I tried using
          >both Sun's
          >and BEA's jdk. None of them help. Btw, there is another attribute mentioned
          >in
          >the html tld, which is 'target'. The compiler doesn't complain yet about
          >this.:(
          >Also, I happened to compile other apps which have struts logic tags.
          >
          >
          >My environment:
          >OS: Win2k sp3
          >WLS: 8.1 sp2
          >JDK: Sun's 1.4.2 sp4 / Bea's 1.4.1 sp5 (tried both)
          >Ant: 1.5.3 (I had an issue earlier with ant until I found that Bea officially
          >without any mention supports only ant 1.5.3.)
          >
          >I would appreciate any help in this regard.
          >
          >Thanks,
          >
          >Abbas

Code webservices in WLS 6.1 sp2 using apache soap servlet

Similar Messages

Maybe you are looking for