The binding of FOP Servlet in BEA Weblogic

hello everybody,
I have a FOP Servelt after sample of Apache fop developed and afterwards as WAR-file (Web application) registered in prop.-file. with reboot of the server I get the following error message.
org.xml.sax.SAXParseException: Element "web-app" does not allow "servlet" here.
and
Received SAXParseException from Sun Parser at line 13, column -1: org.xml.sax.SAXParseException: Element "web-
app" does not allow "servlet" here.
perhaps someone can help me
thanks in advance
arman

Hi Xavi,
In "weblogic.xml" you need to write following kind of entry to make Context-Root changes...
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-web-app xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd">
<wls:weblogic-version>10.3.1</wls:weblogic-version>
<wls:context-root>TestContextRoot</wls:context-root>
</wls:weblogic-web-app>
To Make the Context-root Changes Dynamically(Without Editing the Deployment Descriptor Physically) Please refer to:
1). http://middlewaremagic.com/weblogic/?p=741 (For EAR Applications)
2). http://blogs.oracle.com/jamesbayer/2009/07 (James Bayer’s Blog For WAR Applications)
Thanks
Jay SenSharma
http://middlewaremagic.com/weblogic  (Middleware magic Is Here)

Similar Messages

  • How to install oracle xsql servlet on bea weblogic 5.1

              Hi there,
              I tried to install oracles xsql servlet (1.0.4.1) on bea weblogic 5.1 without
              any success.
              in weblogic.properties I started with:
              weblogic.httpd.webApp.xsql=c:\\weblogic\\myserver\\servletclasses\\xsql
              And in this dir I have WEB-INF with the following web.xml:
              <?xml version="1.0" encoding="ISO-8859-1"?>
              <!DOCTYPE web-app
              PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
              "http://java.sun.com/j2ee/dtds/web-app_2.2.dtd">
              <web-app>
              <servlet>
              <servlet-name>oracle-xsql-servlet</servlet-name>
              <servlet-class>oracle.xml.xsql.XSQLServlet</servlet-class>
              </servlet>
              <servlet-mapping>
              <servlet-name>oracle-xsql-servlet</servlet-name>
              <url-pattern> *.xsql </url-pattern>
              </servlet-mapping>
              </web-app>
              So the xsql extension is mapped to the named servlet which is found in a jar file
              contained in subdirectory lib.
              The problem is that the general mapping of *.xsql extension to specified class
              does not work at all. And there are no errors...
              Application server just presents me with the content of the xsql file instead
              of executing servlet whith the xsql file as input.
              Any ideas??
              Thanx in advance.
              JK
              

    What kind of problem do you have?
    If it's not connected with JDBC, you'd better post your question
    in webservices newsgroup.
    Regards,
    Slava Imeshev
    "leopld goess" <[email protected]> wrote in message
    news:[email protected]..
    hy out there.
    i've been working with apache soap on wl 5.1 for a while now, and
    everything seems to be working allright- as long as i don't try to
    install a servicepack, namely sp8 or sp10. if i do that, the entire
    soap service fails to deploy.
    any ideas...
    thanx
    leopold

  • Cannot run BEA WebLogic 8.1 SP 3 with JDK 1.6

    Hi,
    Im using BEA Weblogic 8.1 SP3 trying to run a sample where a Robot from Kapow Mashup Server is called from a WebService hosted in the server.
    The thing is that I keep getting a EJB Exception: : java.lang.NoClassDefFoundError: java/lang/StringBuilder (I attach the full exception below). I realised that by default the server uses the JDK which comes with the software (version 1.4) and that the class java.lang.StringBuilder is only available from JDK 1.5 onwards.
    I have JDK 1.6 in my system, so in WebLogic -> Tools -> Application Properties -> JDK Home, I set that folder but still same exception occurs.
    Through the Configuration Wizard I create a new “Basic WebLogic Server Domain” and in the step to configure the Java SDK I set the JDK 1.6 folder. However, when I try to start that server I get this error.
    JAVA Memory arguments: -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m
    WLS Start Mode=Development
    CLASSPATH=;C:\bea\WEBLOG~1\server\lib\weblogic_knex_patch.jar;C:\bea\WEBLOG~1\common\lib\log4j.jar;C:\bea\WEBLOG~1\server\lib\debugging.jar;C:\bea\WEBLOG~1\server\lib\knex.jar;C:\bea\WEBLOG~1\javelin\lib\javelin.jar;C:\bea\WEBLOG~1\server\lib\wlw-lang.jar;C:\ARCHIV~1\Java\JDK16~1.0_1\lib\tools.jar;C:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;C:\bea\WEBLOG~1\server\lib\weblogic.jar;C:\bea\WEBLOG~1\server\lib\ant\ant.jar;C:\ARCHIV~1\Java\JDK16~1.0_1\jre\lib\rt.jar;;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbserver44.jar;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient+ssl.jar;C:\bea\WEBLOG~1\server\lib\xbean.jar;C:\bea\WEBLOG~1\server\lib\wlxbean.jar;C:\bea\WEBLOG~1\server\lib\xqrl.jar;C:\bea\WEBLOG~1\server\lib\netui\netui-compiler.jar;C:\bea\WEBLOG~1\server\lib\wli.jar;C:\bea\WEBLOG~1\server\lib\fop.jar;C:\bea\WEBLOG~1\integration\adapters\sample\lib\sample-eis.jar;
    PATH=C:\bea\WEBLOG~1\server\bin;C:\ARCHIV~1\Java\JDK16~1.0_1\jre\bin;C:\ARCHIV~1\Java\JDK16~1.0_1\bin;C:\Archivos de programa\PC Connectivity Solution\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\Intel\DMIX;C:\Archivos de programa\HPQ\IAM\bin;C:\Archivos de programa\Java\jdk1.6.0_10\bin;C:\eclipseJava\plugins\org.apache.ant_1.7.0.v200803061910\bin;C:\Archivos de programa\Archivos comunes\Adobe\AGL;c:\Archivos de programa\Microsoft SQL Server\90\Tools\binn\;c:\matlab6p5\bin\win32;C:\Nokia\Update_Manager\bin;C:\Archivos de programa\QuickTime\QTSystem\;C:\Sun\jwsdp-2.0\jwsdp-shared\bin;C:\Archivos de programa\Kapow Mashup Server 6.3\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\Intel\DMIX;C:\Archivos de programa\HPQ\IAM\bin;C:\Archivos de programa\Java\jdk1.6.0_10\bin;C:\eclipseJava\plugins\org.apache.ant_1.7.0.v200803061910\bin;C:\bea\WEBLOG~1\server\bin\oci920_8
    * To start WebLogic Server, use a username and *
    === Debugging ===
    This window is necessary for debugging code using WebLogic Workshop
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http:\\hostname:port\console *
    starting weblogic with Java version:
    Listening for transport dt_socket at address: 8453
    Starting WLS with line:
    C:\ARCHIV~1\Java\JDK16~1.0_1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -Dplatform.home=C:\bea\WEBLOG~1 -Dwls.home=C:\bea\WEBLOG~1\server -Dwli.home=C:\bea\WEBLOG~1\integration -Dlog4j.configuration=file:C:\bea\WEBLOG~1\common\lib\workshopLogCfg.xml -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.Name=myserver -Djava.security.policy=C:\bea\WEBLOG~1\server\lib\weblogic.policy weblogic.Server
    Listening for transport dt_socket at address: 8453
    <27-abr-2009 11H22' CEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 11.0-b15 from Sun Microsystems Inc.>
    <27-abr-2009 11H22' CEST> <Info> <Configuration Management> <BEA-150016> <This server is being started as the administration server.>
    <27-abr-2009 11H22' CEST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Integration 8.1 SP3 Wed Jun 30 14:05:38 PDT 2004 405464>
    Stopping the Weblogic Workshop debugger...
    Debugger Stopped.
    Stopping Pointbase server...
    Pointbase server stopped.
    If I modify the settings of this new domain an pick a BEA Supplied SDKs, everything works just fine.
    Someone can give a hand on that? It seems like Bea WebLogic 8.1 and JDK 1.6 are not compatible. Completely stacked here.
    Regards.
    Full Exception
    EJB Exception: : java.lang.NoClassDefFoundError: java/lang/StringBuilder
    at robosuite.wizard.jws5a1dbbea00000001.ApiKapowIN.toString(ApiKapowIN.java:141)
    at java.lang.String.valueOf(String.java:2131)
    at java.lang.StringBuffer.append(StringBuffer.java:370)
    at com.bea.wlw.runtime.core.context.WlwThreadContext.logInvoke(WlwThreadContext.java:363)
    at com.bea.wlw.runtime.core.context.WlwThreadContext.startInvocation(WlwThreadContext.java:608)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:414)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:248)
    at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:198)
    at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:103)
    at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:153)
    at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:62)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:160)
    at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:100)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:161)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.dispatch(Dispatcher.java:49)
    at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.executePostRequest(HttpServerHelper.java:713)
    at com.bea.wlw.runtime.core.dispatcher.HttpServer.doPost(HttpServer.java:49)
    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: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:6456)
    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)

    Even if it is a very naive question but I just cannot get it worked, what do you mean by using jdk 1.5 on client side?
    I guess client side is completely out of WLS so the jdk to be used on the client side is not set in the environment.
    However, the Exception Im getting is on the server side, when it tries to run the code automatically generated from Kapow Mashup Server 6.3. That code is embedded in a jar file, but it seems it makes a call to the java.lang.StringBuilder class which as said before, it is only available from jdk 1.5 onwards.
    Should I contact Kapow Mashup Server support to see how the sample code is generated or I am missing something?
    Regards.

  • XSQL und BEA Weblogic  ERROR:XSQL-013

    We develop an web-application using XSQL to generate XML, which is further transformed via XSL to HTML or PDF.
    As IDE we use JDeveloper 9.0.3.1.
    Running and debugging in JDeveloper works fine.
    We deploy the application as war-file on bea weblogic 7.2.
    When starting the xsql-servlet / calling the xsql file we get the following error:
    Oracle XSQL Servlet Page Processor 9.0.3.0.0 (Production)
    XSQL-013: XSQL Page URI is null or has an invalid format.
    XSQLConfig is located in:
    WEB-INF\classes\XSQLConfig.xml</li>
    XSQLConfig remains untouched and holds the right connection (OCI)
    <connection name="KimOci">
    <username>...</username>
    <password>...</password>
    <dburl>jdbc:oracle:oci8:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=...)(PORT=...)))(CONNECT_DATA=(SID=...)))</dburl>
    <driver>oracle.jdbc.driver.OracleDriver</driver>
    </connection>
    XSQL-File starts with
    <?xml version = "1.0" encoding = "ISO-8859-1"?>
    <page xmlns:xsql="urn:oracle-xsql" connection="KimOci">
    <xsql:include-request-params/>
    <xsql:include-param name="ImageUrl"/>
    <xsql:include-param name="BaseUrl"/>
    <xsql:include-param name="LocalUrl"/>
    <xsql:query max-rows="-1" null-indicator="no" tag-case="lower" rowset-element="global" row-element="date">
    select ...
    Whats wrong or missing?
    Thanks

    Trying to check whats going on within the XSQL-Prozessor we tried the programmatic approach.
    First step is to call XSQL from within an action /jsp .
    <%
    String baseUrl = request.getScheme()
    + "://"
    + request.getServerName()
    + ":"
    + request.getServerPort()
    //+ "/"
    + request.getContextPath()
    + "/"
    URL pageUrl = new URL(baseUrl+"report/untitled2.xsql");
    XSQLRequest req = new XSQLRequest(pageUrl);
    PrintWriter of = new PrintWriter( new FileOutputStream("./report.xml"));
    PrintWriter ef = new PrintWriter( response.getOutputStream());
    Hashtable params = new Hashtable(0);
    req.process(params, of, ef );
    %>
    But still there is an error.
    This time we got:
    Oracle XSQL Programmatic Page Processor 9.0.3.0.0 (Production) XSQL-005: XSQL page is not well-formed. XML parse error at line 2, char 1 Expected 'EOF'
    The code of untitled2.xsql
    <?xml version = "1.0" encoding = "ISO-8859-1"?>
    <page xmlns:xsql="urn:oracle-xsql" connection="KimOci">
    <amen>leer</amen>
    </page>

  • Reg: JAXM support on BEA Weblogic 7.0

    BACKGROUND: I am developing a Point-to-point SOAP sender/receiver application.
    A client sends a SOAP message directly to the ultimate recipient
    using a SOAPConnection object. Here client to the intended recipient
    rather than to a messaging provider. Therefore, when the application
    sends a message, the message goes directly to the intended recipient.
    This kind of SOAP message exchange uses the APIs in the javax.xml.soap package.
    SOAPConnection (and its related classes) is a pure library implementation
    that lets you send SOAP messages directly to a remote party.
    CODE:
    try
    String endpoint="http://localhost:7001/WholesaleVendor/wsv";
    URLEndpoint urlEndpoint= new URLEndpoint(endpoint);
    SOAPConnectionFactory soapConnFct = SOAPConnectionFactory.newInstance();
    SOAPConnection soapConnection = soapConnFct.createConnection();
    MessageFactory messageFactory = MessageFactory.newInstance();
    SOAPMessage requestSoapMsg = messageFactory.createMessage();
    //REST OF THE CODE FOLLOWS
    PROBLEM: It works on Sun's JWSDP 1.0. Howerver, on BEA Weblogic 7.0, I get error.
    The error is in the following line:
    ============================
    javax.xml.soap.SOAPException: Unable to create SOAP connection factory:
    Provider com.sun.xml.messaging.client.p2p.HttpSOAPConnectionFactory not found
    at javax.xml.soap.SOAPConnectionFactory.newInstance(Unknown Source)
    at supermarket.InventoryBuilder.placePOOnWholeSaleVendor(InventoryBuilder.java:74)
    ============================
    QUERY: Is Point-to-point JAXM communication supported on BEA Weblogic 7.0?
    If not, what is alternative?
    What is the scope of JAXM support on BEA Weblogic 7.0?
    Thanking you in anticipation.
    Sachin Raverkar

    We have not implemented JAXM, nor has JAXM been included in J2EE 1.4.
    JAXM has not gotten much traction in the marketplace, and we have
    focused instead on JAX-RPC, which is available in 7.0 and 8.1. From
    your description, it sounds like JAX-RPC would meet your requirements.
    Note that we do support the SAAJ APIs, which were previously part of JAXM.
    -Don
    Sachin Raverkar wrote:
    BACKGROUND: I am developing a Point-to-point SOAP sender/receiver application.
    A client sends a SOAP message directly to the ultimate recipient
    using a SOAPConnection object. Here client to the intended recipient
    rather than to a messaging provider. Therefore, when the application
    sends a message, the message goes directly to the intended recipient.
    This kind of SOAP message exchange uses the APIs in the javax.xml.soap package.
    SOAPConnection (and its related classes) is a pure library implementation
    that lets you send SOAP messages directly to a remote party.
    CODE:
    try
    String endpoint="http://localhost:7001/WholesaleVendor/wsv";
    URLEndpoint urlEndpoint= new URLEndpoint(endpoint);
    SOAPConnectionFactory soapConnFct = SOAPConnectionFactory.newInstance();
    SOAPConnection soapConnection = soapConnFct.createConnection();
    MessageFactory messageFactory = MessageFactory.newInstance();
    SOAPMessage requestSoapMsg = messageFactory.createMessage();
    //REST OF THE CODE FOLLOWS
    PROBLEM: It works on Sun's JWSDP 1.0. Howerver, on BEA Weblogic 7.0, I get error.
    The error is in the following line:
    ============================
    javax.xml.soap.SOAPException: Unable to create SOAP connection factory:
    Provider com.sun.xml.messaging.client.p2p.HttpSOAPConnectionFactory not found
    at javax.xml.soap.SOAPConnectionFactory.newInstance(Unknown Source)
    at supermarket.InventoryBuilder.placePOOnWholeSaleVendor(InventoryBuilder.java:74)
    ============================
    QUERY: Is Point-to-point JAXM communication supported on BEA Weblogic 7.0?
    If not, what is alternative?
    What is the scope of JAXM support on BEA Weblogic 7.0?
    Thanking you in anticipation.
    Sachin Raverkar

  • Welcome to the BEA WebLogic Server Version 6.0 Beta Program!

    Welcome to the BEA WebLogic Server Version 6.0 Beta Program!
    We are very excited about this beta program and appreciate your
    participation. In the past, our public betas have been very well received
    by our developer community. So, we have once again organized a public beta
    program to enable everyone to preview our latest release.
    We do ask that you follow a few guidelines:
    -- There will be no voice, e-mail, or fax support for this beta through the
    technical support organization. All questions, bug reports, or comments on
    the beta program should be directed to to the WebLogic beta newsgroups at
    news://newsgroups.bea.com. These newsgroups are:
    weblogic.developer.interest.60beta.transaction
    weblogic.support.install.60beta
    weblogic.developer.interest.60beta.ejb
    weblogic.developer.interest.60beta.clustering
    weblogic.developer.interest.60beta.security
    weblogic.developer.interest.60beta.jdbc
    weblogic.developer.interest.60beta.jms
    weblogic.developer.interest.60beta.performance
    weblogic.developer.interest.60beta.misc
    weblogic.developer.interest.60beta.servlet
    weblogic.developer.interest.60beta.jsp
    weblogic.developer.interest.60beta.tools
    weblogic.developer.interest.60beta.rmi-iiop
    weblogic.developer.interest.60beta.management
    weblogic.developer.interest.60beta.management.console
    weblogic.developer.interest.60beta.management.general_and_jmx
    weblogic.developer.interest.60beta.internationalization
    weblogic.developer.interest.60beta.xml
    weblogic.developer.interest.60beta.jndi
    weblogic.developer.interest.60beta.documentation
    weblogic.developer.interest.60beta.javamail
    -- Please remember that this release is currently beta code. This means that
    it should not be put into production deployments until the final release
    occurs.
    -- It is very likely that this release will contain bugs and errors. This is
    the nature of beta code. Please the patient with us as we do our best to fix
    any problems that we find. We will do our absolute best to make sure that
    your issues are addressed as soon as possible.
    -- Please do not post any issues relevant to the beta on the standard
    newsgroups also available at news://newsgroups.bea.com.
    -- Please use the newsgroup for all communication and do not contact any BEA
    employees directly. They have been instructed to direct you to comment only
    via the newsgroup.
    -- Please review previous posts in the newsgroups before posting. If you
    locate a bug or need to ask a question, it is very likely that it will have
    been asked before.
    -- Please do not post on the newsgroup using hostile or profane language.
    Inappropriate posts will be removed and offenders will be blocked from the
    beta program.
    Thank you again for your support and participation. We very much appreciate
    all that you will be doing to make this release of the BEA WebLogic Server
    as great as possible.
    Michael Girdley
    BEA Systems Inc

    Welcome to the BEA WebLogic Server Version 6.0 Beta Program!
    We are very excited about this beta program and appreciate your
    participation. In the past, our public betas have been very well received
    by our developer community. So, we have once again organized a public beta
    program to enable everyone to preview our latest release.
    We do ask that you follow a few guidelines:
    -- There will be no voice, e-mail, or fax support for this beta through the
    technical support organization. All questions, bug reports, or comments on
    the beta program should be directed to to the WebLogic beta newsgroups at
    news://newsgroups.bea.com. These newsgroups are:
    weblogic.developer.interest.60beta.transaction
    weblogic.support.install.60beta
    weblogic.developer.interest.60beta.ejb
    weblogic.developer.interest.60beta.clustering
    weblogic.developer.interest.60beta.security
    weblogic.developer.interest.60beta.jdbc
    weblogic.developer.interest.60beta.jms
    weblogic.developer.interest.60beta.performance
    weblogic.developer.interest.60beta.misc
    weblogic.developer.interest.60beta.servlet
    weblogic.developer.interest.60beta.jsp
    weblogic.developer.interest.60beta.tools
    weblogic.developer.interest.60beta.rmi-iiop
    weblogic.developer.interest.60beta.management
    weblogic.developer.interest.60beta.management.console
    weblogic.developer.interest.60beta.management.general_and_jmx
    weblogic.developer.interest.60beta.internationalization
    weblogic.developer.interest.60beta.xml
    weblogic.developer.interest.60beta.jndi
    weblogic.developer.interest.60beta.documentation
    weblogic.developer.interest.60beta.javamail
    -- Please remember that this release is currently beta code. This means that
    it should not be put into production deployments until the final release
    occurs.
    -- It is very likely that this release will contain bugs and errors. This is
    the nature of beta code. Please the patient with us as we do our best to fix
    any problems that we find. We will do our absolute best to make sure that
    your issues are addressed as soon as possible.
    -- Please do not post any issues relevant to the beta on the standard
    newsgroups also available at news://newsgroups.bea.com.
    -- Please use the newsgroup for all communication and do not contact any BEA
    employees directly. They have been instructed to direct you to comment only
    via the newsgroup.
    -- Please review previous posts in the newsgroups before posting. If you
    locate a bug or need to ask a question, it is very likely that it will have
    been asked before.
    -- Please do not post on the newsgroup using hostile or profane language.
    Inappropriate posts will be removed and offenders will be blocked from the
    beta program.
    Thank you again for your support and participation. We very much appreciate
    all that you will be doing to make this release of the BEA WebLogic Server
    as great as possible.
    Michael Girdley
    BEA Systems Inc

  • Support for the creation of a new BEA WebLogic Application Server v10.3

    To All,
    After downloading and installing the Enterprise Pack for Eclipse (Ganymede: http://download.oracle.com/otn_software/oepe/ganymede) I attempted to create a new BEA WebLogic 10.3 server - since that is the version of the application server that I have installed on my machine.
    I went to create the new server and selected "BEA WebLogic Server v10.0", since there was no option to select a WebLogic 10.3 server. I selected as the WebLogic Home directory "D:\BEA_HOME\wlserver_10.3" and received the error message: "The path "D:\BEA_HOME\wlserver_10.3" contains the wrong version of WebLogic Server. Expected version 10.0. Found version 10.3."
    Is there some way that I can create a new WLS v10.3 in Eclipse Ganymede? Do I need to download an additional plugin?
    Thanks in advance for your help on this,
    John Livingstone

    Look for WLS 10.3 under Oracle rather than BEA group.
    Konstantin

  • How to install Oracle BPEL Process Manager with the BEA WebLogic

    Hi ,
    I will install Oracle BPEL Process Manager with BEA WebLogic 9.2(MP2). I have download orabpel_10133_WebLogic.zip ,then Modify the following mandatory installation properties in the orabpel_10133_WebLogic\bpelDomain.properties file:
    # BEA_HOME is the path where Weblogic is Installed
    BEA_HOME=/opt/bea
    # JAVA_HOME is the path of jdk folder inside your weblogic
    JAVA_HOME=/opt/bea/jrockit90_150_10
    # DOMAIN_HOME is the path where you wish to create your domain called BPELDomain
    DOMAIN_HOME=/opt/bea/user_projects/domains
    # APPS_HOME is the path where you wish to copy your applications and adapters that are required for oracleBPELServer
    APPS_HOME=/opt/bea/user_projects/apps
    # BEA_HOME is the path where BPEL PM is Installed
    BPEL_HOME=/home/oracle/bpel/product/10.1.3.1/OraBPEL_1/bpel
    # DRIVER_TYPE is the datasource class that installable use to create a datasources for oracleBPELServer
    DRIVER_TYPE=oracle.jdbc.xa.client.OracleXADataSource
    # DB_URL is the url to connect to orabpel schema
    DB_URL=jdbc:oracle:thin:@16.157.134.17:1521:orcl
    # DB_USER is the user Id for orabpel shema in database
    DB_USER=ORABPEL
    #DB_PASSWORD is the password for orabpel schema in database
    DB_PASSWORD=bpel
    #BPEL_SERVER_NAME is the server i.e. to be created under BPELDomain
    BPEL_SERVER_NAME=oracleBPELServer
    #PROXY_HOST is the Host name of the proxy server
    PROXY_HOST=www-proxy.us.oracle.com
    #PROXY_HOST=
    #PROXY_PORT is the Port where the proxy server is running
    PROXY_PORT=80
    #PROXY_PORT=
    #NON_PROXY_HOST is the list of non proxy hosts that are divided by a | symbol
    #NON_PROXY_HOST=*.oracle.com|*.oraclecorp.com|localhost|127.0.0.1|stbbn10|stbbn10.us.oracle.com
    NON_PROXY_HOST=*.oracle.com|*.oraclecorp.com|localhost|127.0.0.1|stbbn10|stbbn10.us.oracle.com|16.157.134.135
    When I run the setup.sh , it will report
    BUILD FAILED
    /opt/software/WL_Installables/build.xml:131: Traceback (innermost last):
    File "./wl_scripts/bpelDomain.py", line 22, in ?
    File "./wl_scripts/createGroupsAndUsers.py", line 4, in ?
    weblogic.management.utils.AlreadyExistsException: [Security:090267]Group BpelGroup
    Actully ,there is no BpelGroup in Weblogic. Does anybody know how to solve it ?

    MAke sure you have not set ANY environment variable related to Oracle / BEA / Java / LD_library path. Use the following script to unset / set the initial settings:
    #!/bin/sh
    unset ORACLE_BASE ORACLE_HOME ORACLE_SID ORACLE_TERM
    unset LD_LIBRARY_PATH LD_LIBRARY_PATH_64
    unset CLASSPATH JAVA_HOME
    export PATH=.:/usr/sbin:/usr/bin:/usr/local/bin:/opt/VRTS/bin
    export BEA_HOME=/appl/oracle/products/9.2/weblogic
    Marc
    http://orasoa.blogspot.com

  • What are the limitations of AJAX in BEA Weblogic 10.2 ?

    Hi All,
    I am wondering if some one could tell/summaries what are the limitations of AJAX in BEA weblogic portal 10.2 ??

    Please reask this question in the WebLogic Portal forum:
    WebLogic Portal
    I think you'll need to be more specific as well. Are you referring to portlet development, in which the portlet uses a javascript library, drag/drop functionality in Dynamic Visitor Tools, etc?
    http://edocs.bea.com/wlp/docs102/clientdev/ria.html#wp1008891

  • I need to download the server runtime for BEA WEBLOGIC server

    Hi ^^,
    I am trying to create a web project in Eclipse WTP europa. I do not have the bea weblogic server installed on my desktop. My organization has issues running it locally. I need to first create a project and then create a war and then deploy it on server.
    I am going through the tutorial at the following website:
    http://www.eclipse.org/webtools/community/tutorials/BuildJ2EEWebApp/BuildJ2EEWebApp.html
    It says "To do this tutorial you will need a server runtime that is supported by WTP"
    Also "During web application development, we will need a server runtime environment to test, debug and run our project".
    Hence I need the link where I can download the server runtime for bea weblogic server.
    T&R,
    Prashant

    Crossposted over all places:
    [http://forums.sun.com/thread.jspa?threadID=5347690]
    [http://forums.sun.com/thread.jspa?threadID=5348001]
    [http://forums.sun.com/thread.jspa?threadID=5348002]
    Don't crosspost. It's very rude.

  • Is the 11.1.1.2 software compatible with BEA WebLogic 10.3?

    Hi,
    Does anyone know, is Oracle EPM version 11.1.1.2 compatible with BEA WebLogic 10.3? I know the recommended version is 9.2 MP3 for Windows 32 bit.
    Do we need to get seperate license for WebLogic or is it included in this EPM software bundle?
    Thanks for your answers in advance..!

    Not sure about the licensing, its best to ask someone at Oracle, but I believe when you when automatic deploy 11.1.1.2 apps to Oracle10gR3 Application Server, it is actually referring to the Oracle Weblogic 10.3 Application Server, not the old Oracle (OAS) 10G Application Server, so it should work. You can also deploy to Weblogic 9.2 and IBM Webshpere automatically. I believe all other application servers may still be compatible but require a manual deployment.
    Regards,
    Imran

  • How to speed up the BEA weblogic workshop perforkmance?

    Hi,
    Does anybody knows how to speed up the BEA weblogic workshop,as it consumes heavy memory.
    I've configured the settings in workshop.cfg file and set the maximum memory size as 1024m midium size 516m and minimum size as 256m
    and deleted all the files from .workshop directory before open up the workshop file.
    But it hanging up the system when i opened the worshop file after some time. what could be the problem . i am using 2GB ram size

    Hi Vishnu,
    I agree this can also be one of the reason for the performance. There is Trend Micro Office Scan client installed on my system, but i couldn't not do any settings ,as it is disabled by sys admin .
    however, i removed all the scanning processes from task manager and set the high priority for the java process! still, no improvement. There are only few jpd files not even 500kb size, but when i open them, weblogic cried and utilized lots lots of memory! :-(
    I am afraid to open the weblogic which had jpd files,as it hanged my whole system, unable to perform any other tasks!

  • What's the differenct in the BEA WebLogic Server Products.

    hello,
    can anyone tell me the difference between 'BEA WebLogic Server Advantage Edition' and 'A WebLogic Server Premium Edition'?
    thanks.

    Premium supports clustering of servers, web sessions, jms and ejb's.
    Advantage edition only licenses non-clustered servers.

  • Is the Bea weblogic workshop IDE develop use the Java?

    is the Bea weblogic workshop IDE develop use the Java?
    beautiful UI.I like it.
    but i think it develop use C#!

    Dear carls:
    Thank you very much.I'm look forward to the day it is released!
    "Carl Sjogreen" <[email protected]> wrote:
    Thanks for the compliment!
    At the current time, BEA is not planning to release the workshop look and
    feel to third parties, or make it available via open source. However, its
    all standard swing code -- just a lot of custom drawn controls!
    In a later release we may open up these libraries to partners who want to
    work closely with the Workshop environment.
    -Carl Sjogreen, Product Manager
    "andiyang" <[email protected]> wrote in message
    news:3cff0bc5$[email protected]..
    Dear Anurag Pareek:
    Thank u very much,I want to know to do it?is it Open and standard ?where has develop
    resource about it?
    thank u very much!
    andiyang
    "Anurag Pareek" <[email protected]> wrote:
    Hi,
    As beautiful as it looks, it has been developed entirely using Java Swing
    components:-)
    Regards,
    Anurag
    Workshop Support
    "andiyang" <[email protected]> wrote in message
    news:3cfd727d$[email protected]..
    is the Bea weblogic workshop IDE develop use the Java?
    beautiful UI.I like it.
    but i think it develop use C#!

  • Problem in calling a web service hosted on tomcat from BEA WebLogic portal

    Hi,
    I have a wsdl file for my web service which is hosted on apache tomcat 5.5(running on port : 8080). The contents of the wsdl file are-
    *<?xml version="1.0" encoding="UTF-8"?>*
    *<wsdl:definitions targetNamespace="http://soa.tutorials.serg.edu" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://soa.tutorials.serg.edu" xmlns:intf="http://soa.tutorials.serg.edu" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">*
    *<!--WSDL created by Apache Axis version: 1.4*
    Built on Apr 22, 2006 (06:55:48 PDT)-->
    *<wsdl:types>*
    *<schema elementFormDefault="qualified" targetNamespace="http://soa.tutorials.serg.edu" xmlns="http://www.w3.org/2001/XMLSchema">*
    *<element name="getNums">*
    *<complexType>*
    *<sequence>*
    *<element name="n" type="xsd:int"/>*
    *<element name="m" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *<element name="getNumsResponse">*
    *<complexType>*
    *<sequence>*
    *<element maxOccurs="unbounded" name="getNumsReturn" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *<element name="getNums2">*
    *<complexType>*
    *<sequence>*
    *<element name="n" type="xsd:int"/>*
    *<element name="m" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *<element name="getNums2Response">*
    *<complexType>*
    *<sequence>*
    *<element maxOccurs="unbounded" name="getNums2Return" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *</schema>*
    *</wsdl:types>*
    *<wsdl:message name="getNums2Request">*
    *<wsdl:part element="impl:getNums2" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:message name="getNumsRequest">*
    *<wsdl:part element="impl:getNums" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:message name="getNums2Response">*
    *<wsdl:part element="impl:getNums2Response" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:message name="getNumsResponse">*
    *<wsdl:part element="impl:getNumsResponse" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:portType name="Echo">*
    *<wsdl:operation name="getNums">*
    *<wsdl:input message="impl:getNumsRequest" name="getNumsRequest"/>*
    *<wsdl:output message="impl:getNumsResponse" name="getNumsResponse"/>*
    *</wsdl:operation>*
    *<wsdl:operation name="getNums2">*
    *<wsdl:input message="impl:getNums2Request" name="getNums2Request"/>*
    *<wsdl:output message="impl:getNums2Response" name="getNums2Response"/>*
    *</wsdl:operation>*
    *</wsdl:portType>*
    *<wsdl:binding name="EchoSoapBinding" type="impl:Echo">*
    *<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>*
    *<wsdl:operation name="getNums">*
    *<wsdlsoap:operation soapAction=""/>*
    *<wsdl:input name="getNumsRequest">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:input>*
    *<wsdl:output name="getNumsResponse">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:output>*
    *</wsdl:operation>*
    *<wsdl:operation name="getNums2">*
    *<wsdlsoap:operation soapAction=""/>*
    *<wsdl:input name="getNums2Request">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:input>*
    *<wsdl:output name="getNums2Response">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:output>*
    *</wsdl:operation>*
    *</wsdl:binding>*
    *<wsdl:service name="EchoService">*
    *<wsdl:port binding="impl:EchoSoapBinding" name="Echo">*
    *<wsdlsoap:address location="http://localhost:8080/SOATest/services/Echo"/>*
    *</wsdl:port>*
    *</wsdl:service>*
    *</wsdl:definitions>*
    I created a client from the above wsdl file using ClientGen wizard in WebLogic. This client contains the follwoing classes-
    Echo.java
    EchoService.java
    EchoService_Impl.java
    Echo_Stub.java
    I created a JSP portlet and the jsp content of it is-
    String url = "http://localhost:8080/SOATest/services/Echo";
    Echo echo = new EchoService_Impl(url).getEcho();
    getNumsResponse = echo.getNums(getNums);
    I tried to call that web service from BEA weblogic portal through a JSP potlet. I got an error saying -
    *<An exception [javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element] was thrown while rendering the content at [TestEcho.jsp].*
    *javax.servlet.ServletException: javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.servlet.jsp.PageContextImpl.handlePageException(PageContextImpl.java:420)*
    *     at jsp_servlet.__testecho._jspService(__testecho.java:112)*
    *     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)*
    *     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)*
    *     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)*
    *     Truncated. see log file for complete stacktrace*
    *javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.wsee.jaxrpc.ServiceImpl.throwServiceException(ServiceImpl.java:174)*
    *     at weblogic.wsee.jaxrpc.ServiceImpl.loadWsdlDefinition(ServiceImpl.java:485)*
    *     at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:119)*
    *     at edu.serg.tutorials.soa.EchoService_Impl.<init>(Unknown Source)*
    *     at edu.serg.tutorials.soa.EchoService_Impl.<init>(Unknown Source)*
    *     Truncated. see log file for complete stacktrace*
    *weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:313)*
    *     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:405)*
    *     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:391)*
    *     at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:79)*
    *     at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:66)*
    *     Truncated. see log file for complete stacktrace*
    *java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:38)*
    *     at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:122)*
    *     at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)*
    *     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)*
    *     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:405)*
    *     Truncated. see log file for complete stacktrace*
    *javax.xml.stream.XMLStreamException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:206)*
    *     at weblogic.xml.stax.XMLStreamReaderBase.next(XMLStreamReaderBase.java:237)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:112)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:73)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:35)*
    *     Truncated. see log file for complete stacktrace*
    *Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.xml.babel.baseparser.BaseParser.parseProlog(BaseParser.java:417)*
    *     at weblogic.xml.babel.baseparser.BaseParser.parseSome(BaseParser.java:328)*
    *     at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:195)*
    *     at weblogic.xml.stax.XMLStreamReaderBase.next(XMLStreamReaderBase.java:237)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:112)*
    *     Truncated. see log file for complete stacktrace*
    My web service is using soap binding. I have tested it with eclipse and other tools also. It is working well and good. But when I tried to call a web service which is created and hosted on WebLogic server(running on port : 7001), I got the correct output.
    Can anyone help me out in calling a web service hosted on different server from WebLogic server.
    Thanks in advance,
    Tiijnar
    Edited by: user8715057 on Aug 13, 2009 1:11 AM

    Hi
    1. The way you are invoking the WebService deployed on Tomcat server is looks suspicious. It may be valid by adding extra ?wsdl etc into the url, but still I have not seen this way to invoke the webservice.
    2. So you used Weblogic ant task to generate client JARs by giving this WSDL. So looks like it generated the 4 classes (.java) and in addition any other classes for Request/Response xml objects.
    3. Look at the source code of EchoService.java. It should have one default empty constructor. Internally it uses the default wsdl defined in this class. You will see another constructor that takes WSDL URL as one of the parameters (QName) etc. Echo.java is the class corresponding to the Port. In the same EchoService you should see an instance method like getEcho() something like that. This Echo.java class will have methods for all the Operations defined on this Port. So the standard code snippet we use most of the times will be like this:
    EchoService myEchoService = new EchoService(); // Default it uses WSDL deployed on Tomcat at localhost:8080
    Echo myEchoPort = myEchoService.getEchoPort(); // Something along these lines.
    myEchoPort.xxxYYY(); // NOW this is the operation name that takes the input parameters and returns outputs defined as per the WSDL defintions. If the Input and Outputs are complex xml types, it will have corresponing .JAVA files with setters and getters.
    Now if this WebService is deployed on same Tomcat but on different machine or different port, you just give the full WSDL URL with that host and port in the constructor for new EchoService(...). You may need to instantiate QName object. But look at the methods generated in EchoService.java class.
    The way you are using with Impl and Stubs class may also work. I am not much famiiar with this APIs apporach. Still look at the methods generated in these classes.
    Also if you latest Sun JDK 1.6, it also has one command like wsimport. Infact if you install WLS 10.3 with Sun JDK, it should have C:\beawlp103\jdk160_05\bin\wsimport command. This will also generate client jar given a WSDL URL.
    Thanks
    Ravi Jegga

Maybe you are looking for