From: "James Strachan" <[EMAIL PROTECTED]>
> From: <[EMAIL PROTECTED]>
> > Hi folks,
> >
> > No confusion would have arisen, of course, if somebody at maven hadn't
> > decided to rename xmlParserAPIs (or reformat xml-apis). Does anyone
hav
From: <[EMAIL PROTECTED]>
> Hi folks,
>
> No confusion would have arisen, of course, if somebody at maven hadn't
> decided to rename xmlParserAPIs (or reformat xml-apis). Does anyone have
> contacts in the maven world who could straighten this out?
Yes - I'll try sort this out. I'll ensure that a
s you
> need. (Does Xalan ship our xmlParserAPIs file? I doubt they do; I hope
> they don't. :) )
>
> Hope that helps,
> Neil
> Neil Graham
> XML Parser Development
> IBM Toronto Lab
> Phone: 905-413-3519, T/L 969-3519
> E-mail: [EMAIL PROTECT
I've just downloaded the latest & greatest xerces and xalan and they both
come with a jar called xml-apis.jar but seem to contain different bits of
the XML-api set. Most notably the one with xerces doesn't come with the XSLT
part of JAXP. Is this by design or just an oversight?
Things are getting
From: "Andy Clark" <[EMAIL PROTECTED]>
> James Strachan wrote:
> > BTW it wasn't my intention to suggest Jelly was in any way competitive
> > technology, more that Jelly could be an alternative runtime engine for
your
> > pipeline processors; that if more
The Jaxen and SAXPath teams are proud to annouce the 1.0 FCS releases of
both Jaxen and SAXPath.
Jaxen is a fast Java engine for XPath 1.0 that works on all XML object
models. The following models are currently supported out of the box [DOM,
dom4j, Electric XML and JDOM].
This new release adds a
dom4j is a simple and flexible open source library for working with XML,
XPath and XSLT on the Java platform using the Java Collections Framework
with full integration with DOM, SAX and JAXP.
The new release and further documentation can be found at:-
http://dom4j.org
This release includes:-
*
Hi Edwin
> > I take it this is a bug in Crimson? Or is there another way to know when
you
> > are getting internal or external DTD declarations - that works
consistently
> > for Crimson and Xerces and can handle mixed subsets (internal and
external)?
>
> Yes, looks like a Crimson bug. Not sure I
The startDTD() method of the SAX LexicalHandler
http://dom4j.org/javadoc/org/xml/sax/ext/LexicalHandler.html
says on the topic of DTD declarations:-
Declarations are assumed to belong to the internal DTD subset unless
they appear between startEntity and endEntity events.
Now I've tried us
dom4j is a simple and flexible open source library for working with XML,
XPath and XSLT on the Java platform using the Java Collections Framework
with full integration with DOM, SAX and JAXP.
The new release and further documentation can be found at:-
http://dom4j.org
This release includes:-
*
dom4j is a simple and flexible open source library for working with XML,
XPath and XSLT on the Java platform using the Java Collections Framework
with full integration with DOM, SAX and JAXP.
The new release and further documentation can be found at:-
http://dom4j.org
This release is primarily
dom4j is a simple and flexible open source library for working with XML,
XPath and XSLT on the Java platform using the Java Collections Framework
with full integration with DOM, SAX and JAXP.
The new release and further documentation can be found at:-
http://dom4j.org
This release is primarily
dom4j is a simple and flexible open source library for working with XML,
XPath and XSLT on the Java platform using the Java Collections Framework
with full integration with DOM, SAX and JAXP.
The new release and further documentation can be found at:-
http://dom4j.org
This release is primarily
builder methods such that 'Element Construction Set' style
methods can be used to create documents
Element author = element.addElement( "author" )
.addAttribute( "name", "James" )
.addAttribute( "location", "
> Thanks for the ref. For the most part, this looks like exactly what
maverick
> domify is; and more.
>
> Do you know if JPath is limited to the Xalan (XSLT/XPATH) engine?
JPath should be usable wherever DOM is so you should be able to use it, via
JAXP (TRaX) to work with any XSLT engine or any X
You might find the work of Dmitri Plotnikov useful. He's done a full
JavaBeans <-> DOM implementation so that he can do XPath and XSLT on
JavaBeans. Its all part of the JPath project in the Jakarta Commons sandbox.
http://jakarta.apache.org/commons/sandbox.html
http://jakarta.apache.org/cvsweb/
From: "Curt Smith" <[EMAIL PROTECTED]>
> I'm looking for any subcomponent or whole parts of the framework that
delagates
> from the View JSP to XSLT to form the final output stream.
You might find XTags useful - its a JSP Tag library which is part of the
Jakarta Taglibs project
http://jakarta.ap
Hi Jun
> Thanks a lot. I downloaded dom4j, it does allow me to create a new
document
> from scratch. However, based on the given sample code, I still need to
hard
> code the element name, attribute name, ... how can I build the xml DOM
tree
> based on a given DTD file? You have any sample code in
dom4j is an easy to use, open source Java library for working with XML.
dom4j combines the best of DOM, SAX, XPath and the Java Collections
Framework to provide a flexible and powerful toolkit for working with XML
optimised to take advantage of the Java platform.
The new 0.4 release and further
19 matches
Mail list logo
