StreamingSender raises missing document root

I have a jax-rpc web service that I generated using jwsdp 1.2 tools. It all works fine except when I try to throw a user defined Exception on the server side, I get the following exception on the client:
ava.rmi.RemoteException: Runtime exception; nested exception is:
     XML parsing error: com.sun.xml.rpc.sp.ParseException:1: Document root element is missing
     at com.sun.xml.rpc.client.StreamingSender._handleRuntimeExceptionInSend(StreamingSender.java:258)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:240)
     at com.wstest.webrpc.ObjectPropertiesIF_Stub.createObject(ObjectPropertiesIF_Stub.java:69)
     at com.wstest.webrpc.clients.MyClientProxy.createObject(MyClientProxy.java:128)
When I inspect the SOAP response I see the following:
HTTP/1.1 500 Internal Server Error
Date: Wed, 04 May 2005 17:12:52 GMT
Server: Apache/2.0.52 (Win32) mod_jk2/2.0.4
SOAPAction: ""
Content-Type: text/xml; charset="utf-8"
Connection: close
Transfer-Encoding: chunked
371
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://com.test/types/MyObjectProperties" xmlns:ns1="http://java.sun.com/jax-rpc-ri/internal"><env:Body><env:Fault xsi:type="env:Fault"><faultcode>env:Server</faultcode><faultstring>com.wstest.webrpc.MyServerException</faultstring><detail><ans1:MyServerException xmlns:ans1="http://com.test/wsdl/MyObjectProperties" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns0:MyServerException"><code xsi:type="xsd:long">2</code><message xsi:type="xsd:string">This is a dummy error</message></ans1:MyServerException></detail></env:Fault></env:Body></env:Envelope>
0
which appears to my untrained eyes to be a reasonably legitimate fault response. Can anyone tell me why my client is choking on this instead of raising the appropriate exception?
Thanks!
Jim

I have a jax-rpc web service that I generated using jwsdp 1.2 tools. It all works fine except when I try to throw a user defined Exception on the server side, I get the following exception on the client:
ava.rmi.RemoteException: Runtime exception; nested exception is:
     XML parsing error: com.sun.xml.rpc.sp.ParseException:1: Document root element is missing
     at com.sun.xml.rpc.client.StreamingSender._handleRuntimeExceptionInSend(StreamingSender.java:258)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:240)
     at com.wstest.webrpc.ObjectPropertiesIF_Stub.createObject(ObjectPropertiesIF_Stub.java:69)
     at com.wstest.webrpc.clients.MyClientProxy.createObject(MyClientProxy.java:128)
When I inspect the SOAP response I see the following:
HTTP/1.1 500 Internal Server Error
Date: Wed, 04 May 2005 17:12:52 GMT
Server: Apache/2.0.52 (Win32) mod_jk2/2.0.4
SOAPAction: ""
Content-Type: text/xml; charset="utf-8"
Connection: close
Transfer-Encoding: chunked
371
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://com.test/types/MyObjectProperties" xmlns:ns1="http://java.sun.com/jax-rpc-ri/internal"><env:Body><env:Fault xsi:type="env:Fault"><faultcode>env:Server</faultcode><faultstring>com.wstest.webrpc.MyServerException</faultstring><detail><ans1:MyServerException xmlns:ans1="http://com.test/wsdl/MyObjectProperties" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns0:MyServerException"><code xsi:type="xsd:long">2</code><message xsi:type="xsd:string">This is a dummy error</message></ans1:MyServerException></detail></env:Fault></env:Body></env:Envelope>
0
which appears to my untrained eyes to be a reasonably legitimate fault response. Can anyone tell me why my client is choking on this instead of raising the appropriate exception?
Thanks!
Jim

Similar Messages

  • Org.xml.sax.SAXParseException: Document root element is missing.

    Hi,
    I am trying to get the portal login id from a weblogic server based application from iplaet portal server.
    I get this follwoing error
    org.xml.sax.SAXParseException: Document root element is missing.
    at com.sun.xml.parser.Parser.fatal(Parser.java:2817)
    at com.sun.xml.parser.Parser.fatal(Parser.java:2805)
    at com.sun.xml.parser.Parser.parseInternal(Parser.java:493)
    at com.sun.xml.parser.Parser.parse(Parser.java:284)
    at com.sun.xml.tree.XmlDocument.createXmlDocument(XmlDocument.java:226)
    at com.iplanet.portalserver.util.XMLParser.<init>(XMLParser.java:70)
    at com.iplanet.portalserver.naming.share.NamingResponseParser.<init>(NamingResponseParser.java:33)
    at com.iplanet.portalserver.naming.share.NamingResponse.parseXML(NamingResponse.java:74)
    at com.iplanet.portalserver.naming.WebtopNaming.updateNamingTable(WebtopNaming.java:174)
    at com.iplanet.portalserver.naming.WebtopNaming.getNamingProfile(WebtopNaming.java:155)
    at com.iplanet.portalserver.naming.WebtopNaming.getServiceURL(WebtopNaming.java:57)
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:534)
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:520)
    at com.iplanet.portalserver.session.Session.getSession(Session.java:414)
    at jsp_servlet.__eatonPortalLogin._jspService(__eatonPortalLogin.java:155)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:462)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    <May 19, 2004 9:01:12 AM EDT> <Error> <HTTP> <101017> <[ServletContext(id=4873279,name=ematrix,context-path=/ematrix)] Root cause of ServletException
    com.iplanet.portalserver.session.SessionException
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:539)
    at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:520)
    at com.iplanet.portalserver.session.Session.getSession(Session.java:414)
    at jsp_servlet.__eatonPortalLogin._jspService(__eatonPortalLogin.java:155)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:462)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    Any help/pointers will be appreciated.
    Ashish

    Just for anyone else who hits this problem: I encountered the same issue with an XML document that XMLSpy claims is quite well formed. I opened the document in a hex editor, and there at the from was a three-byte byte order marker - the marker that I believe the UTF-8 standard says is optional. I removed these three bytes, and the file was parsed correctly.
    In this case, the XML file was created using a Microsft DOM (save).
    My solution is to make the java parser - as I use it - a tad more robust: Open the file and create an input stream - a pushback input stream. Read the first three bytes; if they are NOT a BOM, then push those bytes back. Now - in any case - give the stream to the parser to read.
    try {
    // Open file for reading.
    f = new File(path);
    FileInputStream fis = new FileInputStream(f);
    PushbackInputStream pis = new PushbackInputStream(fis);
    byte[] buf = new byte[3];
    pis.read(buf, 0, 3);
    if (! (buf[0] == 0x00EF) && (buf[1] == 0x00BB) && (buf[2] == 0x00BF) ) {
         pis.unread(buf, 0, 3);
    builder = DocumentBuilderFactory.newInstance().newDocumentBuilder();
    doc = builder.parse(pis);
    catch (Exception x) {
         x.printStackTrace();
    }

  • XML "Document root element is missing"

    i have made a research in the forums but i have no definite solution about the error.
    my flash client sends XML stream to my ServerSocket. and i want to parse these XML datas.
    Document XMLDoc;
    DocumentBuilderFactory Factory = DocumentBuilderFactory.newInstance();
    DocumentBuilder Builder = Factory.newDocumentBuilder() ;
    InputSource Is = new InputSource(new BufferedReader(new InputStreamReader(Sock.getInputStream(),"UTF-16LE")));
    XMLDoc = Builder.parse(Is);
    But now i have problem called "Document root element is missing". My XML stream comming from flash client :
    // Actionscript code :
         XDoc = new XML("<?XML version=\"1\"?><LOGIN><USERNAME>KHARON</USERNAME><PASSWORD>485009</PASSWORD></LOGIN>");
    ----- The XML data i want to sent to ...
    <?XML version="1"?>
    <LOGIN>
    <USERNAME>KHARON</USERNAME>
    <PASSWORD>485009</PASSWORD>
    </LOGIN>
    What is the problem ?

    now ?
    // Actionscript
    XSock = new XMLSocket();
    XSock.connect("127.0.0.1",6667);
    XDoc = new XML("<?xml version=\"1.0\"?><LOGIN><USERNAME>KHARON</USERNAME><PASSWORD>ew2345dfs</PASSWORD></LOGIN>");
    // Java
    public void run() {
    try {
    Document XMLDoc;
    DocumentBuilderFactory Factory = DocumentBuilderFactory.newInstance();
    DocumentBuilder Builder = Factory.newDocumentBuilder() ;
    InputSource Is = new InputSource(new BufferedReader(new InputStreamReader(Sock.getInputStream(),"UTF-16LE")));
    XMLDoc = Builder.parse(Is);
    org.w3c.dom.Node Node = XMLDoc.getFirstChild();
    System.out.print(Node.getNodeValue());
    /* Incomming data test code
    System.out.print("Listening to incomming messeges");
    char in ;
    while ( (in = (char)Reader.read()) != -1 ) {
    System.out.print( in );
    but the result
    parser exception ( Document root element is missing )
    ihave made a research ( i am newbee in XML) and i have made some declerations like <!DOCTYPE LOGIN <!Element ...
    i have declared root element with DOC type decleration. but the same error. :|
    since 2 days i am working over these, but solution = null

  • Document root element is missing: migrating spring app from tomcat

    Hi!
    can anybody help me with this issue?
    I have ported my tomcat spring application to netweaver(6.40, SP 17, Windows 2k SP4) and i get the following error:
    Error occured in invoking event "contextInitialized()" on listener clas
    s com.webapp.listener.StartupListener. The error is: org.springfram
    ework.beans.factory.BeanCreationException: Error creating bean with nam
    e 'sessionFactory' defined in ServletContext resource [/WEB-INF/applica
    tionContext-hibernate.xml]: Initialization of bean failed; nested excep
    tion is org.hibernate.MappingException: Could not parse mapping documen
    t in input stream
    org.hibernate.MappingException: Could not parse mapp
    ing document in input stream
         at org.hibernate.cfg.Configuration.addIn
    putStream(Configuration.java:430)
         at org.springframework.orm.hibernat
    e3.LocalSessionFactoryBean.afterPropertiesSet(LocalSessionFactoryBean.j
    ava:654)
         at org.springframework.beans.factory.support.AbstractAutowir
    eCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactor
    y.java:1059)
         at org.springframework.beans.factory.support.AbstractAut
    owireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.j
    ava:363)
         at org.springframework.beans.factory.support.AbstractBeanFac
    tory.getBean(AbstractBeanFactory.java:226)
         at org.springframework.bea
    ns.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java
    :147)
         at org.springframework.beans.factory.support.DefaultListableBea
    nFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:269)
         at org.springframework.context.support.AbstractApplicationContext.ref
    resh(AbstractApplicationContext.java:320)
         at org.springframework.web.
    context.support.AbstractRefreshableWebApplicationContext.refresh(Abstra
    ctRefreshableWebApplicationContext.java:134)
         at org.springframework.w
    eb.context.ContextLoader.createWebApplicationContext(ContextLoader.java
    :246)
         at org.springframework.web.context.ContextLoader.initWebApplica
    tionContext(ContextLoader.java:184)
         at org.springframework.web.contex
    t.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:4
    9)
         at com.ifx.webapp.listener.StartupListener.contextInitialized(Star
    tupListener.java:42)
         at com.sap.engine.services.servlets_jsp.server.r
    untime.context.WebEvents.contextInitialized(WebEvents.java:45)
         at com
    .sap.engine.services.servlets_jsp.server.container.ApplicationThreadIni
    tializer.run(ApplicationThreadInitializer.java:112)
         at com.sap.engine
    .core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.sec
    urity.AccessController.doPrivileged(Native Method)
         at com.sap.engine.
    core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.
    sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    C
    aused by: org.dom4j.DocumentException: Error on line 1 of document  : D
    ocument root element is missing. Nested exception: Document root elemen
    t is missing.
         at org.dom4j.io.SAXReader.read(SAXReader.java:482)
         at
    org.hibernate.cfg.Configuration.addInputStream(Configuration.java:421)
         ... 18 more
    And yes, the xml files are valid xml files at least in anything i've used to look at them (eclipse, ultraedit, notepad, ie) :).....
    Thank you!
    ps. the file:
    <?xml version="1.0" encoding="UTF-8" ?>
    <!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN"
        "http://www.springframework.org/dtd/spring-beans.dtd">
    <beans>
        <!-- Hibernate SessionFactory -->
        <bean id="sessionFactory" class="org.springframework.orm.hibernate3.LocalSessionFactoryBean">
            <property name="dataSource" ref="dataSource"/>
            <property name="mappingResources">
                <list>
                    <value>package/ModelObj1.hbm.xml</value>
                    <value>package/ModelObj2.hbm.xml</value>
                </list>
            </property>
            <property name="hibernateProperties">
                <props>
                    <prop key="hibernate.dialect">org.hibernate.dialect.Oracle9Dialect</prop>
                </props>
            </property>
        </bean>
        <!-- Transaction manager for a single Hibernate SessionFactory (alternative to JTA) -->
        <bean id="transactionManager" class="org.springframework.orm.hibernate3.HibernateTransactionManager">
            <property name="sessionFactory" ref="sessionFactory"/>
        </bean>
        <!-- Generic DAO - can be used when doing standard CRUD -->
        <bean id="dao" class="com.dao.hibernate.BaseDAOHibernate">
            <property name="sessionFactory" ref="sessionFactory"/>
        </bean>
    </beans>

    hi istvan,
    we are also migrating from websphere to netweaver.
    But in spring framework we r facing problems.
    We hav spring-beans.jar file in lib dir of Web Application. But When we are creating BeanFactory from xml as,
    BeanFactory beanFactory = new ClassPathXmlApplicationContext ("client-config.xml");
    clent-config.xml file contains :
    [code<?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">
    <beans>
         <bean id="propertyConfigurer" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer" >
              <property name="location">
                   <value>conf/service-client/client.properties</value>
              </property>
         </bean></beans>
    [/code]
    But code is giving exception: ClassNotFoundException -org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.
    Wat is the problem ?
    Kindly help.
    We are also using JAAS for authentication.We are refering above code from our LoginModules login() method.
    Regards,
    sagar.

  • Parsing xml file error: Document root element is missing.

    Hi,
    When I try to parse an xml file with SAX parser, the SAXParseException message I got is: "Document root element is missing." Anybody knows what it is? How should I fix it? Thanks a lot in advance!
    J.H.

    An XML document has only a single root element. So after the XML header, your document must look something like this:
    <tag>
    </tag>
    If you have more than one element like this, for example:
    <tag>
    </tag>
    <anothertag>
    </anothertag>
    then you don't have a root element and your parser will give the message you referred to.

  • R/3 vs BW - Missing documents in BW

    Hi,
    After comparing the BW data with R/3 in production, we found the following variances,
    Identified BW variances:
    1) PCA Cube Variance 11/05 & 12/05 - resolved
           – resolved by execution of full load.
    2) PCA Cube Variance 08/05 - unresolved
           – Unable to utilize FI-SL doc type field.
    Question :
    Could you please help me to identify the root cause for this issue and help me to determine a solution for preventing missing documents in BW.
    Thanks,Senthil

    Hi,
    Thanks for your reply.
    I have checked the values for doc type field, it is coming from R/3.
    I also checked the transfer and update rules, records are not filtered, I don't get any other clue as well. Missing records were updated through full update for the period Nov-05.
    I supposed to identify the root cause for this issue and also find a solution for preventing missing documents in BW (Future).
    Please share if you have any other idea as well.
    Thanks, Senthil

  • Shared Document Root & Multiple Mail Spooling Issue

    I've shared my document root (
    as
    per these instructions) accross 7 JRun instances, but now any
    email sent from 1 of them gets sent 7 times.
    Seems what's happening is that the mail spool is getting
    shared accross all instances, but all instances are also trying to
    send the same file.
    I can change the mail spool directory mapping, but that seems
    odd. Did I miss something? How do others deal with this?
    To do this, we have to edit XML files to make all this
    happen. For each server instance, edit the jrun-web.xml file in
    {jrun.home}/servers/<instance>/cfusion/WEB-INF/ (assuming
    your context root is /cfusion).
    <virtual-mapping>
    <resource-path>/</resource-path>
    <system-path/>
    </virtual-mapping>
    <context-root>/cfusion</context-root>
    <compile>false</compile>
    <reload>false</reload>
    <uri-character-encoding>UTF-8</uri-character-encoding>
    <virtual-mapping>
    <resource-path>/*</resource-path>
    <system-path>{cfmx}/wwwroot</system-path>
    </virtual-mapping>
    <virtual-mapping>
    <resource-path>/WEB-INF/*</resource-path>
    <system-path>{jrun.home}/servers/<instance>/cfusion/WEB-INF</system-path>
    </virtual-mapping>
    </jrun-web-app>

    Worth a try according to
    http://answers.microsoft.com/en-us/office/forum/office_2010-word/wordexcel-2010-merge-error-has-occurred-external/3facb2b9-a7ed-41a7-bf22-51666b8418eb
    which you already have read.
    "Opening and then closing Access seems to be the key"
    Regards Pete

  • Missing documents from 2LIS_03_BF/2LIS_03_UM

    We discovered that on one day last week for a few hours most if not all material and accounting documents were not getting captured coming from 2LIS_03_BF and UM. 
    We've been live using 2LIS_03_BF and UM since May of last year and never had any trouble with missing documents from the inventory extractors until last week, and are not sure what could cause this?
    We patched things up by identifying the missing documents and loading those into BW doing new initializations/full repair requests.  Everything seems fine now, but we'd like to know how to prevent this in the future.  Has anyone experienced this before where suddenly LO documents are not getting captured?
    We found OSS note 766622 which allows for a logging feature for application 03 (LO-IM) but are not sure what kind of system overhead this will cause.  Has anyone else implemented this note and could comment on any impact on the R/3 production system?
    Thanks,
    Chris

    Hi Chris,
    you are not the first and probably you will not the last to face similar problem with inventory management: I already saw similar situation, but I never found a customer with this OSS Note applied (that, among the other thing, is not a solution, but an activation of a log system in order to hope to understand something next time will happen a similar problem)...
    If SAP support has this type of approach in its OSS note I think that the answer to your doubt will remain unanswered: the cause of this problem is not known and (as you can understand from your experience) it's really hard to understand what's happened !
    The only way to go is applying the log system as per OSS Note and hoping (what a paradox !) that the problem will raise again !!!
    If you apply the note, I don't believe that you will see relevant performance impact (even if you have to write on TMCEXLOG table), but this depends from the average number of your material movements/delta records...
    Bye,
    Roberto

  • Org.xml.sax.SAXParseException: Document root element "taglib", must match D

    hi
    using tomcat 4
    and jdf1.5
    i am getting bellow error
    org.xml.sax.SAXParseException: Document root element "taglib", must match DOCTYPE root "null".

    Check your web.xml once again.

  • Setting Document Root in WebLogic 6.1

    I have recently migrated from WebLogic 5.1 to WebLogic 6.1, on Windows 2000
    running jdk 1.3.1. My Document Root settings (weblogic.httpd.documentRoot)
    from WebLogic 5.1 in my weblogic.properties file did not carry over to
    WebLogic 6.1, so does anybody know how to set the Document Root in WebLogic
    6.1? Or is there an equivalent to it now?
    Thanks in advance,
    Dustin N. Jenkins

    Hi Dustin,
    I think you posted this to the wrong newsgroup :-)
    In WLS 6.1, document roots are Web Application specific. Unless you explicitly
    change it, the default Web Application (the one that you get when you type in
    the http://localhost:7001 URL), the document root is a folder under your domain's
    application directory named "DefaultWebApp_{name-of-your-server}". Where {name-of-your-server}
    is whatever value you assigned to the -Dweblogic.Name property, on the command
    line you started WLS with. Refer to the WLS 6.1 documentation for instructions
    on how to change this to a different Web Application. Here are a couple of links
    that will provide you with some insight into this:
    http://edocs.bea.com/wls/docs61/webapp/basics.html#136976
    http://edocs.bea.com/wls/docs61/adminguide/web_server.html#113228
    Regards,
    Mike Wooten
    "Dustin N. Jenkins" <[email protected]> wrote:
    I have recently migrated from WebLogic 5.1 to WebLogic 6.1, on Windows
    2000
    running jdk 1.3.1. My Document Root settings (weblogic.httpd.documentRoot)
    from WebLogic 5.1 in my weblogic.properties file did not carry over to
    WebLogic 6.1, so does anybody know how to set the Document Root in WebLogic
    6.1? Or is there an equivalent to it now?
    Thanks in advance,
    Dustin N. Jenkins

  • Changing the document root in WLS 6.0 SP1

    Hello,
              I want to change the deployment folder of
              config/<domainName>/applications
              to another folder in our source tree. Is this possible? The reason we
              want to do this is because our root tree contains the java source code
              and web-related content in our configuration management system. It
              would seem very odd to map our web-related stuff to
              /WLS6.0sp1/config/<mydomain>/applications and everything else to the
              standard structure.
              In 5.1, setting the weblogic.httpd.documentRoot property does this.
              However, I understand that WLS 6.0 uses a classloader for the
              /applications directory. Can I use a system to property to notify WLS
              6.0 to look at a different directory instead?
              There seems to be error in docs related to this.
              http://e-docs.bea.com/wls/docs60///////config_xml/properties.html
              Says DocumentRoot entry can be set in config.xml.
              But the entry is not found in DTD (config.dtd)
              http://e-docs.bea.com/wls/docs60///////config_xml/config.html
              Thanks.
              --Bahar
              

    Bahar,
              The docs you pointed out is absolutely right. There is no error in the
              document.
              If you want to change the document root make the following
              modifications in your config.xml as per the example here:
              <Application Deployed="true" Name="DefaultWebApp_myserver"
              Path="d:\docmain">
              <WebAppComponent Name="DefaultWebApp_myserver"
              Targets="myserver" URI="www"/>
              </Application>
              Where Your document root is : d:\docmain\www
              Make sure that you have web.xml under
              d:\docmain\www\WEB-INF
              Kumar.
              Bahar Limaye wrote:
              > Hello,
              >
              > I want to change the deployment folder of
              > config/<domainName>/applications
              > to another folder in our source tree. Is this possible? The reason we
              > want to do this is because our root tree contains the java source code
              > and web-related content in our configuration management system. It
              > would seem very odd to map our web-related stuff to
              > /WLS6.0sp1/config/<mydomain>/applications and everything else to the
              > standard structure.
              >
              > In 5.1, setting the weblogic.httpd.documentRoot property does this.
              > However, I understand that WLS 6.0 uses a classloader for the
              > /applications directory. Can I use a system to property to notify WLS
              > 6.0 to look at a different directory instead?
              >
              > There seems to be error in docs related to this.
              > http://e-docs.bea.com/wls/docs60///////config_xml/properties.html
              > Says DocumentRoot entry can be set in config.xml.
              > But the entry is not found in DTD (config.dtd)
              > http://e-docs.bea.com/wls/docs60///////config_xml/config.html
              >
              > Thanks.
              >
              > --Bahar
              

  • How to map directory not under "document root" directory?

    In Weblogic (5.1.0), how do you map one URL "directory" to a filesystem
    directory that is not a subdirectory of the regular document root
    directory?
    This is, I want some URL "http://xxx.com/some/subset" to map to local
    directory "/x/y" instead of mapping to a subdirectory "some/subset"
    under the document root directory (the directory to which
    "http://xxx.com/" maps).
    How do you do this in Weblogic (using Weblogic as the HTTP server,
    not using it plugged in to some other HTTP server)?
    (In Apache, this would be the "Alias" directive.)
    Thanks,
    Daniel
    Daniel Barclay
    Digital Focus
    [email protected]

    [REPLY TO NEWSGROUP ------- This followup was posted to
    weblogic.support.install and a copy was sent to the cited author.]
    Default registration for the file servlet is:
    weblogic.httpd.register.file=weblogic.servlet.FileServlet
    weblogic.httpd.initArgs.file=defaultFilename=index.html
    So do this:
    weblogic.httpd.register.some/subset=weblogic.servlet.FileServlet
    weblogic.httpd.initArgs.some/subset=defaultFilename=index.html,docHome=d:
    /foo/bar/baz
    mbg
    In article <[email protected]>,
    [email protected] says...
    >
    In Weblogic (5.1.0), how do you map one URL "directory" to a filesystem
    directory that is not a subdirectory of the regular document root
    directory?
    This is, I want some URL "http://xxx.com/some/subset" to map to local
    directory "/x/y" instead of mapping to a subdirectory "some/subset"
    under the document root directory (the directory to which
    "http://xxx.com/" maps).
    How do you do this in Weblogic (using Weblogic as the HTTP server,
    not using it plugged in to some other HTTP server)?
    (In Apache, this would be the "Alias" directive.)
    Thanks,
    Daniel
    ==================================================
    NewsGroup Rant
    ==================================================
    Rant 1.
    The less info you provide about your problem means
    the less we can help you. Try to look at the
    problem from an external perspective and provide
    all the data necessary to put your problem in
    perspective.

  • Missing Document Number Report in Oracle Accounts Payable

    Hi All,
    Can you please let me know if there alternative report for Missing Document Number Report in R12......
    similar to what we had in 11.5.9 Instance In AP
    Thanks
    Edited by: user5358827 on Apr 19, 2010 11:31 AM

    Hi
    We have tried this but no output. ie the issue continues the same. This issue is there for all PC including Server. Is there any other solution avaliable. .
    Regards
    Sunil

  • Can I have more document roots?

    Hello,
    I am new to Web Logic. I have been using JRun for a while. Now I have to
    port these applications to Web Logic server. In Allaire JRun document roots
    can be specified in local.properties file (see the following example). How
    to modify weblogic.properties file to run both the applications
    simultaneously. See the attachment for more info about local.properties.
    JRUN local.properties
    Store1.rootdir=H:\\Webroot\\Store1
    Store1.class={webapp.service-class}
    webapp.mapping./store1=store1
    Store2.rootdir=H:\\Webroot\\Store2
    Store2.class={webapp.service-class}
    webapp.mapping./store1=store2
    H:\Webroot
    - \Store1
    - HTML folder
    - Images folder
    - WEB-INF
    - classes
    - \Store2
    - HTML folder
    - Images folder
    - WEB-INF
    -classes
    Thanks
    Meher
    [local.properties]

    See doc about deploying a webapp in .war format.
    Basically, each .war web application has its own document root,
    specified by the
    weblogic.httpd.webApp.<webapp-docroot>=<fullpathtowarfile> in the
    weblogic.properties file.
    John Salvo
    SrinivasMeher Kandukuri wrote:
    >
    Hello,
    I am new to Web Logic. I have been using JRun for a while. Now I have to
    port these applications to Web Logic server. In Allaire JRun document roots
    can be specified in local.properties file (see the following example). How
    to modify weblogic.properties file to run both the applications
    simultaneously. See the attachment for more info about local.properties.
    JRUN local.properties
    Store1.rootdir=H:\\Webroot\\Store1
    Store1.class={webapp.service-class}
    webapp.mapping./store1=store1
    Store2.rootdir=H:\\Webroot\\Store2
    Store2.class={webapp.service-class}
    webapp.mapping./store1=store2
    H:\Webroot
    - \Store1
    - HTML folder
    - Images folder
    - WEB-INF
    - classes
    - \Store2
    - HTML folder
    - Images folder
    - WEB-INF
    -classes
    Thanks
    Meher
    Name: local.properties
    local.properties Type: unspecified type (application/octet-stream)
    Encoding: x-uuencode

  • How do I change the document root and servlets root in WL 6.0

    Please reply fast.
    Suresh Wilson

    In 5.1, you specify the "name" via the property:
    weblogic.httpd.webApp.NAME=<path_to_war>
    ... where NAME is the path in the URL where you want your webapp to be
    access from
    Say:
    weblogic.httpd.webApp.sampleapp=/home/weblogic/product/wls/5.1/sample.war
    ... the application's root is http://hostname/sampleapp
    In 6.0, it seems to be the name of the war file itself. I deployed the
    war twice, one using sampleapp.war and the other using sampleapp2.war,
    and the webapps' root are http://hostname/sampleapp and
    http://hostname/sampleapp2, respectively.
    Is this rigth? Well, that is at least what I observed. The admin docs
    regarding deploying was not clear on what is defined as "name" or where
    it gets it from ... until I tried the above.
    For a while, I thought that the application's root are defined by the
    servlet spec.
    John
    Gene Chuang wrote:
    >
    Servlets in 6.0 must be deployed in .war; "document root" setting is irrelevant in 6.0.
    Gene
    "suresh wilson" <[email protected]> wrote in message news:[email protected]..
    Please reply fast.
    Suresh Wilson
    Homepage: http://homepages.tig.com.au/~jmsalvo/

Maybe you are looking for