Debug two document roots in JDeveloper

I have the following situation.
I have a JSP-project called Admin. All references to admin are made like http://x.y.z/Admin/Login/Login.jsp etc.
Some of the JSP-pages have included static images, stylesheets and javascripts that are fetched from a separate root called Static (we also have ha User JSP project).
When I start my Admin JSP-project in the internal OC4J in JDeveloper it cannot find the images, scripts etc in Static (e.g. /Static/scripts/validate.js) since I started the Admin-project.
I have not found any way to add a /Static root to the internal OC4J. Is that possible?
The code I'm debugging is a large older project so I'm not able to rewrite the /Static/.. references to something like /Admin/Static/.. which would solve my problem.
Thanks in advance for any help.
/Jan-Erik

Fixed with OSS Note

Similar Messages

[CS3 JS] Working with two documents of the same name

I work with sets of documents that use standardized names. I'm trying to write a script that compares two documents from different sets. Because the source and the target documents both have the same name, I've encountered some disturbing behavior that reminds me of the app.activeWindow bug that Dave has written about. (
Dave Saunders, "Scripting FAQ as Wiki" #14, 15 Oct 2007 12:19 pm)
To perform the comparison, I have to grab a reference to the same region of text in both documents, as offset from regular landmarks. I was just patting myself on the back for figuring out the "story.characters.itemByRange(begin, end).texts[0]" acrobatics required, when I discovered that my text objects were magically "dissolving" into invalid objects.
After a lot of debugging and attempts to hack around the problem (i.e. storing the text begin/end indices and not grabbing the text object until the last possible moment), I've narrowed it down to the references to the source and target documents. I've watched the reference variable to the source document *change* to instead reference the target document when I start accessing the target document object. Once this happens, any text objects belonging to the source document become invalid, as if the source document had been closed.
Is there any way around this? I've thought about temporarily saving the files to different names, but I haven't tried it yet.
Here's a script that demonstrates the problem (you'll have to find your own same-named documents if you want to run it):
var source = "/Users/deyk/Desktop/test/source";
var target = "/Users/deyk/Desktop/test/target";
function findChapters(in_doc) {
app.findGrepPreferences = NothingEnum.nothing;
app.findGrepPreferences.appliedCharacterStyle = "chapter-num";
app.findGrepPreferences.findWhat = "\\d+";
return in_doc.findGrep();
var sdoc = app.open(File(source+"/01.Genesis.indd"));
var s_file_start = sdoc.fullName;
var s_chs = findChapters(sdoc);
var s_story = s_chs[0].parentStory;
var s_txt = s_story.characters.itemByRange(s_chs[0].index,
s_chs[1].index-1).texts[0];
var tdoc = app.open(File(target+"/01.Genesis.indd"));
// At this point, sdoc now references tdoc instead.
// s_txt, s_story, and s_chs become invalid objects.
var t_file_start = tdoc.fullName;
var t_chs = findChapters(tdoc);
var t_story = t_chs[0].parentStory;
var t_txt = t_story.characters.itemByRange(t_chs[0].index,
t_chs[1].index-1).texts[0];
var s_file_end = sdoc.fullName;
if (s_file_end.name != s_file_start.name) {
var result = "What a nasty bug!";
"Finished";

I've tried saving the document to a temporary name, and it works satisfactorily:
function openFileAsTemp(a_file) {
var tmp_folder = Folder.temp.fullName;
var date = new Date();
var temp_file = File(tmp_folder+'/'+date.valueOf()+'_'+a_file.name);
var doc = app.open(a_file);
doc = doc.save(temp_file);
return doc;

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.

Set document root for Tomcat

Hello
I want Tomcat to use another document root (where index.html typically resides in). I set
<Host name="localhost" debug="0" appBase="" docBase="d:\WWW" unpackWARs="true">
but I got error
MAPPING configuration error for request URI
Unfortunately, I can't track down the problem, even some articles in this newsgroup explain something like this.
I took care of capitalizing letters.
Thank you for your aid.

Hi,
use:
<Host name="localhost" debug="0" appBase="d:\www" unpackWARs="true">
or:
<Context path="" docBase="d:\www" debug="0"/>
I think the first edit the default directory for all webapps. The second edit the root-doc only for the uri-path "", thats means for "http://localhost:8080" e.g.
Good Luck
Kuno

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?

7210 - Specify different document root for a WAR/exploded application

          Hello,
          I would like to know how to specify a specific directory under my WAR/exploded
          directory as the
          document root instead of the standard application root directory as the document
          root directory.
          The following explains why I need that way..
          Our Source Code Control System consists of the following development directory
          hierarchy..
          /VOB/Application/
          /VOB/Application/Development/source/com/company/... *.java
          /VOB/Application/Development/docs/businessfunctionality1/*.jsp, *.html
          /VOB/Application/Development/docs/businessfunctionality2/*.jsp, *.html
          /VOB/Application/Development/docs/images/*.gif
          /VOB/Application/Development/Web-inf/web.xml
          /VOB/Application/Development/Web-inf/tlds/*.tld
          /VOB/Application/Development/Web-inf/lib/*.jar
          /VOB/Application/Development/Web-inf/classes/com/company/... *.class
          /VOB/Application/Design/*.doc, *.mdl
          With the above structure, the root directory of the applications is /VOB/Application/Development/


Hi,
You can't specify two different context root directly from your application unless until you specify " / " in context root and access application from two different host.
Hope this should give you a clue.
Regards,
Kal

Unable to debug the jspx page on Jdeveloper Studio Edition Version 11.1.1.6.0, Build JDEVADF_11.1.1.6.0_GENERIC_111205.1733.6192.1, using Windows 7 OS

Hi,
I am unable to debug the jspx page on Jdeveloper Studio Edition Version 11.1.1.6.0, Build JDEVADF_11.1.1.6.0_GENERIC_111205.1733.6192.1, using Windows 7 OS.
When right click on jspx page , clicks on Debug option, it gives the following error:
Debugger unable to connect to local process.
[Server Instance IntegratedWebLogicServer is shutting down. All applications currently running will be terminated and undeployed.]
I also restarted the Jdeveloper, even re-installed Jdev but still the problem persist.
Any help is appreciated.
Thanks in advance.

If the jspx page is not part of the adfc-config.xml the page can only be displayed, but the tags will not work as the adf life cycle is not involved. drag te page onto the adfc-config.xml (the unbounded task flow), right click on it and select debug from the context menu.
Main problem is : Weblogic server cannot be started in debug mode.
To check this, open the application navigator, select the integrated server, right click on it and select 'debug' from the context menu.
After a short time you should see some messages and at last you should see <Runnning> in the message log. Now the server runs (without any of your applications, but it runs).
If you done't see the 'Running' message you should see an error, which you should post here.
Timo

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.

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

While doing F-32 residual payment - Two documents generated AB and RV

Hi all,
While Clearing partial payment with respect to Invoice thorough F-32 ( As residual )- Two documents generated AB and RV in development system.
where as in Quality and Production system there is only one AB document generated.
Is it standard behavior to generate AB and RV?
Customer don't what that RV document to be generated.

Hi,
This is one of the option given by SAP to manage your open items in case of partial payments. In this process when you go for residual payment, your original open item against which partial payment is made gets cleared & system automatically creates a new open item with the balance amount.
e.g you have an open item of Rs 10,000/- since 01.03.2014 & today i.e on 01.04.2014 you are making an payment of Rs 6,000/- against the said item & you opt for residual payment. In this case the original open item i.e Rs 10,000/- gets cleared & a new open item of i.e Rs 4,000/- get created . Note that this new open item created by the system will have the new document date (01.04.2014) and new baseline date, i.e here aging of your receivable/payable does not reflects the true picture.
But this is not the case when you opt for partial clearing method. In partial clearing method , the original open item is not cleared, instead both the items are shown as open items.
If you take the case of above example, after making the partial payment of Rs 6,000/- against Rs 10,000/- you will have two open items. One the original one of Rs 10,000/- since 01.03.2014 and another for Rs 6,000/- on 01.04.2014.In this case the aging of your receivable/payable shows the true picture.
Yes its a business decision ,which method to adopt.
Thanks & regards
Deepak

POSTING_INTERFACE_CLEARING - clear two documents

Hi,
I need to create a new program that should be able to clear two documents by comparing the ASSIGNMENT filed of the payment document (DZ) against the REFERENCE field of the installment invoice (II).
I can do this via batch input in FB05 (choosing open item -> Select Document Number in Radio Button -> Enter Account -> Click Process Open Items -> Enter Document Numbers -> Post).
However, I came across the FM POSTING_INTERFACE_CLEARING and tried to use it. Unfortunately, I was not successful in using this to clear the items that I need to clear.
Do you think I can use the said FM for clearing two open items to produce one clearing doc using the document number?
Can you please provide sample code if you have one?
Thank you very much in advance for your inputs.
Best regards.
Brando

Please be informed informed that the invoice and payment are already present in table BSID. I would just need to clear them in my custom program. Thanks.

How to change the color of letters instead of highlight the text when compare two documents

Hello!!
I have the Adobe Acrobat 9 Pro (Versión 9.0.0) and I need to compare two documents, but I want to show the diferences changing the color of letters instead of highlight the text with any color. My boss tell me that other Acrobat version have this option, but I couldn't find it in this version.
Could you help me on this topic??
Thanks

Hello!!
I have the Adobe Acrobat 9 Pro (Versión 9.0.0) and I need to compare two documents, but I want to show the diferences changing the color of letters instead of highlight the text with any color. My boss tell me that other Acrobat version have this option, but I couldn't find it in this version.
Could you help me on this topic??
Thanks

The same delivery in two document for shipment

Hello,
I wonder if there is a way to block the delivery if it is already in another document shipment. Is there any way in customizing? Because the way it is configured the system is allowing a single delivery is contained in two documents of freight transport and calculating twice.
observation - the delivery is not split.
Thanks,
Tatiane

Hi,
In standard system I'm not aware of any setting that would restrict the assignemnt of one delivery to several shipment.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/5f/e411bb044411d2bf5d0000e8a7386f/frameset.htm
Since a delivery for which the billing document is to be created can be part of several shipments (for example, in the case of a transportation chain), it can happen that several shipment cost documents need to be calculated so that the billing document itself can at all be created.
I guess you have to:
- use proper selection criteria when assigning deliveries to the shipment (e.g. proper transportation planning status (VBUK-TRSTA) --> you can define variants)
- go to development (SPRO > LE > Transportation > System Modifications > User Exits for Transportation + SPRO > LE > Transportation > System Modifications > Biusiness Add-In in Transportation)
In Is-Oil there are built in checks:
http://help.sap.com/saphelp_erp60_sp/helpdata/en/70/23d610419311d2ac100000e829fbfe/frameset.htm
Regards,
Csaba
Edited by: Csaba Szommer on Jan 19, 2010 8:53 PM

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

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

Debug two document roots in JDeveloper

Similar Messages

Maybe you are looking for