Org.apache.crimson and 1.5

I am trying to test an application in 1.5 and am getting compile errors for crimson references in classes someone else wrote.
Looking at the JDK src, it looks like the apache packages are not bundeled in to the 1.5 beta.
Wth the preface that I am mostly a Swing developer my questions are...
I know it has to do with XML, but what specific functionality did crimson bring to the tale?
Why did Sun remove the apache libs from the distribution?
Is there anything in 1.5 to take crimsons place.
Thanks for your time if you answer,
Todd

Looking at the JDK src, it looks like the apache
packages are not bundeled in to the 1.5 beta.That's correct. The only contract is to supply an XML processor, not a specific one. Crimson is just one; Xerces is the most popular one out there. Looks like 1.5 includes a subset of Xerces (with a different package - com.sun.org.apache.xerces.internal).
I know it has to do with XML, but what specific
functionality did crimson bring to the tale?Nothing special. It was just a lightweight XML implementation.
Why did Sun remove the apache libs from the distribution?
Is there anything in 1.5 to take crimsons place.It's just replaced them with something they felt they could maintain better.
You should not ever be referring to Crimson classes directly. You should ONLY use org.w3c.dom or org.w3c.sax classes directly, and use the advertised Factory APIs to create or manipulate Documents, Elements, etc.
Your best bet is to rip out all references to org.apache.crimson, and use an elementary XML textbook to replace them with references to standard org.w3c.* classes.

Similar Messages

URGENT: JAXP Provider org.apache.crimson.jaxp.SAXParserFactoryImpl not foun

Hi all
I am having this strage problem. I am using JAXP Apis to do XSLT transformation and everything works fine.
But when I try the samething with
-Djava.security.manager option and
-Djava.security.policy==$WL_HOME/weblogic.policy option set it doesn't work. Stranger still the error it gives:
javax.xml.transform.TransformerException: javax.xml.parsers.FactoryConfigurationError: Provider org.apache.crimson.jaxp.SAXParserFactoryImpl not found
This the command that works:
$JAVA_HOME/java -classpath $WL_CLASSPATH -Dintegration.config=$WL_HOME/integration.cfg com.swl.integration.translation.SendPRThread 24972 451
This one does NOT work:
$JAVA_HOME/java -ms64m -mx64m -verbosegc -classpath $WL_CLASSPATH -Djava.security.manager -Djava.security.policy=$WL_HOME/weblogic.policy -Dintegration.config=$WL_HOME/integration.cfg com.swl.integration.translation.SendPRThread 24972 451
I know it's something to do with Security manager/policy setting, but can't figure it out.
Could anyone please help? It is very urgent.
Thanks a lot
Mak

I have your solution... under Weblogic BEA were giving the same error, I resolved it with this code before the instantiation of SAXParserFactory:
String key = "javax.xml.parsers.SAXParserFactory"
String value = "org.apache.xerces.jaxp.SAXParserFactoryImpl";
Properties props = System.getProperties();
props.put(key, value);
System.setProperties(props);

NullPointerException at org.apache.crimson.parser.Parser2.parseInternal

I've tried to use JavaTM API for XML Processing (JAXP), particulary default SAX parser,
which is embeded into JAXP.
I downloaded jaxp-1_1.zip file from http://java.sun.com/xml/download.html, extacted it
and included crimson.jar, jaxp.jar and xalan.jar to java CLASSPATH.
After that I'd tried to parse XML document
with following code
     // prepare SAX parser
SAXParserFactory factory = SAXParserFactory.newInstance();
DefaultHandler handler = new XMLHandler();
try {
// Create a JAXP SAXParser
SAXParser saxParser = factory.newSAXParser();
// url
File file = new File( fileName );
String url = file.toURL().toString();
System.out.println( "URL: " + url );
// parse
saxParser.parse( url, handler );
} catch (Exception ex) {
ex.printStackTrace();
throw ex;
and obtained the message below
java.lang.NullPointerException
     at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:523)
     at org.apache.crimson.parser.Parser2.parse(Parser2.java:304)
     at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:346)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:232)
     at com.darout.bot.parser.PObjectsBuilder.parse(PObjectsBuilder.java:54)
     at TestSAXParser.main(TestSAXParser.java:22)
Could you help me?

I've found an error. It was in my handler implementation.
But is it possible to trace a handler exception correctly?

Java.lang.ClassCastException: org.apache.crimson.tree.XmlDocument

Hi all,
i am new to java. I am trying to parse an xml document. the code is as follows:-
Document document = null;
DocumentBuilderFactory factory = ocumentBuilderFactory.newInstance();
try {
     DocumentBuilder builder = factory.newDocumentBuilder();
     document = builder.parse( new File(xmlFile) );
after this i am trying to traverse using treewalker :-
Element docElem = document.getDocumentElement();
               DocumentTraversal docTrav = (DocumentTraversal) document;
               TreeWalker treeWalk = docTrav.createTreeWalker(docElem, NodeFilter.SHOW_ELEMENT, new ConfigNodeFilter(), false);
          Node node = treeWalk.nextNode();
when i compile all is fine but while runnig it. i get the following error:-
java.lang.ClassCastException: org.apache.crimson.tree.XmlDocument
at - DocumentTraversal docTrav = (DocumentTraversal) document;.
my import statements are as follows:-
import java.io.File;
import java.io.IOException;
import java.net.InetAddress;
import java.net.UnknownHostException;
import java.util.Vector;
import java.util.regex.Matcher;
import java.util.regex.Pattern;
import javax.servlet.Filter;
import javax.servlet.FilterChain;
import javax.servlet.FilterConfig;
import javax.servlet.RequestDispatcher;
import javax.servlet.ServletException;
import javax.servlet.ServletRequest;
import javax.servlet.ServletResponse;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.ParserConfigurationException;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.traversal.DocumentTraversal;
import org.w3c.dom.traversal.NodeFilter;
import org.w3c.dom.traversal.TreeWalker;
import org.xml.sax.SAXException;
i am not able to understand why the error is coming.
any help will be appreciated.

"In DOMs which support the Traversal feature, DocumentTraversal will be implemented by the same objects that implement the Document interface. "
My guess is that the DOM parser you are using doesn't support the DocumentTraversal interface which is why you can not cast to that class.

Org.apache.crimson.tree.DomEx: INVALID_CHARACTER_ERR:

I am using XML to create an element.
It fails when I try to create with numbers.
node = doc.createElement("111");
why is that?

So, you think it would be valid to have the following:
<document>
<1 1 1>some text</1 1 1>
</document>That is what you are asking for. The String you specify in the createElement is the tagname. Tagnames cannot have spaces in them. I don't have a reference with me, but I don't think they can start with a numeric.
How is "node" defined? Did you mean node = doc.createTextNode("1 1 1");
That should work.
Dave Patterson

Crimson and DTDs

Hi!
I'm having problems with Crimson in combination with documents validated using an external DTD. I'm usinf JAXP 1.1. Basically I get an exception:
Exception in thread "main" java.lang.NoSuchMethodError
     at org.apache.crimson.tree.XmlDocumentBuilder.startDTD(XmlDocumentBuilder.java:648)
     at org.apache.crimson.parser.Parser2.maybeDoctypeDecl(Parser2.java:1118)
     at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:488)
     at org.apache.crimson.parser.Parser2.parse(Parser2.java:304)
     at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
     at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:179)
     at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:161)
I'm using the following bit of code:
DocumentBuilderFactory fac = DocumentBuilderFactory.newInstance();
builder = fac.newDocumentBuilder();
doc = builder.parse(new File(filename));
Is that a Crimson error or am I doing something wrong? Maybe I have messed up different versions of DOM, JAXP, ... libraries?!
I'm doing that to compare different implementations, and it works fine with Xerces and my own one. I thought it is strange that exactly the JAXP default parser would fail on this task.
Any thoughts?
Mathias

I had a problem like yours. Apparently, the "parse" method have a little problem with a "file" object as a parameter try this, it worked with me :
File fl = new File(strFileName);
doc = builder.parse(new FileInputStream(fl));
San_A

Eclipse won't resolve org.apache.* packages

Hello everyone,
I'm relatively new to java and eclipse and I am really stuck trying to use various packages.
First a little history on what I am doing. I've created a project from existing source using the new java project wizard. This source code is obtained from the Book: XML and Java: Developing Web Applications, 2nd Edition. It's sort of dated. It uses SDK 1.3, and xerces 1.4.3 the current is 2.9.1. I have version 2.9.0 according to the Eclipse plugin registry. ( Thought I'd mention this in the event it may be relevant ).
The problem is Eclipse will not resolve this line of code:
import org.apache.xerces.parsers.DOMParser;
I look at plugins and I see xerces listed:
Provider:: eclipse.org
Plug-in Name:: Apache Xerces-J
Version:: 2.9.0v200909240008
Plug-in ID:: org.appache.xerces
However, Eclipse content assist does not list any org.apache packages and of course it won't compile without fatal errors.
In an attempt to correct the problem I've created a classpath variable in
Preferences > Java > Buildpath > Classpath variables:: xerces_2_9_0 - /Applicatins/Eclipse/plugins/org.apache.xerces_2.9.0.v200909240008.jar
Then added the var to a launch configuration.
The same error still persists::
Exception in thread "main" java.lang.Error: Unresolved compilation problems:
DOMParser cannot be resolved to a type
DOMParser cannot be resolved to a type
at chap02.SimpleParse.main(SimpleParse.java:20)
I've also tried to add jar's to the libraries using Preferences > Java > Build Path > User Libraries but the the button on the right 'Add jars...' is not acitve.
The complete source code is listed below. Although I don't think the problem resides there.
Anyone who can help me in understanding this problem and resolving it would be greatly appreciated.
( I obviously am misunderstanding something ).
Regards,
gjames
package chap02;
* SimpleParse.java
import org.w3c.dom.Document;
import org.apache.xerces.parsers.DOMParser;
import org.xml.sax.SAXException;
import java.io.IOException;
public class SimpleParse {
public static void main(String[] argv) {
if (argv.length != 1) {
System.err.println(
"Usage: java chap02.SimpleParse <filename>");
System.exit(1);
try {
// Creates a parser object
DOMParser parser = new DOMParser();
// Parses an XML Document
parser.parse(argv[0]);
// Gets a Document object
Document doc = parser.getDocument();
// Does something
} catch (SAXException se) {
System.out.println("Parser error found: "
+se.getMessage());
System.exit(1);
} catch (IOException ioe) {
System.out.println("IO error found: "
+ ioe.getMessage());
System.exit(1);
}

gmjames wrote:
..I'm relatively new to java and eclipse and I am really stuck trying to use various packages. 1) The Jars need to be added to the compile-time & run-time class-path of the application.
2) You will be better off figuring how to do that in Ant or from the command line, rather than an IDE.
3) When posting code, code snippets, HTML/XML or input/output, please use the code tags. The code tags protect the indentation and formatting of the sample. To use the code tags, select the sample and click the CODE button.
4) For best help on Eclipse, see the [Eclipse forums|http://www.eclipse.org/forums/].

Org/apache/log4j/Category on OAS 10.1.3 and Jdev 10.1.3.5

Hi,
I am new to ADF and my company is also new to ADF. We are doing how it coudl help us in acclerating the development of custom screens on top of OTM 5.5
I am using OAS 10.1.3. I am getting org/apache/log4j/Category error at the time of deployment causing road block. Plz help...
Below are the steps I followed
1. Stopped OAS
2. Install ADF Installer 10.1.3.5 by extracting files, changing adfinstaller.properties, and running java -jar runinstaller.jar adfinstaller.properties
3. Started OAS
4. OAS never started up as server.xml had an new entry
<application name="datatags" path="../../../BC4J/redist/datatags.ear" start="true" />
<import-shared-library name="oracle.ws.jaxrpc"/>
5. datatags directory was malformed in the sense META-INF/application.xml and other .xml file was not created at all.
6. Since ADF requires only libraries to be available, I removed this 2 enteries and started up the OAS.
7. Started the OAS
8. Copied files from
[$Jdeveloper Home]\jakarta-taglibs
to
[$OC4J Home]\BC4J\lib
the files are:
commons-digester.jar
commons-logging.jar
commons-collections.jar
9. Download and copy apache-log4j-1.2.15 (log4j-1.2.15.jar) to [$OC4J Home]\BC4J\lib
10. I created a simpel ADF Helloworld page.
11.Created a deployment discriptor orion-application and added the following enteries
<imported-shared-libraries>
<remove-inherited name="apache.commons.logging"></remove-inherited>
</imported-shared-libraries>
12. I right clicked on my UserInterface ->New-> Deployment profile -> Created a WAR file
13. Right click the WAR file and deployed to the OAS
14. I got the following deployment error
Wrote EAR file to C:\shobz\SOFTWARES\otm_jdev_10G\jdev\mywork\TestADF\UserInterface\deploy\webapp1.ear
Uploading file webapp1.ear ...
Uploading file webapp1.ear ...
Uploading file webapp1.ear ...
Uploading file webapp1.ear ...
Uploading file webapp1.ear ...
Uploading file webapp1.ear ...
Uploading file webapp1.ear ...
Uploading file webapp1.ear ...
Application Deployer for webapp1 STARTS.
Copy the archive to /u01/app/otm/otmapp/oas/j2ee/home/applications/webapp1.ear
Initialize /u01/app/otm/otmapp/oas/j2ee/home/applications/webapp1.ear begins...
Unpacking webapp1.ear
Done unpacking webapp1.ear
Unpacking webapp1.war
Done unpacking webapp1.war
Initialize /u01/app/otm/otmapp/oas/j2ee/home/applications/webapp1.ear ends...
Starting application : webapp1
Initializing ClassLoader(s)
Initializing EJB container
Loading connector(s)
Starting up resource adapters
Initializing EJB sessions
Committing ClassLoader(s)
Initialize webapp1 begins...
Initialize webapp1 ends...
Started application : webapp1
Binding web application(s) to site default-web-site begins...
Binding webapp1 web-module for application webapp1 to site default-web-site under context root TestADF-UserInterface-context-root
Operation failed with error:
org/apache/log4j/Category
Deployment failed
I tried step 9 and 11 in order to get rid of this log4j error.
Your help is highly appreciated.
Shobz
Edited by: user13114596 on Jan 6, 2011 8:40 PM

ADF 11g requires JEE 5.0 server.
Oracle Application Server 10.1.3 supports J2EE 1.4.
JDeveloper 11g application won't run on OAS 10.1.3.

The import org.apache cannot be resolved and I am not sure why?

Alright, so I decided to build myself the simplest of simplest ftp client so that I could understand how this works:
Ok, I have parts built but I am trying to include the following things:
import org.apache.commons.net.ftp.FTPClient;
import org.apache.commons.net.ftp.FTPFile;The error I am getting from eclipse (which is the editor that I am using) is:
The import org.apache cannot be resolvedThe same thing happens when I try to do:
import com.jscape.inet.ftp.*;I have an idea what is going on with this but I am not entirely sure. I think I need a package that I must download from apache or somewhere that might give me access to libraries?
I would be grateful to any help...
Thanks,
Adam Scott

Yes you need to have the classes that you want to import. If you have them then you need to add them to your project's classpath.

Namespaces / apache.crimson.parser / BASDA XML / HELP!!

This is probably an easy question but I can't find anyone to help me.
I am using the apache.crimson.parser to parse and validate an Xml doc against the BASDA eBIS-XML purchase order schema but i can't get the Namespaces right.
I have this at present for the Xml doc;
<Order xmlns ="urn:schemas-microsoft-com:xml-data"
xmlns:xsi ="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:schemas-microsoft-com:xml-data
http://www.cs.aston.ac.uk/hillsm/project/eBIS-XML_Order_v3.01.xml">
....and this for the schema;
<Schema name="eBIS-XML_Order_v3.01.xml"
xmlns="urn:schemas-microsoft-com:xml-data"
xmlns:dt="urn:schemas-microsoft-com:datatypes">
Does anyone have any ideas??

Steven,
let me first note that I'm not familiar with the specific Schema you mention here (apparently from M$), and it would have been helpful to see at least part of it in your posting, because it seems abnormal that Microslob uses the conventional xsd namespace for schema declarations (although it wouldn't surprise me).
Anyways, let's do a first version without the xsd name space.
The declarations in your xml file are correct.
In the schema file, the first error is, that schema is misspelled as Schema. Secondly, schema does not allow a name attribute (get rid of it). There is also no reference to the namespace "http://www.w3.org/2001/SMLSchema". So, the default namespace has to be changed to that. The targetNamespace attribute specifies that this schema applies to the specified name space. Putting it all together:
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
             targetNamespace="urn:schemas-microsoft-com:xml-data"
             xmlns:dt="urn:schemas-microsoft-com:datatypes">
       
       <element name="Order" type="string"/>
</schema>So this would validate OK with this xml file (provided that ..../eBIS-XML_Order_v3.01.xml is the above schema file):
<?xml version="1.0"?>
<Order xmlns ="urn:schemas-microsoft-com:xml-data"
          xmlns:xsi ="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="urn:schemas-microsoft-com:xml-data
          http://www.cs.aston.ac.uk/hillsm/project/eBIS-XML_Order_v3.01.xml">
</Order>                     So, in this example, the default namespace in the schema is set to "http://www.w3.org/2001/XMLSchema" and the targetNamespace attribute points to the xml file's default name space.
However, the standard way of doing things differs. You certainly should not (mis-)set the schema's default name space to "http://www.w3.org/2001/XMLSchema".
I do not know in what way Microsoft limits you, but I strongly recommend something along these lines in order to not have regrets, headache and coffein and nicotine addiction lateron:
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
            xmlns="urn:schemas-microsoft-com:xml-data"
            xmlns:dt="urn:schemas-microsoft-com:datatypes"
            targetNamespace="urn:schemas-microsoft-com:xml-data">
   <xsd:element name="Order" type="xsd:string"/>
</xsd:schema>Also, in order to avoid confusion, Schema files should have the extension xsd - a minor sidepoint.
Hope that helps,
Leo.

Java.lang.NoClassDefFoundError: org/apache/axis/client/Service

Hi,
I am developing a WebService Client and for that i am using the Apache axis client. but when i am trying to instnatiate the org.apache.axis.client.Service class it says a NoClassDefinition Found error.
Can anyone tell me the reason for this? Is there any settings for axis client in the Portal-App.xml or any other place?
Thanks
Kiran

Have you included all the Axis client jars in your /dist/PORTAL-INF/lib folder and added them to to .classpath?
axis.jar , commons-discovery.jar , commons-logging.jar , crimson.jar , jaxp.jar , jaxrpc.jar , log4j.jar , saaj.jar , wsdl4j.jar , xalan.jar , xerces.jar .

JSTL & Apache Crimson

Hi, I have been experiencing problems whilst attempting to use the JSTL Standard Tag Library with the Apache Crimson XML Parser in the classpath. I have tried running the JSTL JSP page without Crimson in the classpath and it works fine. However when included in the classpath and I attempt to view the page I get the error below. According to this page:
http://jakarta.apache.org/taglibs/doc/standard-1.0-doc/GettingStarted.html
the "Standard Taglib requires a JAXP 1.1 or 1.2 compliant parser". It goes on to list Crimson as an example of this. However the Crimson pages states that it supports "JAXP 1.1 minus the javax.xml.transform package."
I would simply use another XML parser, except that I am using the Google API Jar which uses Crimson, thus I cannot remove it from the classpath if I wish to continue using the Google API.
If anyone has any idea how I might solve this problem I'd be keen to hear them,
Thanks very much,
Ross Butler
org.apache.jasper.JasperException: <h3>Validation error messages from TagLibraryValidator for c</h3>
null: java.lang.IllegalStateException: can't declare any more prefixes in this context
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:50)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:72)
org.apache.jasper.compiler.Validator.validateXmlView(Validator.java:1549)
org.apache.jasper.compiler.Validator.validate(Validator.java:1495)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:157)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:267)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:255)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:556)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:296)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:362)

the "Standard Taglib requires a JAXP 1.1 or 1.2
compliant parser". It goes on to list Crimson as an
example of this. However the Crimson pages states
that it supports "JAXP 1.1 minus the
javax.xml.transform package." So what? An XML parser just parses an XML document into some internal representation of the XML. It doesn't do transformations. So what you say there doesn't appear to be relevant to me. It is an example of that.
I would simply use another XML parser, except that I
am using the Google API Jar which uses Crimson, thus
I cannot remove it from the classpath if I wish to
continue using the Google API.Why not? Does the Google API (I'm not familiar with it) say it MUST use Crimson? I think it's likely that it's distributed with Crimson for the convenience of users who don't have any XML parser (Java 1.3 and earlier users). So if it comes with a separate crimson.jar (or whatever) then just toss that out and see what happens. I didn't notice that being one of the tests you did.
And if you find that Google API doesn't work with the built-in parser in your JRE, it's possible to specify the parser your environment should use by setting the system property javax.xml.parsers.SAXParserFactory to the full name of Crimson's SAX parser factory and likewise the system property javax.xml.parsers.DocumentBuilderFactory. (You can't do this just for your web application, though, you want your entire web application server to use the same parser or strange things may happen. Like the strange things you are seeing.)

Apache Crimson not compatible with JSTL?

Hi, I have been experiencing problems whilst attempting to use the JSTL Standard Tag Library with the Apache Crimson XML Parser in the classpath. I have tried running the JSTL JSP page without Crimson in the classpath and it works fine. However when included in the classpath and I attempt to view the page I get the error below. According to this page:
http://jakarta.apache.org/taglibs/doc/standard-1.0-doc/GettingStarted.html
the "Standard Taglib requires a JAXP 1.1 or 1.2 compliant parser". It goes on to list Crimson as an example of this. However the Crimson pages states that it supports "JAXP 1.1 minus the javax.xml.transform package."
I would simply use another XML parser, except that I am using the Google API Jar which uses Crimson, thus I cannot remove it from the classpath if I wish to continue using the Google API.
If anyone has any idea how I might solve this problem I'd be keen to hear them,
Thanks very much,
Ross Butler
org.apache.jasper.JasperException: <h3>Validation error messages from TagLibraryValidator for c</h3>
null: java.lang.IllegalStateException: can't declare any more prefixes in this context
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:50)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:72)
org.apache.jasper.compiler.Validator.validateXmlView(Validator.java:1549)
org.apache.jasper.compiler.Validator.validate(Validator.java:1495)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:157)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:267)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:255)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:556)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:296)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:362)

You should not add j2ee.jar to the WEB-INF folder. I think you should move it to "C:\Program Files\Apache Group\Tomcat 4.1\lib\j2ee.jar".
Also, it might help to read section 9.7.2 in the servlet 2.3 specification (as stated in the error). You can download the spec here: http://www.jcp.org/aboutJava/communityprocess/final/jsr053/

Java.lang.NoClassDefFoundError: org/apache/xerces/parsers/SAXParser

We are trying to evaluate Weblogic 6.1 Beta version.
We have tried a setup that is working in WebLogic 6.0 sp1 version,
but the same setup fails in the Beta version.
We get ...
java.lang.NoClassDefFoundError:
org/apache/xerces/parsers/SAXParser
We had not specified any addl. jars in the classpath
in 6.0 sp1 version. But this fails in the Beta version.
Could someone tell if this is a known bug in the Beta release and
suggest a solution or tell if this will be fixed in the actual version
when it is
released in July?
Thanks.
-Arvind

"Jeeva" <[email protected]> wrote in message
news:3b40ecb5$[email protected]..
>
Alternatively u can set the parameters to look at the right parser when uneed
it. This can be done by:
System.setProperty("javax.xml.parsers.SAXParserFactory","org.apache.xerces.jaxp.SAXParserFactoryImpl");
System.setProperty("javax.xml.parsers.DocumentBuilderFactory","org.apache.xerces.jaxp.DocumentBuilderFactoryImpl");
System.setProperty("javax.xml.parsers.SAXParser","org.apache.xerces.jaxp.SAXParserImpl");
This is far from being recommended for the following reason:
The JAXP factories cache the classes used to instantiate the factories,
therefore you cannot changed dynamically these properties at runtime, you
will have absolutely NO guarantee that this will work. If a factory is
instantiated before yours, it will use this one. Additionaly, Weblogic
already defines these properties at startup so that they refer to their own
factories that can look into the XML registry.
Consider these properties as being read-only. Chance are that you will mess
up everything if you modify them.
If you need to define a specific parser (such as crimson), then put crimson
in your system classpath and set the XML registry appropriately.
If you want to take a look at jaxp strategy. Use the JVM
property -Djaxp.debug=true.
As well use -Dweblogic.xml.debug=true for Weblogic XML related info.
Stéphane Bailliez
Software Engineer, Paris - France
iMediation - http://www.imediation.com
Disclaimer: All the opinions expressed above are mine and not those from my
company.

Import org.apache.xml.serialize.*;

.java:66: package org.apache.xml.serialize does not exist
import org.apache.xml.serialize.*;
^
i am getting this error while running a java program, which i downloaded from a open source.
i am using J Creator.
i suppose i need to add a class path or package.
can anybody tell me how to do this.
and where can i find that package.
if i can't find that in my system, where can i get it on net.

.java:66: package org.apache.xml.serialize does notThe org.apache.xml.serialize.* package is part of Xerces:
http://xml.apache.org/xerces-j/
http://xml.apache.org/xerces2-j/index.html

Org.apache.crimson and 1.5

Similar Messages

Maybe you are looking for