Help Me what is the "Parse Error: com.sun.xml.parser/P-067"?

OS: Window 2000 (it will be changed HP-UX 11)
Web Server: iPlanet 4.1 SP14
DB Server : Oracle 8i
JDK: 1.2.2_017
Tag Library : jakarta-taglibs-dbtags-1.0.0 (http://jakarta.apache.org/taglibs/doc/dbtags-doc/intro.html)
DTD file: web-jsptaglib_1_1.dtd ( actually, jakarta used http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd, but that dosen't work in iPlanet 4.1 SP 14. so i changed the path of dtd location to web-jsptaglib_1_1.dtd like the following tld file.)
How should I use Jakarta DB Tag Library in iPlanet 4.1 SP? I'm very tired to set all of thses stupid things!
I can't use Tag Library in iPlanet 4.1 SP 14
Any comments make me happy~!
Please, help me~!
■ Error Message
[15/3/2005:20:21:41] info ( 4552): Internal Info: loading servlet /test/jdbc5.jsp
[15/3/2005:20:21:42] info ( 4552): JSP: JSP1x compiler threw exception
org.apache.jasper.JasperException: Unable to open taglibrary http://localhost/tlds/dbtags5.jar : Parse Error in the tag library descriptor: com.sun.xml.parser/P-067
 at org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspParseEventListener.java, Compiled Code)
 at org.apache.jasper.compiler.DelegatingListener.handleDirective(DelegatingListener.java:119)
 at org.apache.jasper.compiler.Parser$Directive.accept(Parser.java, Compiled Code)
 at org.apache.jasper.compiler.Parser.parse(Parser.java, Compiled Code)
 at org.apache.jasper.compiler.Parser.parse(Parser.java:1022)
 at org.apache.jasper.compiler.Parser.parse(Parser.java:1018)
 at org.apache.jasper.compiler.Compiler.compile(Compiler.java, Compiled Code)
 at com.netscape.server.http.servlet.NSServletEntity.load(NSServletEntity.java:231)
 at com.netscape.server.http.servlet.NSServletEntity.update(NSServletEntity.java:149)
 at com.netscape.server.http.servlet.NSServletRunner.Service(NSServletRunner.java:453)
■ TLD File
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE taglib
PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.2//EN"
 "http://localhost/dtd/web-jsptaglib_1_1.dtd">


<taglib>
 <tlibversion>1.0</tlibversion>
<jspversion>1.1</jspversion>
<prefix>DBTag</prefix>
<urn></urn>
<info>
 A simple db tab library for the examples
</info>
<tag>
<name>connection</name>
<tagclass>org.apache.taglibs.dbtags.connection.ConnectionTag</tagclass>
<teiclass>org.apache.taglibs.dbtags.connection.ConnectionTEI</teiclass>
<bodycontent>JSP</bodycontent>
<attribute>
<name>id</name>
<required>yes</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>dataSource</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>jndiName</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
</tag>
<tag>
<name>url</name>
<tagclass>org.apache.taglibs.dbtags.connection.DatabaseURLTag</tagclass>
<bodycontent>JSP</bodycontent>
<attribute>
<name>initParameter</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
</tag>
<tag>
<name>jndiName</name>
<tagclass>org.apache.taglibs.dbtags.connection.JndiNameTag</tagclass>
<bodycontent>JSP</bodycontent>
<attribute>
<name>initParameter</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
</tag>
<tag>
<name>driver</name>
<tagclass>org.apache.taglibs.dbtags.connection.DriverTag</tagclass>
<bodycontent>JSP</bodycontent>
<attribute>
<name>initParameter</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
</tag>
<tag>
<name>userId</name>
<tagclass>org.apache.taglibs.dbtags.connection.UserIdTag</tagclass>
<bodycontent>JSP</bodycontent>
<attribute>
<name>initParameter</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
</tag>
<tag>
<name>password</name>
<tagclass>org.apache.taglibs.dbtags.connection.PasswordTag</tagclass>
<bodycontent>JSP</bodycontent>
<attribute>
<name>initParameter</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
</tag>
<tag>
<name>closeConnection</name>
<tagclass>org.apache.taglibs.dbtags.connection.CloseConnectionTag</tagclass>
<bodycontent>empty</bodycontent>
<attribute>
<name>conn</name>
<required>yes</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
</tag>
<tag>
<name>statement</name>
<tagclass>org.apache.taglibs.dbtags.statement.StatementImplTag</tagclass>
<teiclass>org.apache.taglibs.dbtags.statement.StatementTEI</teiclass>
<bodycontent>JSP</bodycontent>
<attribute>
<name>id</name>
<required>yes</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>conn</name>
<required>yes</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
</tag>
<tag>
<name>escapeSql</name>
<tagclass>org.apache.taglibs.dbtags.statement.EscapeSQLTag</tagclass>
<bodycontent>JSP</bodycontent>
</tag>
<tag>
<name>query</name>
<tagclass>org.apache.taglibs.dbtags.statement.QueryTag</tagclass>
<bodycontent>JSP</bodycontent>
</tag>
<tag>
<name>execute</name>
<tagclass>org.apache.taglibs.dbtags.statement.ExecuteTag</tagclass>
<bodycontent>JSP</bodycontent>
<attribute>
<name>ignoreErrors</name>
<required>no</required>
<rtexprvalue>yes</rtexprvalue>
</attribute>
</tag>
<tag>
<name>preparedStatement</name>
<tagclass>org.apache.taglibs.dbtags.preparedstatement.PreparedStatementImplTag</tagclass>
<teiclass>org.apache.taglibs.dbtags.preparedstatement.PreparedStatementTEI</teiclass>
<bodycontent>JSP</bodycontent>
<attribute>
<name>id</name>
<required>yes</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>conn</name>
<required>yes</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
</tag>
<tag>
<name>setColumn</name>
<tagclass>org.apache.taglibs.dbtags.preparedstatement.SetColumnTag</tagclass>
<bodycontent>JSP</bodycontent>
<attribute>
<name>position</name>
<required>yes</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
</tag>
<tag>
<name>resultSet</name>
<tagclass>org.apache.taglibs.dbtags.resultset.ResultSetTag</tagclass>
<teiclass>org.apache.taglibs.dbtags.resultset.ResultSetTEI</teiclass>
<bodycontent>JSP</bodycontent>
<attribute>
<name>id</name>
<required>yes</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>loop</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>name</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>scope</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
</tag>
<tag>
<name>wasNull</name>
<tagclass>org.apache.taglibs.dbtags.resultset.WasNullTag</tagclass>
<bodycontent>JSP</bodycontent>
</tag>
<tag>
<name>wasNotNull</name>
<tagclass>org.apache.taglibs.dbtags.resultset.WasNotNullTag</tagclass>
<bodycontent>JSP</bodycontent>
</tag>
<tag>
<name>getColumn</name>
<tagclass>org.apache.taglibs.dbtags.resultset.GetColumnTag</tagclass>
<teiclass>org.apache.taglibs.dbtags.resultset.BaseGetterTEI</teiclass>
<bodycontent>empty</bodycontent>
<attribute>
<name>position</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>colName</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>to</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>scope</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
</tag>
<tag>
<name>getNumber</name>
<tagclass>org.apache.taglibs.dbtags.resultset.GetNumberTag</tagclass>
<teiclass>org.apache.taglibs.dbtags.resultset.BaseGetterTEI</teiclass>
<bodycontent>empty</bodycontent>
<attribute>
<name>position</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>colName</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>to</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>scope</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>locale</name>
<required>no</required>
<rtexprvalue>yes</rtexprvalue>
</attribute>
<attribute>
<name>format</name>
<required>no</required>
<rtexprvalue>yes</rtexprvalue>
</attribute>
</tag>
<tag>
<name>getTime</name>
<tagclass>org.apache.taglibs.dbtags.resultset.GetTimeTag</tagclass>
<teiclass>org.apache.taglibs.dbtags.resultset.BaseGetterTEI</teiclass>
<bodycontent>empty</bodycontent>
<attribute>
<name>position</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>colName</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>to</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>scope</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>locale</name>
<required>no</required>
<rtexprvalue>yes</rtexprvalue>
</attribute>
<attribute>
<name>format</name>
<required>no</required>
<rtexprvalue>yes</rtexprvalue>
</attribute>
</tag>
<tag>
<name>getTimestamp</name>
<tagclass>org.apache.taglibs.dbtags.resultset.GetTimestampTag</tagclass>
<teiclass>org.apache.taglibs.dbtags.resultset.BaseGetterTEI</teiclass>
<bodycontent>empty</bodycontent>
<attribute>
<name>position</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>colName</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>to</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>scope</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>locale</name>
<required>no</required>
<rtexprvalue>yes</rtexprvalue>
</attribute>
<attribute>
<name>format</name>
<required>no</required>
<rtexprvalue>yes</rtexprvalue>
</attribute>
</tag>
<tag>
<name>getDate</name>
<tagclass>org.apache.taglibs.dbtags.resultset.GetDateTag</tagclass>
<teiclass>org.apache.taglibs.dbtags.resultset.BaseGetterTEI</teiclass>
<bodycontent>empty</bodycontent>
<attribute>
<name>position</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>colName</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>to</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>scope</name>
<required>no</required>
<rtexprvalue>no</rtexprvalue>
</attribute>
<attribute>
<name>locale</name>
<required>no</required>
<rtexprvalue>yes</rtexprvalue>
</attribute>
<attribute>
<name>format</name>
<required>no</required>
<rtexprvalue>yes</rtexprvalue>
</attribute>
</tag>
<tag>
<name>wasEmpty</name>
<tagclass>org.apache.taglibs.dbtags.resultset.WasEmptyTag</tagclass>
<bodycontent>JSP</bodycontent>
</tag>
<tag>
<name>wasNotEmpty</name>
<tagclass>org.apache.taglibs.dbtags.resultset.WasNotEmptyTag</tagclass>
<bodycontent>JSP</bodycontent>
</tag>
<tag>
<name>rowCount</name>
<tagclass>org.apache.taglibs.dbtags.resultset.RowCountTag</tagclass>
<bodycontent>empty</bodycontent>
</tag>
</taglib>

Googling I get this....
P-067 = Document root element is missing.

Similar Messages

Web Service error com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStack

Hi,
I have implemented a Java class which calls some XML RPC 3.0 proxy methods.
If I test the method input inside a "main ()" method and get the output, it works nice.
The XML RPC 3.0 procy method is also invoked and there is no problem.
However, when I expose this java class as a "web service" and invoke the web service from the JDeveloper integrated console or
even an external test client running on a browser, I get the error mentioned below.
Which setting must be defined in the JDevelopper ( Studio Edition Version 11.1.1.2.0 on :
set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false"
class="java.lang.NoClassDefFoundError"
+++++++++ Integrated WebLogic server ( + Integrated WebLogic server started on port 7101) +++++++++
[Running application AllCustomers on Server Instance IntegratedWebLogicServer...]
[02:47:42 PM] ---- Deployment started. ----
[02:47:42 PM] Target platform is (Weblogic 10.3).
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Thanks
YL
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
<faultcode>S:Server</faultcode>
<faultstring>org/opensource/proxy/OpenSourceApiXmlRpcProxy</faultstring>
<detail>
<ns2:exception xmlns:ns2="http://jax-ws.dev.java.net/" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" class="java.lang.NoClassDefFoundError">
<message>org/opensource/proxy/OpenSourceApiXmlRpcProxy</message>
<ns2:stackTrace>
<ns2:frame line="246" file="GetAllCustomers.java" method="GetOneCustomerWithProxy" class="com.std.customer.GetAllCustomers" />
<ns2:frame line="native" file="NativeMethodAccessorImpl.java" method="invoke0" class="sun.reflect.NativeMethodAccessorImpl" />
<ns2:frame line="39" file="NativeMethodAccessorImpl.java" method="invoke" class="sun.reflect.NativeMethodAccessorImpl" />
<ns2:frame line="25" file="DelegatingMethodAccessorImpl.java" method="invoke" class="sun.reflect.DelegatingMethodAccessorImpl" />
<ns2:frame line="597" file="Method.java" method="invoke" class="java.lang.reflect.Method" />
<ns2:frame line="101" file="WLSInstanceResolver.java" method="invoke" class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" />
<ns2:frame line="83" file="WLSInstanceResolver.java" method="invoke" class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" />
<ns2:frame line="152" file="InvokerTube.java" method="invoke" class="com.sun.xml.ws.server.InvokerTube$2" />
<ns2:frame line="264" file="EndpointMethodHandler.java" method="invoke" class="com.sun.xml.ws.server.sei.EndpointMethodHandler" />
<ns2:frame line="93" file="SEIInvokerTube.java" method="processRequest" class="com.sun.xml.ws.server.sei.SEIInvokerTube" />
<ns2:frame line="604" file="Fiber.java" method="__doRun" class="com.sun.xml.ws.api.pipe.Fiber" />
<ns2:frame line="563" file="Fiber.java" method="_doRun" class="com.sun.xml.ws.api.pipe.Fiber" />
<ns2:frame line="548" file="Fiber.java" method="doRun" class="com.sun.xml.ws.api.pipe.Fiber" />
<ns2:frame line="445" file="Fiber.java" method="runSync" class="com.sun.xml.ws.api.pipe.Fiber" />
<ns2:frame line="275" file="WSEndpointImpl.java" method="process" class="com.sun.xml.ws.server.WSEndpointImpl$2" />
<ns2:frame line="454" file="HttpAdapter.java" method="handle" class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" />
<ns2:frame line="250" file="HttpAdapter.java" method="handle" class="com.sun.xml.ws.transport.http.HttpAdapter" />
<ns2:frame line="140" file="ServletAdapter.java" method="handle" class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" />
<ns2:frame line="319" file="HttpServletAdapter.java" method="run" class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" />
<ns2:frame line="232" file="HttpServletAdapter.java" method="post" class="weblogic.wsee.jaxws.HttpServletAdapter" />
<ns2:frame line="310" file="JAXWSServlet.java" method="doPost" class="weblogic.wsee.jaxws.JAXWSServlet" />
<ns2:frame line="727" file="HttpServlet.java" method="service" class="javax.servlet.http.HttpServlet" />
<ns2:frame line="87" file="JAXWSServlet.java" method="service" class="weblogic.wsee.jaxws.JAXWSServlet" />
<ns2:frame line="820" file="HttpServlet.java" method="service" class="javax.servlet.http.HttpServlet" />
<ns2:frame line="227" file="StubSecurityHelper.java" method="run" class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" />
<ns2:frame line="125" file="StubSecurityHelper.java" method="invokeServlet" class="weblogic.servlet.internal.StubSecurityHelper" />
<ns2:frame line="292" file="ServletStubImpl.java" method="execute" class="weblogic.servlet.internal.ServletStubImpl" />
<ns2:frame line="26" file="TailFilter.java" method="doFilter" class="weblogic.servlet.internal.TailFilter" />
<ns2:frame line="56" file="FilterChainImpl.java" method="doFilter" class="weblogic.servlet.internal.FilterChainImpl" />
<ns2:frame line="326" file="DMSServletFilter.java" method="doFilter" class="oracle.dms.wls.DMSServletFilter" />
<ns2:frame line="56" file="FilterChainImpl.java" method="doFilter" class="weblogic.servlet.internal.FilterChainImpl" />
<ns2:frame line="3592" file="WebAppServletContext.java" method="run" class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" />
<ns2:frame line="321" file="AuthenticatedSubject.java" method="doAs" class="weblogic.security.acl.internal.AuthenticatedSubject" />
<ns2:frame line="121" file="SecurityManager.java" method="runAs" class="weblogic.security.service.SecurityManager" />
<ns2:frame line="2202" file="WebAppServletContext.java" method="securedExecute" class="weblogic.servlet.internal.WebAppServletContext" />
<ns2:frame line="2108" file="WebAppServletContext.java" method="execute" class="weblogic.servlet.internal.WebAppServletContext" />
<ns2:frame line="1432" file="ServletRequestImpl.java" method="run" class="weblogic.servlet.internal.ServletRequestImpl" />
<ns2:frame line="201" file="ExecuteThread.java" method="execute" class="weblogic.work.ExecuteThread" />
<ns2:frame line="173" file="ExecuteThread.java" method="run" class="weblogic.work.ExecuteThread" />
</ns2:stackTrace>
</ns2:exception>
</detail>
</S:Fault>
</S:Body>
</S:Envelope>

Hello AYVR
I found your post because I want to suppress the stack trace in my response of the web service. I put the -Dcom.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace=false parameter in the setDomainEnv.cmd in the bin directory of my domain. Maybe this is also a solution for you.
Cheers Chris
Edited by: user8989253 on Aug 5, 2011 6:36 AM

What are the general errors will come in data uploading

Hi Friends,
What are the general errors will come in data uploading
Thanks in Advance

Paul
It all depends on how we configure the system. Errors may be different for different scenerios like
User ALEROMOTE Loacked for master data's
Data Sourcs has to be replicated
Activation Failures
Error occures in data Selection Etc.
Do you have any specific error so that we can work on that.
Thanks
Sat

What are the common error while EBS installation in Unix /windows

what are the common error while EBS R12 installation with os unix and windows.
oracle have any any check after installation all installation are correct according to no of directory, files and file size ?
regards

Hi user;
what are the common error while EBS R12 installation with os unix and windows.AFAIK there is no document which show common error.There are some common error for installation like:
RW-5004- RW-50010 etc.
For error we have to check instalaltion log files for can get more details about it
oracle have any any check after installation all installation are correct according to no of directory, files and file size ?Oracle has 2 checking mechanisim during installation.
1. Before start installation, rapidwiz makes Validate system Configuration check which is checking port avaliability,file system check etc.
2. End of the installation,rapidwiz makes Validate system Configuration again to check jsp,dbc file, db avaliablity etc..
For more details Please check:
For r12.1.1:
http://download.oracle.com/docs/cd/B53825_01/current/html/docset.html
For r12:
http://download.oracle.com/docs/cd/B40089_10/current/html/docset.html
Hope it helps
Regard
Helios

Error in parsing: SAX2 driver class com.sun.xml.parser not found

Hi I have this exception
Error in parsing: SAX2 driver class com.sun.xml.parser not found
when I try to run the examples from the book xml and java
I have added the following jar files to the class path that i have download form java.sun.com
xml.jar
xalan.jar
jaxp.jar
crimson.jar
Please can anyone tell me what is missing or wrong..the code must be right since written by oreilly... please have u any ideA
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");//
I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..to com.sun.xml.parser
THIS IS THE ALL CODE
import java.io.IOException;
import org.xml.sax.Attributes;
import org.xml.sax.ContentHandler;
import org.xml.sax.ErrorHandler;
import org.xml.sax.Locator;
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
import org.xml.sax.XMLReader;
import org.xml.sax.helpers.XMLReaderFactory;
import org.xml.sax.*;
* <code>SAXParserDemo</code> will take an XML file and parse it using SAX,
* displaying the callbacks in the parsing lifecycle.
* @author Brett McLaughlin
* @version 1.0
public class SAXParserDemo {
* 
* This parses the file, using registered SAX handlers, and output
* the events in the parsing process cycle.
* 
* @param uri <code>String</code> URI of file to parse.
public void performDemo(String uri) {
System.out.println("Parsing XML File: " + uri + "\n\n");
// Get instances of our handlers
ContentHandler contentHandler = new MyContentHandler();
ErrorHandler errorHandler = new MyErrorHandler();
try {
// Instantiate a parser
XMLReader parser =
XMLReaderFactory.createXMLReader(
// "org.apache.xerces.parsers.SAXParser");
"com.sun.xml.parser");// I HAVE ONLY CHANGED THIS LINE FROM THE apache parser..
// Register the content handler
parser.setContentHandler(contentHandler);
// Register the error handler
parser.setErrorHandler(errorHandler);
// Parse the document
parser.parse(uri);
} catch (IOException e) {
System.out.println("Error reading URI: " + e.getMessage());
} catch (SAXException e) {
System.out.println("Error in parsing: " + e.getMessage());
* 
* This provides a command line entry point for this demo.
* 
public static void main(String[] args) {
// if (args.length != 1) {
// System.out.println("Usage: java SAXParserDemo [XML URI]");
// System.exit(0);
//String uri = args[0];
SAXParserDemo parserDemo = new SAXParserDemo();
parserDemo.performDemo("content.xml");
* <code>MyContentHandler</code> implements the SAX
* <code>ContentHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's content.
class MyContentHandler implements ContentHandler {
/** Hold onto the locator for location information */
private Locator locator;
* 
* Provide reference to <code>Locator</code> which provides
* information about where in a document callbacks occur.
* 
* @param locator <code>Locator</code> object tied to callback
* process
public void setDocumentLocator(Locator locator) {
System.out.println(" * setDocumentLocator() called");
// We save this for later use if desired.
this.locator = locator;
* 
* This indicates the start of a Document parse - this precedes
* all callbacks in all SAX Handlers with the sole exception
* of <code>{@link #setDocumentLocator}</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void startDocument() throws SAXException {
System.out.println("Parsing begins...");
* 
* This indicates the end of a Document parse - this occurs after
* all callbacks in all SAX Handlers.</code>.
* 
* @throws <code>SAXException</code> when things go wrong
public void endDocument() throws SAXException {
System.out.println("...Parsing ends.");
* 
* This will indicate that a processing instruction (other than
* the XML declaration) has been encountered.
* 
* @param target <code>String</code> target of PI
* @param data <code>String</code containing all data sent to the PI.
* This typically looks like one or more attribute value
* pairs.
* @throws <code>SAXException</code> when things go wrong
public void processingInstruction(String target, String data)
throws SAXException {
System.out.println("PI: Target:" + target + " and Data:" + data);
* 
* This will indicate the beginning of an XML Namespace prefix
* mapping. Although this typically occur within the root element
* of an XML document, it can occur at any point within the
* document. Note that a prefix mapping on an element triggers
* this callback before the callback for the actual element
* itself (<code>{@link #startElement}</code>) occurs.
* 
* @param prefix <code>String</code> prefix used for the namespace
* being reported
* @param uri <code>String</code> URI for the namespace
* being reported
* @throws <code>SAXException</code> when things go wrong
public void startPrefixMapping(String prefix, String uri) {
System.out.println("Mapping starts for prefix " + prefix +
" mapped to URI " + uri);
* 
* This indicates the end of a prefix mapping, when the namespace
* reported in a <code>{@link #startPrefixMapping}</code> callback
* is no longer available.
* 
* @param prefix <code>String</code> of namespace being reported
* @throws <code>SAXException</code> when things go wrong
public void endPrefixMapping(String prefix) {
System.out.println("Mapping ends for prefix " + prefix);
* 
* This reports the occurrence of an actual element. It will include
* the element's attributes, with the exception of XML vocabulary
* specific attributes, such as
* <code>xmlns:[namespace prefix]</code> and
* <code>xsi:schemaLocation</code>.
* 
* @param namespaceURI <code>String</code> namespace URI this element
* is associated with, or an empty
* <code>String</code>
* @param localName <code>String</code> name of element (with no
* namespace prefix, if one is present)
* @param rawName <code>String</code> XML 1.0 version of element name:
* [namespace prefix]:[localName]
* @param atts <code>Attributes</code> list for this element
* @throws <code>SAXException</code> when things go wrong
public void startElement(String namespaceURI, String localName,
String rawName, Attributes atts)
throws SAXException {
System.out.print("startElement: " + localName);
if (!namespaceURI.equals("")) {
System.out.println(" in namespace " + namespaceURI +
" (" + rawName + ")");
} else {
System.out.println(" has no associated namespace");
for (int i=0; i<atts.getLength(); i++)
System.out.println(" Attribute: " + atts.getLocalName(i) +
"=" + atts.getValue(i));
* 
* Indicates the end of an element
* (<code></[element name]></code>) is reached. Note that
* the parser does not distinguish between empty
* elements and non-empty elements, so this will occur uniformly.
* 
* @param namespaceURI <code>String</code> URI of namespace this
* element is associated with
* @param localName <code>String</code> name of element without prefix
* @param rawName <code>String</code> name of element in XML 1.0 form
* @throws <code>SAXException</code> when things go wrong
public void endElement(String namespaceURI, String localName,
String rawName)
throws SAXException {
System.out.println("endElement: " + localName + "\n");
* 
* This will report character data (within an element).
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void characters(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("characters: " + s);
* 
* This will report whitespace that can be ignored in the
* originating document. This is typically only invoked when
* validation is ocurring in the parsing process.
* 
* @param ch <code>char[]</code> character array with character data
* @param start <code>int</code> index in array where data starts.
* @param end <code>int</code> index in array where data ends.
* @throws <code>SAXException</code> when things go wrong
public void ignorableWhitespace(char[] ch, int start, int end)
throws SAXException {
String s = new String(ch, start, end);
System.out.println("ignorableWhitespace: [" + s + "]");
* 
* This will report an entity that is skipped by the parser. This
* should only occur for non-validating parsers, and then is still
* implementation-dependent behavior.
* 
* @param name <code>String</code> name of entity being skipped
* @throws <code>SAXException</code> when things go wrong
public void skippedEntity(String name) throws SAXException {
System.out.println("Skipping entity " + name);
* <code>MyErrorHandler</code> implements the SAX
* <code>ErrorHandler</code> interface and defines callback
* behavior for the SAX callbacks associated with an XML
* document's errors.
class MyErrorHandler implements ErrorHandler {
* 
* This will report a warning that has occurred; this indicates
* that while no XML rules were "broken", something appears
* to be incorrect or missing.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void warning(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Warning**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Warning encountered");
* 
* This will report an error that has occurred; this indicates
* that a rule was broken, typically in validation, but that
* parsing can reasonably continue.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void error(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Error encountered");
* 
* This will report a fatal error that has occurred; this indicates
* that a rule has been broken that makes continued parsing either
* impossible or an almost certain waste of time.
* 
* @param exception <code>SAXParseException</code> that occurred.
* @throws <code>SAXException</code> when things go wrong
public void fatalError(SAXParseException exception)
throws SAXException {
System.out.println("**Parsing Fatal Error**\n" +
" Line: " +
exception.getLineNumber() + "\n" +
" URI: " +
exception.getSystemId() + "\n" +
" Message: " +
exception.getMessage());
throw new SAXException("Fatal Error encountered");

I have seen this error when I'm executing inside one of the (j2ee sun reference implementation) server containers (either web or ejb). I believe its caused by "something" having previously loaded the "sax 1 driver class". In my case, I think the container or server is loading the sax parser from a jar that contains a sax 1 version. If you can, ensure that nothing is loading the sax 1 parser from another jar on your system. Verify that you are loading the sax parser from a jar containing the latest version so that you get the sax 2 compliant parser. Good luck!

What are the possible errors that can happen in data loads(rsmo monitor)?

hi all,
what could be the error that could result in red color in the RSMO monitor of data load transaction?
1. request everything ok
(what are the possible error type which make here red)
2. extraction everything ok
(what are the possible error type which make here red)
3. transfer (idocs and trfc) error occured?
(what are the possible error type which make here red)
4. processing
- data package
5. process chain
(what are the possible error type which make here red)
6 other messages.
(what are the possible error type which make here red)
thanks
pooja

Hi,
I can tell you the most common reasons of these failures.
1. request everything ok
Here it will be telling you if the request was properly send to source system and got triggered there.
2. extraction everything ok
In this step the actual extraction of data happens, issue slike sysfail or CPIC error may cause this to fail.
3. transfer (idocs and trfc) error occured?
When extraction is complete and data is being send to BW. But if dur to some reason it fails, error may come here.
4. processing
Processing in BW fails for each data packet is displayed here.
This can also happen when you have sysfail in source.
5. process chain
This can show the logs of the chain here and also status of subsequent process.
6 other messages.
Any other error message.
Refer
What is the information we can get the through details tab in RSMO
working with RSMO errors
http://help.sap.com/saphelp_nw70/helpdata/en/12/43074208ae2a38e10000000a1550b0/frameset.htm
Also
Data Load Errors
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Data Load issues
Errors in loading
data loading errors
load Errors
Process Chain Errors
/people/mona.kapur/blog/2008/01/14/process-chain-errors
Common Process chain errors
process chain issues or errors
Hope this helps.
Thanks,
JituK

What r the diff. error that can be solved using RSRV tcode?

Hi ,
what r the diff. error that can be solved using RSRV tcode?
I want to know all the errors that can be solved using RSRV t code
if any body is having good document regarding RSRV please send it to me at
[email protected]
Thanx in advance,
ravi.

Hi,
Refer the below links for more details about RSRV TCODE.
/community [original link is broken]
http://help.sap.com/saphelp_nw04/helpdata/en/92/1d733b73a8f706e10000000a11402f/frameset.htm
it's for bw objects consistency analysis and repair.
from transaction code RSRV doc itself :
Transaction RSRV: BW Data and Metadata Test and Repair Environment.
Transaction RSRV checks the consistency of data stored in BW. It mostly examines the foreign key relationships between individual tables in the enhanced star schema of the BW system.
The transaction interface was re-designed for SAP Portals release 3.0A. A brief guide about how to use the transaction follows.
Starting the Transaction
You can reach the test and repair environment
By entering the transaction code RSRV
From InfoObject maintenance (Transaction RSD1)
By clicking on the "Analyze" button in the intial screen.
After selecting a characteristic in the maintenance screen via the "Processing -> Analyze InfoObject" menu option.
The Initial Screen
When using the test and repair environment for the first time, the message "Values were not found for all setting parameters" draws your attention to the fact that there aren't any saved settings for your user.
After confirming the dialog box, you reach the initial screen of the transaction. This is divided into two parts:
1. On the left-hand side, you can see a tree structure with the pool of available tests.
2. The right-hand side is empty at first. The tests you have selected will be put here. A selection of tests is called a Test Package here.
Combined and Elementary Tests
An Elementary Test is a test that cannot be divided into smaller tests and that can therefore only be executed as a whole.
In this regard, a Combined Test determines which elementary tests are to be executed after entering the parameters. You can remove individual elementary tests from the test package before carrying out the actual test run, in order to reduce run time, for example.
Combining a Test Package and Executing it.
Firstly select one or more tests with drag&drop or by double-clicking. Each selected test appears as a closed folder in the view of your test package. (An exception is elementary tests without parameters: These do not appear as a folder). You can also drag a whole folder of tests from the test pool across to the right-hand screen area; all tests that are located in the hierarchical structure under this folder are then added to the test package. You can also display a short description of the test, if required. Do this right-clicking on a test and choosing "Description" from the context menu.
Afterwards, you must supply the tests with parameters. Tests without parameters must not be given parameters. You are given notification of this when selecting them. You can enter parameters by double-clicking on a test (or a test package) or by expanding the folder of the test.
A dialog box appears in which you must enter the required parameters. Input help is often available. After entering the parameters, a folder with the name "Parameter" is added under the test. This contains the parameter values. The test name can change in some circumstances, enabling you to see at first sight for which parameter values the test is to be executed. It is possible to select the same test several times and give it different parameters, which may even be preferable in some situations. When you have supplied the combined test with parameters, the folder with the name "Elementary Tests" is added under this one. It contains the elementary tests, from which the combined test is built. You can delete individual elementary tests in the test pool using drag & drop.
After supplying all tests with parameters, you can start the test run by clicking on the "Execution" button. After execution, the test icons change from a gray rhombus to a red, yellow or green one, depending on whether the test had errors, warnings or was error-free.
Test Results
The test results are written to the application log. Depending on the settings, the system jumps automatically to this display, or you can reach it by clicking on the "Display" button. The results are saved in the database, and can therefore be compared later with additional test runs.
In the left-hand side of the window, you can see an overview of the most recent test runs. Double-clicking on a folder displays all messages under these nodes as a flat (non-hierarchical) list in the right-hand screen area. Long texts or detail data may be available for individual messages, which can be displayed with a mouse click.
Repairs
Some tests can repair inconsistencies and errors. Automatic correction is generally not possible: If entries are missing from the SID table for a characteristic, in which case the lost SIDs are still being used in a dimension table (and the corresponding dimension keys are still being used in the fact table) of an InfoCube, you can only remove the inconsistency by reloading the transaction data of the InfoCube. Also note that you must make repairs in the correct sequence. You must always read the documentation for the test and have a good idea about how the error occured, before making the repairs.
After executing the test run, go from the application log back to the initial screen to make these repairs. Click on the "Fix Errors" button to start an error run. Since the dataset could have changed between the test and the repair run, the required tests are executed again before the actual repair. The results can be found in the application log once again.
Test Packages
The test package is deleted if you do not save the test package in the display before leaving the test environment. Choose "Test Packages -> Save Test Package" in the option menu. You can do the following via options in the "Test Package" menu:
Load packages
Load for processing - the package is then locked against changes by others.
Delete and
Schedule execution at a later date or at regular intervals in background processing
Settings
In the "Settings" menu option, you can make settings (adjust the size of the screen areas, for example) and save them. The settings are automatically read when starting the test environment. Support packages are being delivered with additional settings options since the test environment is under development at the moment. A message notifies the user at the start if there aren't any values for the setting options.
Jobs Menu Option
You can access the job overview via the Jobs -> Job Overview menu. Use this when you want to check the status of a test package you have scheduled.
Application Log Menu Option
You can display old logs from previous test runs in the dialog box, as well as scheduled ones. The option of deleting test logs can also be found here.
New Selection Button
The currently selected test package is deleted when you press this button.
Filter Button
After a test run, click on this button to remove all elementary tests without errors or warnings from the test package.
Executing Test Packages in Process Chains
You can add a process chain to the ABAP Programm RSRV_JOB_RUNNER in the process chain maintenance transaction, RSPC. To do this, use drag & drop to select the process type "ABAP Program" under "General Services" in the process type view. When maintaining process variants you will be asked for the program name and a program variant. Enter RSRV_JOB_RUNNER for the program name. Choose a program variant name and click on "Change". In the next screen you are able to either change or display an already existing variant, or create a new variant. When creating a new variant you will be asked for the following: Package name (an imput help on this is available), the detail level for the log to which the RSRV log in the process chain log is to be integrated, and a message type severity at which process chain processing should be terminated.
The RSRV process log in the process chain is built as follows:
First is a summary specifying whether errors, warnings, or no errors occurred for each elementary test.
A log view of the RSRV test package at the specified detail level follows.
Example: If you choose the value '3' for the detail level, only messages up to and including detail level 3 will be included in the log processes for the process chain. Messages occuring at a lower layer of the test package test are not displayed in this log. Please note that, unlike the application log, the process log does not propagate errors from deep detail levels to low detail levels. For example, if a single detail level 4 error occurs the summary will show that the relevant test delivered an error. However, this error will not be listed in the second part of the log.
A complete log is always written independantly of the RSRV process log in the process chain. You can view this in the menu option "Application Log->Display Log->From Batch".
Please note that there is currently no transport object for test packages and that consequently these cannot be transported. Process chains that execute RSRV test packages must therefore be manually postprocessed after a transport to a different system: The relevant test packages must be created.
Hope This Helps,
This is already there in SDN.
Regards,
rik

Trying to update creative cloud, comes error: The installation program could not access the important files / directories. Try to run the installer again. (Error code: 43), please contact customer support. The same error comes updating Muse. Mac 10.9.5. W

Trying to update creative cloud, comes error: The installation program could not access the important files / directories. Try to run the installer again. (Error code: 43), please contact customer support. The same error comes updating Muse. Mac 10.9.5. What shall I do?

Alauda_positos I would recommend reviewing your installation log files to determine the exact directory which the installer is unable to access. You can find details on how to locate and interpret your installation log files at Troubleshoot install issues with log files | CC - http://helpx.adobe.com/creative-cloud/kb/troubleshoot-install-logs-cc.html. You are welcome to post any specific errors discovered to this discussion.
For information on how to adjust file permissions please see Error "Exit 6" or "Exit 7" | Install log | Read, write, system file errors | CS5, CS5.5 - http://helpx.adobe.com/creative-suite/kb/error-exit-6-exit-7.html.

What are the common errors in reporting and extraction.

hi friends,
what are the common errors in reporting and extraction for implementation and support projects.
thanking u
suneel.

Hi Suneel,
Errors in reporting are like incorrect query creation, errors in creating RKF, CKF and variables, misunderstanding the data, or errors with other tools like broadcasting. Errors in extraction relate to source system connectivity, field-infoobject mapping, incorrect code etc. Also, please search the forums and you will find many real time examples.
Hope this helps...

What are the common errors we get in supporting project

can any body reply what are the common errors we get in supporting project
for abapers tickets will get or not.
what type of tickets generally get regarding reports.

SAP Tickets are nothing but problems or issues raised by the end
customer in a company where end users are running SAP project.
Once the SAP project is implemented, support phase begins. Support
team is responsible for solving the tickets/issues in day-to-day
business.
For any support project, customer will set up Help Desk. If any
problem occurs customer will call Help Desk and register the
issue/Ticket.
Different companies use different software products to manage SAP
Tickets. Remember this software is not provided by SAP. It is third
party software. There are many software products in the market like
Manage Now et c. You can call these software products as tools.
All tools will provide the common attributes which are listed below-
1) Every user will be provided with user name and password to enter
into the tool
2) We can see the tickets assigned for a particular user name.
3) You can list all open tickets by giving the Date Range
4) You can list all closed tickets by giving the Date Range
5) You can list out all the open tickets assigned for an User
6) You can list out all the closed tickets assigned for an User
7) You can see the description of the Ticket, by entering the Ticket
Number. You can see who had raised the Ticket, what is the problem.
What is the severity of the Ticket?
There are lot many other attributes like you can transfer the Ticket
to another user etc.
What is the severity of the problem Ticket?
When a Ticket is raised, it will be given severity. There are
following severities. It may vary from company to company.
Severity 1
Severity 2
Severity 3
Severity 4
The severity will be decided based on the business critical impacts.
If there is large impact on the business it
will be given 1 severity, if it is having least impact then it will be given 4.
Severity 1 problem tickets should be solved in 8 hours.
Severity 2 problem ticket should be solved in 16 hours.
Severity 3 problem ticket should be solved in 15 working days.
Severity 4 problem ticket should be solved in 30 working days.
Again the no of days may vary from one company to another.
All these things will be decided when giving the contract to the IT
company. The agreement is called as "SLA".
SLA stands for Service Level Agreement.
What happens if a particular ticket is not solved by the IT company
according to the SLA/Contract?
The Customer imposes fine on IT company as per the contract/SLA.
Errors in Extraction
1) RFC connection lost.
2) Invalid characters while loading.
3) ALEREMOTE user is locked.
4) Lower case letters not allowed.
5) While loading the data i am getting messeage that 'Record
the field mentioned in the errror message is not mapped to any
infoboject in the transfer rule.
6) object locked.
7) "Non-updated Idocs found in Source System".
8) While loading master data, one of the datapackage has a red light
error message:
Master data/text of characteristic ZCUSTSAL already deleted
1)extraction job aborted in r3
2) request couldnt be activated because theres another request in the
psa with a smaller sid
3) repeat of last delta not possible
4) datasource not replicated
5) datasource/transfer structure not active
Issues faced during the implementation :
1. Slippage of milestones
2. Incorrect or wrong design
3. Reporting format problems
4. Data not matching or reconciling problems
5. Issues discovered during testing leading to redesign
6. Performance issues
7. Requirements misinterpretation
9)check the data same in source system and target system ( i mean
suppose u are extarcting from r/3 after loading check ur data r/3 and
bw same or not.
10)that is abap code, i didnt understand ur question properly.
11)
12) generic extarction, if ur businees contect satisfy ur requirement
u go for generic, suppose u need data from different tables go generic
with view with 1:1 relation 1:M relation for function module.
13)v3 update back groud job is in lo
14)its superior info object, u can find this in master data tab .
15)
16)tuning we will go for improve query performance (compression,
aggregates, partation, index, rollup, precalculated web tneplates.)
17) rsa7(check with some one)
18)bw statics for find data base time and olap time and frontend
time(based on u can improve query performance create like aggra comp ,
indices etc..)
19) direct chain only one chain , meta chain if u have more than one chains
load errors u can solve manually, other than load errors u can wait
right click and repeat.
20)
21) u cn cteate other cube and traansfer, but data space waste.(bec
structures will be deffi)
22) u mean data source enhancement.or not(let me know)
23)rsap0001( for customer exit variables) 001 for transaction data 001
attributes, 003 text 004 hierchies.
24)web application design , its like same bex, but report will execute
in browser.
25)
26) arrangement of process are called process type and we can use
varient and start process for back ground jobs.
Don't forget to asign points
regards
ravish

What does the "conversion error" I get when converting a pdf file to Microsoft word?

What is the "conversion error" I get when converfting a pdf file to aMicrosoft word?

Adobe reader with export to PDF
Sent from my iPhone 5
Marty Kennedy

What is the 0x80070570 error when installing Win7 or Win8 or Win 8.1 on a clean SSD/HDD ?!

Hello,
My computer was working perfectly with Win7 for about 2years until I formatted on monday to clean a little bit my drives ... Since then I'm unable to install windows again. I have the 0x80070570 error.
The complete error message is:
Windows cannot install required files. The file may be corrupt or missing. Make sure that all files required for installation are available and restart the installation. Error code:0x80070570.
What is the 0x80070570 error when installing Win7 or Win8 or Win 8.1 on a clean SSD/HDD ?! These versions are full from MSDN.
What I did already:
check my RAM (16go gskill)
remove unnecessary hard drives
replace my "old" SSD with a clean new one
remove my sound cards
remove the mouse and use only keyboard
reset the BIOS
check every LED on the motherboard (asus sabertooth z77) and there is no problem
What are the problems?
Thanks,
Adrien.

Hi,
If all images cannot be installed, we have a reason to suspect the hardware cause.
If you use two memory slots to get 16G RAM, I suggest you test with just one (8G) to check the result.
Alex Zhao
TechNet Community Support

HT202159 I was downloading a app from the app store and it downloaded about 85% then gave an error message download failed but when I reopen the app store to the purchases the resume button show but when i click it the same error comes up failed to downlo

I was downloading a app from the app store and it downloaded about 85% then gave an error message download failed but when I reopen the app store to the purchases the resume button show but when i click it the same error comes up failed to download

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Select
/var/log ▹ install.log
from the hierarchical list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar. Then select the messages from the last installation or update attempt, starting from the time when you initiated it. If you're not sure when that was, start over and note the time. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).
If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.

Yosemite made my MacBook Pro so slow !! Need help ? what is the solution?

Yosemite made my MacBook Pro so slow !! Need help ? what is the solution?

I've ran a benchmark on my Mac (iMac early 2009). Performance of Yosemite in general was about the same as Mavericks. But that can be different on other Mac's of course. Safari is mostly a bit slower. It's recommended you clean your old internet-caches and then restart Safari. (you can use a little app called CCleaner to do that). That might make a difference. Speed-issues are usually solved in the first and second update of OS X.

What is the portal that comes with webcenter suite 11g?

Hello,
What is the portal that comes with webcenter suite 11g?
How to retrieve the content from UCM using this portal?
-Scott

Scott,
The JCR adpater can be configured against Oracle Content Server(UCM), file system and Oracle Portal. This gives you only the read feature on the repository. However the web center frame work also provides you the Document Library Task flows with both Read/Write capabilities and other capabilities like recent documents, search etc. The task flows can also customized to suit your UI requirements as well. In addition to this there is a content presenter Task flow available where Business Users can display formatted content from UCM on web center page. This is similar to the content presenter portlet available inside WLP.
Regards
Vijay

Help Me what is the "Parse Error: com.sun.xml.parser/P-067"?

Similar Messages

Maybe you are looking for