Tomcat to Weblogic

Hi there,
I really need help here. Trying to deploy a tomcat web application on Weblogic, and didn't work.
What I did:
1, upload the webapp folder of the web application, onto Weblogic / user_projects/ domain / base_domain
2, login into Console, find the webapp folder, and deploy it in the AdminServer
3, try browse the web application, and got all different kind of errors (Unable to open database connection, or Unable to compile the stylesheet, or Sytax errors..)
I have written up a simple mysql test servlet and deploy it and test it and it works......
I also got whole bunch of errors when AdminServer starts up:
Ignoring: unable to load class:java.lang.ClassNotFoundException: com.pageseeder.review.NewReviewExplorer at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)
When processing WebService module 'webapp'. Failed to load servlet Class: com.pageseeder.review.ReviewSpace
Really out of my mind, first time using Weblogic, and have no idea where to start debug this issue.
Please any ideas? I can open the server port and give the login/pwd if needed.
Thanks!
cheney

Hi Jay,
This is a great information and really points me to a right direction. However, things are always not going smooth as I imagine, once I put in:
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
into weblogic.xml, my application failed to load. Here is what I got from screen:
<May 5, 2010 10:06:16 AM EST> <Error> <HTTP> <BEA-101216> <Servlet: "com.pageseeder.layout.UIMappingServlet" failed to preload on startup in Web application: "webapp".
java.lang.LinkageError: loader constraint violation: loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) previously initiated loading for a different type with name "org/xml/sax/XMLReader"
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:344)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:301)
I have no idea about this error.....

Similar Messages

  • Migration from tomcat to weblogic 10.3.2

    Hi,
    I am developing a web application, its a servlet which basically acts as a front end for a web service,
    and I use CXF for the web service client, tested under a development tomcat instance and worked fine.
    I have the spring framework and the rest jars in the lib:
    wsdl4j-1.6.1.jar
    wss4j-1.5.8.jar
    jaxb-api-2.0.jar
    cxf-2.2.3.jar
    while I try to migrate to weblogic 10.3.2 follow the change as in
    http://cxf.apache.org/docs/application-server-specific-configuration-guide.html#ApplicationServerSpecificConfigurationGuide-WebLogic
    Then I got the exception:
    java.lang.IncompatibleClassChangeError: Class com.ibm.wsdl.DefinitionImpl does not implement the requested interface javax.wsdl.extensions.AttributeExtensible
    at org.apache.cxf.wsdl11.WSDLServiceBuilder.copyExtensionAttributes(WSDLServiceBuilder.java:137)
    at org.apache.cxf.wsdl11.WSDLServiceBuilder.buildServices(WSDLServiceBuilder.java:277)
    I have been research on this problem for a while, found some posts from experts like Dan on Nable...
    but I still didn't get it, could anyone help on this.
    Joelking

    can u let us know how did you resolve this?

  • Tomcat Vs Weblogic Vs JBOSS

    I planned to start developing server application where the number of concurrent request to the container will be high, so which server I can choose. Can anyone diffentiate all J2EE servers.
    Thank you

    paste from other forum
    Tomacat is a webserver that can handels only HTTP protocol,,,while Weblogic is an applicatin server that handels FTP and HTTP both
    Weblogic can run EJBs but Tomcat cant
    You can do database connection pooling in Weblogic by usinng JNDI inteface but in tomcat you cant do so ,,,some versions of tomcat also supports connection pooling ,but not all
    if u want to get your application run having EJBs and servlets as well as JSP
    u ave to use both
    App server and webserver
    Weblogic never get tomcat bundeled in it
    but app server Jboss have tomcat bundeled in it

  • Context.xml for Tomcat using Weblogic JMS

    Hello,
              has anyone succeeded in getting Tomcat to use a queue hosted by Weblogic? If so, could you please post a snippet of your context.xml with the <Resource>... sections appropriate? My last attempt drowned in a sea of bizarre security exceptions and hasn't been seen since.
              Thanks,
              Richard

    Tom,
              I'll see what happens when I move things about, but really, there's a difference here. One of the issues here is that Tomcat needs a class that implements the ReferenceFactory interface for its configuration. I can't find such a class in the Weblogic docs, but I might have it all wrong or be looking in the wrong place. Hence, my question.
              The weblogic jar is not in the Tomcat classpath, it's in the WEB-INF/lib directory of the war file I'm working with.

  • # of Connections between Web Server (Tomcat) and Weblogic AppServer

    Hi guys,
              does anybody know how many connections are used between a TomCat WebServer and the Weblogic ApplicationServer?
              - One?
              - One per active browser-user?
              - Configurable? (freely, in some ranges, which values are recommandable?)
              Does anybody has some links to related documentation maybe?
              Answers would be very helpful.
              Thanx in advance!
              Markus
              

    Hi,
    While not an exact solution to your problem, I seem to recall a similar issue, not with this web server though, but similar still. As far as I recall, the problem was related to the loading order of the library files and overlapping class files within those libraries. I think it was an issue with j2ee.jar/javaee.jar and jbossall-client.jar.
    For the standalone test, you have probably checked the following, but check again :)
    - Exact same JDK
    - Libraries in the web server lib directory
    - Libraries in application/WEB-INF/lib
    - Loading order
    You might also want to check how war file class loading is done in the web server sp6.
    Other links of interest:
    [javax.xml.soap.SOAPException known versions|http://www.jarfinder.com/index.php/java/info/javax.xml.soap.SOAPException]
    Cheers,
    Øyvind

  • Tomcat Vs Weblogic .. jsp/html file path issue..

    Tomcat gurus, please help !!!
    Development Env. :
    OS: Window NT 4.0 SP6
    Web Server: Tomcat 4.1.12
    Sun JDK 1.3.1
    IDE : Eclipse 2.1
    Deployment/Testing/Prod Env:
    OS: Sun Solaris 2.8
    Web Server: Weblogic 5.1 SP 12
    Sun JDK 1.3.1 IDE : N/A
    Confession: New to Tomcat world.
    Note: Reason why I'm using Tomcat for development though I can use Weblogic, Eclipse IDE with Tomcat plugin provides debuging functionality, thus the problem. I have an enterprise application being built and kind of stepped into a problem. I have a Servlet that marshals all the calls and process them through java beans ( about 50+ ) and content displayed through JSPs.
    Here is the directory structure,
    /AppContext
    | +- src
    | +- com.xyz.wfservices
    +- jsp
    main.jsp
    +- WEB-INF
    |
    + classes
    + com.xyz.wfservices ( compiled classes )
    For Weblogic: It has 2 parameters to specify where the compiled code is and where the docs are,
    => weblogic.httpd.servlet.classpath=c:/wfservices/WEB-INF/classes
    => weblogic.httpd.documentRoot= c:/wfservices/src/html
    and to register instance,
    weblogic.httpd.register.WfServices=com.xyz.wfservices.WfSvcsController
    weblogic.httpd.initArgs.WfServices=\
         main.properties=c:/wfservices/src/properties/wfservices.properties
    But, I looked at Tomcat it is quite different.. it has <Context path="/wfs" docBase="L:\app_services\wfservices" workDir="L:\app_services\wfservices\work" /> Servlet def in web.xml
    <servlet>
    <servlet-name>WfServices</servlet-name>
    <servlet-class>com.xyz.wfservices.WfSvcsController</servlet-class>
    <init-param>
    <param-name>main.properties</param-name>
    <param-value>c:\wfservices\properties\config.properties</param-value>
    </init-param>
         <servlet-mapping>
              <servlet-name>WfServices</servlet-name>
              <url-pattern>/WfServices</url-pattern>
         </servlet-mapping>
    </servlet>
    Probem: Accessing JSP/Html ... documents. weblogic accessing / calling jsp ..
         rd = req.getRequestDispatcher("/main.jsp");      //req is HttpRequest
         if (rd != null)
              rd.forward(req, resp);
    The same does not work under Tomcat because it can find files relative to the context, thus it fails. I have to change the code like below to make it work.
         rd = req.getRequestDispatcher("/src/jsp/main.jsp");
         if (rd != null)
              rd.forward(req, resp);
    It is a nightmare now to maintain two different environments and more over changing all the references and and its internal references is not feasible. The question is, is there a way to configure docBase in tomcat so that I won't need a code change.
    Any help or inputs are greatly appreciated.
    Thanks
    Meher

    I ran into this same problem before, so I created a utility class that would map out a URI or URL given a relative path. It's nice because it will detect and include non-standard ports for both the HTTP and HTTPS protocols. If you access a servlet/jsp using HTTP, it will return a URL for the HTTP protocol and the same for HTTPS. So, that means you don't need any code changes to access things through HTTP or HTTPS :) Here it is, hope it helps you out:
    import javax.servlet.*;
    import javax.servlet.http.*;
    public class ContextMapper
        private static final int HTTP_PORT = 80;
        private static final int HTTPS_PORT = 443;
         * This method will return a URI to access a resource given its relative
         * path.  Please note that the relative path should start in the directory
         * where the web application is deployed to.
         * @param HttpServletRequest request
         * @param HttpServletResponse response
         * @param String relativePath
         * @return String
        public static String getUri (HttpServletRequest request, HttpServletResponse response, String relativePath)
            return request.getContextPath() + relativePath;
         * This method will return a URL to access a resource given its relative
         * path.  Please note that the relative path should start in the directory
         * where the web application is deployed to.  Also, the protocol will be
         * automatically detected from the request.  Supported protocols include
         * HTTP and HTTPS.  For all other protocols, the relative path will be
         * returned unmodified.
         * @param HttpServletRequest request
         * @param HttpServletResponse response
         * @param String relativePath
         * @return String
        public static String getUrl (HttpServletRequest request, HttpServletResponse response, String relativePath)
            if (request.getProtocol().startsWith("HTTP/") == true)
                switch (request.getServerPort())
                    case HTTP_PORT:
                        return "http://" + request.getServerName() + request.getContextPath() + relativePath;
                    default:
                        return "http://" + request.getServerName() + ":" + request.getServerPort() + request.getContextPath() + relativePath;
            else if (request.getProtocol().startsWith("HTTPS/") == true)
                switch (request.getServerPort())
                    case HTTPS_PORT:
                        return "https://" + request.getServerName() + request.getContextPath() + relativePath;
                    default:
                        return "https://" + request.getServerName() + ":" + request.getServerPort() + request.getContextPath() + relativePath;
            else
                return relativePath;
    }Here are a few examples of using this class:
    String uri = ContextMapper.getUri(request, response, "/css/basic.css");
    String url = ContextMapper.getUrl(request, response, "/css/basic.css");
    String uri = ContextMapper.getUri(request, response, "/images/image.gif");
    String url = ContextMapper.getUrl(request, response, "/images/image.gif");
    String uri = ContextMapper.getUri(request, response, "/jsp/HelloWorld.jsp");
    String url = ContextMapper.getUrl(request, response, "/jsp/HelloWorld.jsp");
    String uri = ContextMapper.getUri(request, response, "/servlet/HelloWorld");
    String url = ContextMapper.getUrl(request, response, "/servlet/HelloWorld");

  • Tomcat calling weblogic applet

    Does anyone know how to get by this exception. java.security.AccessControlException:
    access denied (java.net.SocketPermission ) I'm running a web app that calls
    an applet sitting on weblogic 6.1. Whenever I try to call it, it gives me the
    socketPermission error. What do I have to do to get by this?
    Thanks

    I have managed to do this, but perhaps the way I have done it is a bit long-winded and there may be an easier (better) way. Also, note that this method is for applets on the same web site only.
    The answer lies in Javascript, where a Javascript method can call an Applet method. Therefore, if one applet can communicate with the web-page via Javascript, then any other applets on that page can communicate with any other applets there.
    This is an example piece of Javascript code to show u what I mean:
    function callAppletMethod()
       var str = window.parent.VerifyApp.check();
    etc...
    }Here, the variable 'str' gains the value returned by the method 'check()' in the applet called VerifyApp.
    There is other ways to communicate between applets and Javascript, but I think they are for Netscape Navigator browsers only.
    Anyway, hope that helps.

  • Tuxedo and tomcat/weblogic

    Hi all,
    We developed a system that used tuxedo server to handle DB transactions at around 1997, that client now requests an upgrade to allow web based access to the DB.
    There is one major concern about whether we should use Apache/Tomcat or Weblogic. Anyone knows about the interoperability between Tuxedo and Apache/Tomcat and Weblogic?
    Moreover, since the installed Tuxedo is an old version, do we need to upgrade the Tuxedo server, what sort of impact to the existing system if we do that?
    Thanks very much.
    Joey

    Hello Joey,
    I would suggest that you use BEA WebLogic Server to provide a web interface to
    your Tuxedo application. BEA has an API called "Jolt", which allows you to provide
    a Java-based interface (via Servlets/JSP, etc.) to your Tuxedo application. I
    am not familiar with how Tuxedo works with Apache/Tomcat, but I can assure you
    that you will have a lot more support and features if you go with BEA's various
    APIs and tools. Refer to the following links for more information:
    http://dev2dev.bea.com/products/tuxedo/index.jsp
    http://e-docs.bea.com/tuxedo/tux81/jdg/dvintro.htm
    http://e-docs.bea.com/tuxedo/tux81/index.htm
    Also, there is a newsgroup dedicated to BEA Tuxedo.
    Best regards,
    Ryan LeCompte
    [email protected]
    http://www.louisiana.edu/~rml7669
    Joey <[email protected]> wrote:
    Hi all,
    We developed a system that used tuxedo server to handle DB transactions
    at around 1997, that client now requests an upgrade to allow web based
    access to the DB.
    There is one major concern about whether we should use Apache/Tomcat
    or Weblogic. Anyone knows about the interoperability between Tuxedo
    and Apache/Tomcat and Weblogic?
    Moreover, since the installed Tuxedo is an old version, do we need to
    upgrade the Tuxedo server, what sort of impact to the existing system
    if we do that?
    Thanks very much.
    Joey

  • BiBeans's internationalization issue in Weblogic and Tomcat

    Dear,
    It seems that bibeans components such as Toolbar, Crosstab etc in my application can display localized labels only in OC4J, but when I depoly the application into the Tomcat or Weblogic, the labels are only displayed in English, even thought I set the locale of such compenents to China(for example, I write such code: crosstab.setLocale(Locale.China)). Can you tell me how to solve this problem? Thanks in advance.

    I think this is a question for either Tomcat support or BEA, as you correctly point out using Oracle's OC4J environment the application works correctly. Therefore, only Tomcat Support or BEA can answer why this is occuring as I presume this would affect any JSP application not just BI Beans?
    I have searched our support database and cannot find any related issues in this area. So you might also want to consider opening a TAR with Oracle Support.
    Hope this helps
    Business Intelligence Beans Product Management Team
    Oracle Corporation

  • What is the role of J2EE compared with WebLogic and Tomcat?

    Now that J2EE play the role of Web Services Container and Logic Services Container
    What does WebLogic do?and What does Tomcat do?
    Do they collided with each other?

    WebLogic (and WebSphere, JBoss, and Sun ONE) are all J2EE application servers. Each of them has an HTTP server and servlet/JSP engines built-in. They can handle HTML pages, JSPs, EJBs, messaging, transactions, two-phase commit to databases, etc.
    Tomcat is just a servlet/JSP engine with an HTTP server built in. It can handle HTML pages, servlets, and JSPs, but it can't run EJBs for you. If you want to stick EJBs into a servlet or JSP, you'll have to get them from a J2EE app server.
    No, WebLogic is a superset of Tomcat. It has an HTTP server and a servlet/JSP engine, so WebLogic can happily exist without Tomcat.
    If you'd like, you can have both Tomcat and WebLogic. Let Tomcat handle the servlet and JSP requests and leave the EJB enterprise stuff to WebLogic. You might use this arrangement when you'd like to have a Tomcat server running in a DMZ and a WebLogic app server inside the second firewall. Tomcat can then do authentication and forward requests back to WebLogic. - MOD

  • Calling an ejb from glassfish to weblogic server

    I'd like to be able to call a stateless session bean from a glassfishV3 server that is residing on weblogic 9.2.3. (Ejb spec 2.1 NOT 3.0 please)
    I've done this successfully from Tomcat to weblogic, but there are a few hiccups when trying this on glassfish.
    Basically what I've attempted is this:
    1.) I add these jvm properties to the glassfish startup:
    -Dorg.omg.CORBA.ORBClass=weblogic.corba.orb.ORB
    -Dorg.omg.CORBA.ORBSingletonClass=weblogic.corba.orb.ORB
    -Djavax.rmi.CORBA.PortableRemoteObjectClass=weblogic.iiop.PortableRemoteObjectDelegateImpl
    -Djavax.rmi.CORBA.UtilClass=weblogic.iiop.UtilDelegateImpl
    2.) Copy weblogic.jar, tools.jar, and webservices.jar from the weblogic/server/lib directory to the glassfish lib/ext directory
    ...glassfish won't start then because of the weblogic.jar...
    3.) Move the weblogic.jar to the WEB-INF/lib directory of my war in glassfish.
    Now I try it and get:
    (I'm skipping some of the stacktrace at the start)
    .....java.lang.IllegalAccessError: tried to access method weblogic.kernel.KernelStatus.initialized()V from class weblogic.kernel.Kernel at weblogic.kernel.Kernel.ensureInitialized......
    I'm guessing that this has to do with the "weblogic kernel" not being initialized. So now I'm stuck.
    Am I going down the wrong path?
    I've also tried these other proposed solutions:
    1.) Changing the connection properties of the InitialContext to use these properties:
    env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    env.put(Context.PROVIDER_URL, "t3://localhost:7001");
    env.put(Context.SECURITY_PRINCIPAL, "weblogic");
    env.put(Context.SECURITY_CREDENTIALS, "weblogic");
    2.) Using RMI over IIOP instead of T3.
    None of these with any luck.
    If anyone has done this successfully I'd appreciate some insight.
    Regards,
    Eric

    I'd like to be able to call a stateless session bean from a glassfishV3 server that is residing on weblogic 9.2.3. (Ejb spec 2.1 NOT 3.0 please)
    I've done this successfully from Tomcat to weblogic, but there are a few hiccups when trying this on glassfish.
    Basically what I've attempted is this:
    1.) I add these jvm properties to the glassfish startup:
    -Dorg.omg.CORBA.ORBClass=weblogic.corba.orb.ORB
    -Dorg.omg.CORBA.ORBSingletonClass=weblogic.corba.orb.ORB
    -Djavax.rmi.CORBA.PortableRemoteObjectClass=weblogic.iiop.PortableRemoteObjectDelegateImpl
    -Djavax.rmi.CORBA.UtilClass=weblogic.iiop.UtilDelegateImpl
    2.) Copy weblogic.jar, tools.jar, and webservices.jar from the weblogic/server/lib directory to the glassfish lib/ext directory
    ...glassfish won't start then because of the weblogic.jar...
    3.) Move the weblogic.jar to the WEB-INF/lib directory of my war in glassfish.
    Now I try it and get:
    (I'm skipping some of the stacktrace at the start)
    .....java.lang.IllegalAccessError: tried to access method weblogic.kernel.KernelStatus.initialized()V from class weblogic.kernel.Kernel at weblogic.kernel.Kernel.ensureInitialized......
    I'm guessing that this has to do with the "weblogic kernel" not being initialized. So now I'm stuck.
    Am I going down the wrong path?
    I've also tried these other proposed solutions:
    1.) Changing the connection properties of the InitialContext to use these properties:
    env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    env.put(Context.PROVIDER_URL, "t3://localhost:7001");
    env.put(Context.SECURITY_PRINCIPAL, "weblogic");
    env.put(Context.SECURITY_CREDENTIALS, "weblogic");
    2.) Using RMI over IIOP instead of T3.
    None of these with any luck.
    If anyone has done this successfully I'd appreciate some insight.
    Regards,
    Eric

  • Spring web-service application in weblogic 9.1

    Hi,
    Iam trying to port the sample application given with Spring Web Services download(It works great with tomcat) to Weblogic 9.1. There were some issues doing it. You can see the discussion here. [url http://forum.springframework.org/showthread.php?t=26205]
    I did that accordingly and Iam getting a [org.springframework.ws.soap.axiom.AxiomSoapMessageFactory]: Constructor threw exception; nested exception is java.lang.ClassCastException: weblogic.xml.stax.XMLStreamInputFactory
            at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:451)
            at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
            at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
            at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
            at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
            Truncated. see log file for complete stacktrace
    org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.springframework.ws.soap.axiom.AxiomSoapMessageFactory]: Constructor threw exception; nested exception is java.lang.ClassCastException: weblogic.xml.stax.XMLStreamInputFactory
            at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:100)
            at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:61)
            at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:759)
            at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:724)
            at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:387)
            Truncated. see log file for complete stacktrace
    java.lang.ClassCastException: weblogic.xml.stax.XMLStreamInputFactory
            at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136)
            at org.springframework.ws.soap.axiom.AxiomSoapMessageFactory.<init>(AxiomSoapMessageFactory.java:97)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
            Truncated. see log file for complete stacktrace error.
    Look at this page for the settings i have done. [url http://forum.springframework.org/showthread.php?t=40051]
    Please help me resolve this issue.
    Thanks
    Vignesh

    Well, in the web.xml for the app we have it set up as BASIC authentication, and list the roles that are allowed at that particular site. In order to sign in, another app would have to set the authorization property in the URLConnection.
    The problem is, using AXIS to connect, I have no way to set this property in the connection, since it is wrapped up by axis. (Call)
    I have reached a potential solution of constructing the soap message with the client using means other than the AXIS API, which I am implementing now and praying it will work!
    Everything I have read suggests using SSL to connect to the web service, but I can't figure out how to set up SSL so that my host/axisweb directory needs HTTPS but host/ doesn't...
    Does this make sense? Any suggestions?

  • RTFProcessor produces invalid XSL-FO in WebLogic

    I've been writing an application that uses the RTProcessor class to process an rtf file into XML, which I can then parse to information about the report layout.
    While developing on tomcat this worked fine. However for production we will be deploying on WebLogic. WebLogic seems to be using a different XML parser that is stricter than tomcats so when using the application the XML parser throws an error when parsing the XSL-FO.
    The problem is that XSL-FO is not valid XML as it contains an invalid character on the line:
    <xsl:variable name="_XDOXSLTCTX" select="xdoxslt:set_xslt_locale($_XDOCTX, $_XDOLOCALE, $_XDOTIMEZONE, $_XDOCALENDAR, concat($_XDODFOVERRIDE,'',$_XDOCURMASKS,'',$_XDONFSEPARATORS))"/>
    So my first question is: Is there a way to stop this element from being generated in the XSL-FO? This seems to have been looked at in this thread but without much of a conclusion:
    BI Publisher produces invalid XSL:FO stylesheet
    My second question: I don't understand how Tomcat can parse the XML and WebLogic can't. I'm deploying the same code so I'd assumed it would be using the same parser. As a work around around is it possible to configure WebLogic to use the same parser as tomcat? The relevant code I'm using is posted below:
    ByteArrayOutputStream templateOutputStream = new ByteArrayOutputStream();
                   RTFProcessor rtfProcessor = new RTFProcessor(
                             new FileInputStream(template.getTemplateFile())
                   rtfProcessor.setOutput(templateOutputStream);
                   rtfProcessor.process();
                   logger.debug(this.className + " - " + methodName +
                             ":#2 XSL-FO : " + templateOutputStream.toString());
                   DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
                   DocumentBuilder db = dbf.newDocumentBuilder();
                   // parse using builder to get DOM representation of the XML file
                   Document dom = db.parse(new ByteArrayInputStream(templateOutputStream.toByteArray()));
    Thanks in advance.

    Hi,
    Thanks for your reply, After debugging the application carefully in Tomcat and Weblogic it became apparent that weblogic was using it's preferred XML parsers when parsing my XML.
    In Tomcat has a different order or precedence for its class loader so it was parsing my XML with the oracle.xml package, Weblogic was instead using its own weblogic.xml parser. So I had to set up a weblogic-application.xml file to control this.
    If you're right that the XML is valid, then this looks like there is a bug in the weblogic parser. I'm not at work at the moment but if you want more details I can get you them next week.
    Thanks.

  • Problem using myfaces on webLogic

    I run into the problem using myfaces on webLogic 9.1.
    That is... a managedBean's instance is created twice in one page.
    That page is consisted with one <h:inputText> and <h:commandButton>.
    After some tests, we found out that the problems happens in a JSP which has <h:inputText>...
    This problem didn't happen on Tomcat or JDeveloper.
    We tried with another application.
    And oh my goodness, it didn't happen.
    It worked collect with no problems at all.
    The difference between two application is,
    the former managedBean extends abstract class,
    and the latter doesn't.
    Pls help me.....

    It was a program bag rather than weblogic's problem.
    In the program, it deleted all the objects in the session scope.
    So, after JSF render the next JSP, it re-create a managed bean.
    But, I'm still wonder why the same things didn't happen in Tomcat.
    WebLogic put managed bean into the session soon after JSF
    creates it.
    On the otherhand, Tomcat does that after managedbean's action
    is completed???
    Considering the JSF specification, i think weblogic is right.
    Cos,JSF put all the components and related managed bean
    into session, in the rendering phase.
    Thanks for asking anyway.

  • How useJsp 2.0 tag file in Weblogic 9.2

    I would like to use the JSP 2.0 tag file feature involving having a jsp fragment as an attribute.
    The example I have runs fine in Tomcat 6.0. And it runs fine in Weblogic 10.0 and 10.3 But when I run the same test on weblogic 9.2, I get the following error:
    Compilation of JSP File '/jsp/tagfile_hello_test.jspx' failed:
    tagfile_hello_test.jspx:19:8: This tag can only appear as a subelement of a standard or custom action. Exceptions are: jsp:body, jsp:attribute, jsp:expression, jsp:scriptlet, and jsp:declaration.
    <jsp:attribute name="footer">
    Below I show the output I get when running in Tomcat.
    Also below are the listing for the calling jsp page and the tag file page, tagfile_hello_test.jspx and tagfile_hello.tagx respectively.
    The burning question I am trying resolve is why does the example runs perfectly fine in Tomcat and Weblogic 10.0 and 10.3 but fails in Weblogic 9.2. Tag files are part of the JSP2.0 specification and Weblogic 9.2 implements the specification.
    Any help is greatly appreciated.
    Output from Tomcat and Weblogic 10.3:
    JSP 2.0 Examples Tag File
    This JSP page invokes a tag file that has a footer fragment
    Inside tagfile_hello
    Invoking footer: I am the footer
    Listing of tagfile_hello_test.jspx:
    <html xmlns:c="http://java.sun.com/jsp/jstl/core"
         xmlns:fmt="http://java.sun.com/jsp/jstl/fmt"
         xmlns:jsp="http://java.sun.com/JSP/Page"
         xmlns:tags="urn:jsptagdir:/WEB-INF/tags">
    <jsp:directive.page contentType="text/html" />
    <head>
    <title>Hi</title>
    </head>
    <body>
    <h1>JSP 2.0 Examples Tag File</h1>
    <hr/>
    <p>This JSP page invokes a tag file that has a footer fragment</p>
    <tags:tagfile_hello>
    <jsp:attribute name="footer">
                   <b>I am the footer</b>
    </jsp:attribute>
    </tags:tagfile_hello>
    </body>
    </html>
    Listing of tagfile_hello.tagx:
    <jsp:root
         xmlns:c="http://java.sun.com/jsp/jstl/core"
         xmlns:fmt="http://java.sun.com/jsp/jstl/fmt"
         xmlns:jsp="http://java.sun.com/JSP/Page"
         version="2.0"
    >
    <jsp:directive.attribute name="footer" required="true" fragment="true"/>
    Inside tagfile_hello
    Invoking footer:
    <jsp:invoke fragment="footer"/>
    </jsp:root>

    Yes John.. i am using startNodemanager.sh.
    Is this the change OutFile=$ServerDir/logs/$ServerName.out you are talking about.
    wlscontrol.sh file:
    # Directory and file names
    ServerDir=$DomainDir/servers/$ServerName
    SaltFile=$DomainDir/security/SerializedSystemIni.dat
    OldSaltFile=$DomainDir/SerializedSystemIni.dat
    StateFile=$ServerDir/data/nodemanager/$ServerName.state
    PropsFile=$ServerDir/data/nodemanager/startup.properties
    PidFile=$ServerDir/data/nodemanager/$ServerName.pid
    LockFile=$ServerDir/data/nodemanager/$ServerName.lck
    BootFile=$ServerDir/security/boot.properties
    RelBootFile=servers/$ServerName/security/boot.properties
    NMBootFile=$ServerDir/data/nodemanager/boot.properties
    RelNMBootFile=servers/$ServerName/data/nodemanager/boot.properties
    OutFile=$ServerDir/logs/$ServerName.out
    SetDomainEnvScript=$DomainDir/bin/setDomainEnv.sh
    StartWebLogicScript=$DomainDir/bin/startWebLogic.sh
    MigrationScriptDir=$DomainDir/bin/service_migration
    Thanks,
    Krish

Maybe you are looking for