Apache new Document Root

While the new version of Apache sets document root at /srv/http. I am aware of at least one package (phpmyadmin) that install in /srv/www. Is there something wrong ?

Pierre wrote:arch-independent packages like phpmyadmin should install to /usr/share. Maybe you should file a bug report about this issue. (imho /srv/http or anything else in /srv shouldn't be "filled" by any package.)
According to this, where do you think Apache should be installed ?

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();
}

Problem with sp11, wl 5.1, apache and server root requests

We have the following server configuration:
Solaris 2.6
Java 1.3.1_02
Weblogic 5.1
Apache 1.3.20
We recently moved from sp9 to sp11, and noticed a change in the behavior of the Apache-WL
bridge (mod_wl_ssl.so).
We have apache running in front of our WL instance. We're planning to offload static
content to apache, but for now, we pass all requests through to weblogic. This means
we don't have any files in Apache's server root. They all are in the (separate) weblogic
root. This has worked fine until sp11. Now, when you make a request to the server
root, ie, http://server.com/ or http://server.com, weblogic's 404 page is returned.
After turning on the debug logs of an sp9 and an sp11 bridge, I think this is what's
happening:
The way we have the bridge pass everything on is with a " MatchExpression * " directive
in the <IfModule mod_weblogic.c> section of our httpd.conf. We've also tested alternatives
using Directory, Location and LocationMatch directives like this:
<LocationMatch "^/">
SetHandler weblogic-handler
</LocationMatch>
and the behavior I'm writing about still remains.
In sp11, when making the root level request, the only request that apache passes
on to wl is a request for the error page set in the default apache config. (I'm looking
at the mod_wl debug logs).
In sp9, you see a request for "/", and wl returns a 302 redirection. The next request
is to "/index.jsp", which returns correctly (a 200 response).
What I think is happening is that mod_wl stopped intercepting the "/" URL request
in sp11. It would then default to apache's mod_dir to lookup an index file for /,
try to find that file in the apache root(internally to mod_dir), not find anything,
since we don't have an index file in the apache server root, then generate a request
for the apache error page, which is then intercepted and passed on to wl. Since wl
doesn't have this file, a 404 is returned. (whew).
Now, if I go to the apache server root, and create an empty index file (>touch index.jsp),
I see one request for "/index.jsp" passed to WL which then returns correctly. Still
no intial request for "/", which leads me to believe mod_dir is still handling the
"/" URL request rather than mod_wl.
Why did this behavior change between service packs, and can it switch back to the
original behavior? I don't like having empty files lying around. Also, I didn't see
this change in behavior documented in any of the release notes.
--peter

I had a similar problem on Redhat Linux 7.1, Java 1.3.1, Apache 1.3.20
doing PathPrepends for a Location directive.
I recently saw they have release SP12 for WL5.1 which addresses
PathPrepend issues. This could be a similar issue
http://www.weblogic.com/docs51/classdocs/SERVICEPACK_README.html
"peter morelli" <[email protected]> wrote in message news:<[email protected]>...
We have the following server configuration:
Solaris 2.6
Java 1.3.1_02
Weblogic 5.1
Apache 1.3.20
We recently moved from sp9 to sp11, and noticed a change in the behavior of the Apache-WL
bridge (mod_wl_ssl.so).
We have apache running in front of our WL instance. We're planning to offload static
content to apache, but for now, we pass all requests through to weblogic. This means
we don't have any files in Apache's server root. They all are in the (separate) weblogic
root. This has worked fine until sp11. Now, when you make a request to the server
root, ie, http://server.com/ or http://server.com, weblogic's 404 page is returned.
After turning on the debug logs of an sp9 and an sp11 bridge, I think this is what's
happening:
The way we have the bridge pass everything on is with a " MatchExpression * " directive
in the <IfModule mod_weblogic.c> section of our httpd.conf. We've also tested alternatives
using Directory, Location and LocationMatch directives like this:
<LocationMatch "^/">
SetHandler weblogic-handler
</LocationMatch>
and the behavior I'm writing about still remains.
In sp11, when making the root level request, the only request that apache passes
on to wl is a request for the error page set in the default apache config. (I'm looking
at the mod_wl debug logs).
In sp9, you see a request for "/", and wl returns a 302 redirection. The next request
is to "/index.jsp", which returns correctly (a 200 response).
What I think is happening is that mod_wl stopped intercepting the "/" URL request
in sp11. It would then default to apache's mod_dir to lookup an index file for /,
try to find that file in the apache root(internally to mod_dir), not find anything,
since we don't have an index file in the apache server root, then generate a request
for the apache error page, which is then intercepted and passed on to wl. Since wl
doesn't have this file, a 404 is returned. (whew).
Now, if I go to the apache server root, and create an empty index file (>touch index.jsp),
I see one request for "/index.jsp" passed to WL which then returns correctly. Still
no intial request for "/", which leads me to believe mod_dir is still handling the
"/" URL request rather than mod_wl.
Why did this behavior change between service packs, and can it switch back to the
original behavior? I don't like having empty files lying around. Also, I didn't see
this change in behavior documented in any of the release notes.
--peter

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

"New Document" button on ribbon not working in the "Master Page Gallery" in Internet Explorer 10 & 11

I'm trying to add a "JavaScript Display Template" to my "Master Page Gallery" but when I click on the "New Document" button and select "JavaScript Display Template" it opens the "Add a master page" dialog
and prompts me to upload a file. I've ran into this problem with "Compatibility View" set to both "On" or "Off". I'm able to upload files but I can't get the new forms to show up.
This happens on the root site collection site. For subsites, the "New Document" button is completely grayed out.
FYI - I am a site collection admin and in the "Owners" group for each site.
How can I fix this?

Hi,
According to your post, my understanding is that "New Document" button on ribbon falied to work in the "Master Page Gallery".
In the root site, please make sure you enter all the necessary information when you upload file.
In the other word, you need to make sure the save the “JavaScript Display Template" successfully.
In the subsites, when you click the “Master Page” under Master Page Gallery in the sub site site setting page, the "New Document" button is completely grayed out.
If you want to add the template, you need to active the “SharePoint Server Publishing” feature in the Site sitting->Manage site features.
However, the “Master Page” under Master Page Gallery will become to “Master pages and page layouts”.
If you click the Master pages and page layouts”, you will go to the
Master Page Gallery of the root site, and then you can add Document.
Thank you for your understanding.
Thanks,
Linda Li
Linda Li
TechNet Community Support

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.

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/

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

Problems while accessing images outside the web document-root folder

Our application runs on Oracle application server on Linux. Facing problems while accessing images outside the web document-root folder. This works with changes in global-web-application.xml by including the <virtual-directory> tag. The same change does not work when done on Linux machine. It is unable to find the image. Please help in resolving this issue.
</locale-encoding-mapping>
</locale-encoding-mapping-list>
</web-app>
<virtual-directory virtual-path="/img" real-path="/home/eposuat/" />
</orion-web-app>
Code in the jsp:
<img width=700 height=700 src="/img/3.tif"></img>
<img width=700 height=700 src="/img/WB.gif"></img>

This is one of the least satisfactory aspects of site management in Dreamweaver, and several developers, including myself, have been pressuring the Dreamweaver team for some years to improve this. Who knows? They might eventually take notice.
The only way to do this at the moment is to create two site definitions, one nested inside the other. Set up the site definition normally based on htdocs as your site root. Then create a new site definition based on site. Dreamweaver will nag you that it can cause problems, but it won't actually stop you from doing it. The only potential problem is with site synchronization.
The problem with using site as the only basis for your site definition is that Dreamweaver automatically puts things like the Connections, Scripts, and other folders in the site root. So, everything ends up at the wrong level of the site hierarchy. Quite frankly, the whole thing is a bit of a pain. Dynamic site development was added to Dreamweaver only in version 6 (Dreamweaver MX), and no one had really thought through the need to store files outside the site root.

WL 8.1: Configuring a document root for multiple web applcations in a domain

Subject: Application - document root
I am using the Apache web server with the BEA proxy plug-in. All requests to the
apache server are proxied to WebLogic.
http://localhost/wip-gl/xxx.jsp?param1...
http://localhost/wip-am/xxx.jsp?param1...
http://localhost/stg-gl/xxx.jsp?param1...
etc
For weblogic I have a domain where I have deployed 6 web applications. Each application
represents a web site.
.../wip-gl
.../wip-am
.../stg-gl
etc
But when processing jsp's it appears that the document root (web root) is not
defined correctly.
For each application how do I define the document root?
Thanks for the help.

Distributed sessions has nothing to do with different web applications. The concept is about distributing load for the same application between several appserver instances running on the same box(different jvm) or on some other box in the network.
What you used with iAS 6.5 is not available in 8.1 because sharing sessions between web apps is forbidden by the servlet spec. You should consider repackaging your apps. into a single web app. or using other way of signing/verifying user identity(check Sun Access Manager for example).
Have a look at this thread as well: http://swforum.sun.com/jive/thread.jspa?threadID=100931

Multiple document roots on one instance of weblogic server..

Hi,
Is it possible to configure multiple document roots for one weblogic server?
Here is my situation...
We have a sun box which is having 4 IP addresses. We would like to have a
document root for each IP address, but we want to run a SINGLE weblogic
server instance..
Any help is appriciated..
thx

check this out for more info:
http://www.weblogic.com/docs51/admindocs/properties.html#multihoming
"Mauricio Del Moral" <[email protected]> wrote in message
news:3977759c$[email protected]..
Hi,!
I'm afraid not, but that would be great.

Document root element

When starting Sun One Application Server 7 I get the following error in the console:
SEVERE ( 5028): ContextConfig[ROOT] Parse error in application web.xml
org.xml.sax.SAXParseException: Document root element "web-app", must match DOCTYPE root "null".
What does this error mean and how do I fix?
My web.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee      http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
version="2.4">
<display-name>My appliation</display-name>
<description>My appliation</description>
<context-param>
    <param-name>log4j-file</param-name>
    <param-value>WEB-INF/log4j.properties</param-value>
</context-param>
<listener>
    <listener-class>
      com.gh.web.listener.Listener
    </listener-class>
</listener>
<servlet>
    <servlet-name>action</servlet-name>
    <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
    <init-param>
      <param-name>config</param-name>
      <param-value>/WEB-INF/struts-config.xml</param-value>
    </init-param>
    <init-param>
      <param-name>debug</param-name>
      <param-value>0</param-value>
    </init-param>
    <load-on-startup>2</load-on-startup>
</servlet>
<jsp-config>
    <taglib>
      <taglib-uri>/tags/common</taglib-uri>
      <taglib-location>/WEB-INF/tld/common.tld</taglib-location>
    </taglib>
</jsp-config>
</web-app>

If running on Tomcat Server, then is start without errors.
I made a following change in web.xml and error is disappeared:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN'
'http://java.sun.com/j2ee/dtds/web-app_2_3.dtd'>
<web-app>
</web-app>The reason for the 'break' is because I attempting to deploy a web application following the 2.4 spec that Sun One Application Server 7 does not support or why?

"new document or drag files here" not visible

Hi,
I gave "Collaboration" permission to Visitors (read only users) in a document library
sub folder.
My problem is:
users can't see the "new document or drag files here" option, so the only way to upload a file is in the ribbon: "File" -> "Upload document"
That's confusing for the users.
Setting Collaboration on the entire doc lib will solve the issue but users will be able to add/edit/delete on the root folder.
Is there a way to see the "new document" option or avoid collaboration on the root folder?

I ended up creating an event handler, I think it's the only way...
So:
I've created a new permission level for visitors called "Insert" that is Read + Add Items
I've created an event receiver on the Document library that disables collaboration only inside the root folder
Here's the code:
using System;
using System.Security.Permissions;
using Microsoft.SharePoint;
using Microsoft.SharePoint.Utilities;
using Microsoft.SharePoint.Workflow;
namespace Extranet.EventReceivers.EventReceiverAreeScambio
/// <summary>
/// List Item Events
/// </summary>
public class EventReceiverAreeScambio : SPItemEventReceiver
/// <summary>
/// An item is being added.
/// </summary>
public override void ItemAdding(SPItemEventProperties properties)
base.ItemAdding(properties);
ValidaPosizione(properties, "Non puoi aggiungere file nella cartella di base, inseriscili solo all'interno delle sotto aree.");
/// <summary>
/// An item is being deleted
/// </summary>
public override void ItemDeleting(SPItemEventProperties properties)
base.ItemDeleting(properties);
ValidaPosizione(properties, "Non puoi eliminare file in questa cartella.");
/// <summary>
/// An item is being updated
/// </summary>
public override void ItemUpdating(SPItemEventProperties properties)
base.ItemUpdating(properties);
ValidaPosizione(properties, "Non puoi modificare file in questa cartella.");
private static void ValidaPosizione(SPItemEventProperties properties, string errorMessage)
string totalpath = properties.AfterUrl;
string[] test = totalpath.Split('/');
if (test.Length < 3 && !properties.Web.CurrentUser.IsSiteAdmin)
properties.Status = SPEventReceiverStatus.CancelWithError;
properties.ErrorMessage = errorMessage;

Add an existing Element to a new Document

I want to use the appendChild and add an Element to a Document but when the Element comes from another Document it refuses to add it.
How can I add an already existing Element with all its children to a new Document? It seems that you can do that only with the elements that you have created with createElement of the new Document.

did it yesterday :-)
what I did was...
Node tmpNode = document_destination.importNode(document_source.getFirstChild(),true);
document_destination.appendChild(Node);use importNode to copy the Node from the origin document to the destination document ( the true flag means "import the Node and all subnodes"). Once you have the Node in the destination document, you must append it somewhere in the hierarchy (in the example, it will be a child of the root Node)
hope it helps!

Apache new Document Root

Similar Messages

Maybe you are looking for