Beginer
Hello everyone. I need to parse xml document how can I do it? --- This message was sent by Postaci Webmail. See www.trlinux.com for details.
[POLL] WASP Lite on Apache?
Background: WASP Lite for Java is a Web services framework developed by Systinet that supports SOAP 1.1, WSDL 1.1, and XML Schema 1999/2000/2001. Details, including binaries and documentation, can be found at http://www.systinet.com/products/wasp_lite/index.html. The product is currently distributed under a free commercial binary license. It has a large user base, many of whom have requested that we make the source available. A number of companies and individuals have expressed interest in contributing to the development of this code. The code has been developed using a modular approach, which should make it relatively easy for others to get comfortable with the code, and which should allow easy sharing of code with the SOAP and Axis projects. We would like to submit this proposal to the members of the Apache XML project for consideration of accepting this donation as a sub-project. Thank you very much for your attention to and consideration for this proposal. We look foward to your questions, comments, or concerns. Anne Thomas Manes CTO, Systinet (formerly Idoox) www.systinet.com - In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Looking for tools/ideas for filtering HTML
Use JTidy - http://sourceforge.net/projects/jtidy/ Thanks, dims --- Jaquiss, Robert [EMAIL PROTECTED] wrote: Hello: I have just joined this list, and am also a beginning Java programmer. I appologize if this is not a suitable question for this list. I need to write a filter for HTML pages. My goal is to read an HTML page, throwing away all the HTML code and just keeping a block of text that occurs near the bottom of the page. The HTML tags are liable to be unbalanced. There will be a P but no /P. I found a sample program that used the SAXparser, but it SAXparser doesn't seem to handle unbalanced tags. Ideas/comments would be appreciated. Thank you. Regards Robert Jaquiss = Davanum Srinivas - http://jguru.com/dims/ __ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com - In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] WASP Lite on Apache?
Sorry for cluttering up your mailbox -- I'm not sure why this was sent around again. As you can see, it was sent it on Monday. We plan to proceed by submitting the code to the Axis project. Best regards, Anne -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]] Sent: Monday, November 12, 2001 3:40 PM To: General@Xml. Apache. Org Subject: [POLL] WASP Lite on Apache? Background: WASP Lite for Java is a Web services framework developed by Systinet that supports SOAP 1.1, WSDL 1.1, and XML Schema 1999/2000/2001. Details, including binaries and documentation, can be found at http://www.systinet.com/products/wasp_lite/index.html. The product is currently distributed under a free commercial binary license. It has a large user base, many of whom have requested that we make the source available. A number of companies and individuals have expressed interest in contributing to the development of this code. The code has been developed using a modular approach, which should make it relatively easy for others to get comfortable with the code, and which should allow easy sharing of code with the SOAP and Axis projects. We would like to submit this proposal to the members of the Apache XML project for consideration of accepting this donation as a sub-project. Thank you very much for your attention to and consideration for this proposal. We look foward to your questions, comments, or concerns. Anne Thomas Manes CTO, Systinet (formerly Idoox) www.systinet.com - In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
XML APIs and JDK 1.4
Hi, On Eliotte Rusty Harold's Java news site (http://www.cafeaulait.org/2001november.html): Thursday, November 8, 2001 Sun's posted the Maintenance Review Draft Specification for JSR-000917 J2SE 1.4 (Merlin) Beta 3. Mostly this beta makes various minor tweaks in the API. The only major addition is an Endorsed Standards Override Mechanism. According to Sun, The Java 2 Platform includes a number of APIs that are governed by third-party endorsed standards. Examples are of such APIs are javax.rmi.CORBA.*, org.omg.*, and org.w3c.dom. Often software developers and vendors would like to use their own implementation of these APIs, or use a version of the external standard other than the version that is implemented in J2SE. To address this need, J2SE 1.4 supports the Endorsed Standards Override Mechansim, which makes use of new system property, java.endorsed.dirs. Review closes on December 10. The Endorsed Standards Override Mechanism is online here: http://java.sun.com/j2se/1.4/docs/guide/standards/index.html This looks quite significant. Without this, it seems JDK 1.4 users are stuck forevermore with the XML standards as they currently stand (DOM 2, SAX 2). I have not tried the 1.4 betas though.. does that sound correct? One remaining question: will it be possible for an application to override the default parser (crimson I think), or when 1.4 is released, are we stuck with that parser and it's bugs? So far, when it comes to standards, Microsoft have embrace and extend, and Sun have embrace and inadvertently hold back. I wish they'd leave XML out of the JDK, but failing that, I hope (and would like confirmation from this group) that they haven't killed the advancement of DOM and SAX in Java. --Jeff - In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Business-Oriented XML
Seems to me that here is some lack of homework... Have you ever had a look at Apache Cocoon project? That achieves all the benefits you outlined in your paper plus more. Check out http://xml.apache.org/cocoon and http://xml.apache.org/cocoon2... Rgds, Neeme -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dave Jarvis Sent: Friday, November 16, 2001 9:40 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: BOX: Business-Oriented XML Hello, Using Tomcat, Xalan, Xerces, and Java-based technologies, I have developed a system that completely decouples presentation from business logic. I would like to discuss the system and the possibility of adding it to the technologies offered by the Apache Foundation. Please find a brief architectural overview of the system online at the following address: http://www.joot.com/box/ For a more technical system description, please read the following page: http://www.joot.com/dave/writings/articles/bsp/ I look forward to your comments, critiques, and questions. Sincerely, Dave Jarvis - In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Business-Oriented XML
Hello, again.
Neeme Praks wrote:
Have you ever had a look at Apache Cocoon project? That achieves all the
Yes.
benefits you outlined in your paper plus more.
Here are a few items BOX addresses that Cocoon does not (as far as I can
discern; please correct my errors):
o doesn't provide an inherent state-based architecture (it's an aside,
not focus)
o doesn't automatically apply a different view of logic based on the
domain
o extremely complex; it mixes multiple languages and odd syntax (e.g.,
connectDatabase)
o makes it easy to couple presentation and logic (see below)
o lacks an integrated expression parser
o doesn't expose a consistent syntax for doing tasks such as:
- file I/O
- sending XML to remote servers
- calling native code (Java, C, Perl, etc.)
- SQL statements
o cookies, FORM parameters, and URL encoded variables are not treated
uniformly
o doesn't use plain XML (i.e., embeds other language source directly)
If there's interest, I would be more than happy to illustrate a full
cycle of data acquisition (via HTML FORM) to SQL deposit, retrieval, and
final HTML page. For those who enjoy gory details, I've made a brief
comparison of Cocoon and BOX for two very simple examples. The first is
a little counter program, the second shows how to do SQL in both
tongues.
Sincerely,
Dave Jarvis
-=( First Example )=-
]] Cocoon's Logic (18 lines of code; tied to Java) [[
?xml version=1.0?
?cocoon-process type=xsp?
?cocoon-process type=xslt?
?xml-stylesheet href=page-html.xsl type=text/xsl?
xsp:page language=java
xmlns:xsp=http://www.apache.org/1999/XSP/Core;
xsp:logic
static private int counter = 0;
private synchronized int count() {
return counter++;
}
/xsp:logic
page
pI've been requested xsp:exprcount()/xsp:expr times./p
/page
/xsp:page
]] Cocoon's XSP (6 lines of generated code) [[
?xml version=1.0?
?cocoon-process type=xslt?
?xml-stylesheet href=page-html.xsl type=text/xsl?
page
pI've been requested 0 times./p
/page
]] Cocoon's XSL (10 lines of code) [[
?xml version=1.0?
xsl:stylesheet
xsl:output method=html encoding=US-ASCII/
xsl:template match=page
xsl:apply-templates/
/xsl:template
xsl:template match=p
xsl:apply-templates/
/xsl:template
/xsl:stylesheet
BOX code, in my opinion, is much simpler and straightforward, as there
is no intermediary XSP page:
]] BOX's Logic (7 lines of code; tied to XML) [[
?xml version=1.0?
businessLogic
main
session name=count expr=#count + 1/
tag name=count expr=#count/
/main
/businessLogic
]] BOX's XML (4 lines of generated code) [[
?xml version=1.0?
document
count0/count
/document
]] BOX's XSL (7 lines of code) [[
?xml version=1.0?
xsl:stylesheet version=1.0
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xsl:output method=html encoding=US-ASCII/
xsl:template match=document
PI've been requested xsl:value-of select=count/ times./P
/xsl:template
/xsl:stylesheet
By adding babel tags around the English text, you automatically get
a stylesheet that is in the viewer's language (based on their browser's
Accept-Language). This is part of the architecture; no extra futzing is
required. BOX makes it difficult to couple logic and presentation. For
example, to write a p tag with logic, you must write tag
name=p/. XSL is where the p tag belongs; not snuggled in with
logic.
Let's look at a slightly more complex example, involving SQL. First
Cocoon, then BOX.
-=( Second Example )=-
]] Cocoon Logic (20 lines of code) [[
?xml version=1.0 encoding='ISO-8859-1' standalone=no?
?xml-stylesheet href=../xsl/wic_fournisseursListe.xsl
type=text/xsl?
?cocoon-process type=xsp?
?cocoon-process type=xslt?
!DOCTYPE page SYSTEM ./librairies/entity.dtd
xsp:page
language=java
xmlns:xsp=http://www.apache.org/1999/XSP/Core;
xmlns:session=http://www.apache.org/1999/XSP/Session;
xmlns:request=http://www.apache.org/1999/XSP/Request;
xmlns:response=http://www.apache.org/1999/XSP/Response;
xmlns:sql=http://www.apache.org/1999/SQL;
xmlns:log=http://www.arctis.com/2000/XSP/Log;
create-session=true
page title=Liste des fournisseurs
xsp:logic
try {
sql:execute-query
connectDatabase;
sql:doc-elementFOURNISSEURS/sql:doc-element
sql:row-elementFOURNISSEUR/sql:row-element
sql:query
SELECT * FROM WIC.FOURNIS
WHERE COD_CLIENT = 'session:get-value name=WIC_CLIENT/'
ORDER BY NOM_FOURNIS
/sql:query
/sql:execute-query
}
catch (Exception e) {
response:send-redirect location=wic_erreur.xml?Langue=FR/
}
/xsp:logic
/page
/xsp:page
]] Cocoon XSL (43 lines of code) [[
?xml version=1.0 encoding='ISO-8859-1'?
?cocoon-format type=text/xsl?
xsl:stylesheet version=1.0
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns=http://www.w3.org/TR/xhtml1/strict;
xsl:import
Re: Business-Oriented XML
On Fri, Nov 16, 2001 at 08:58:06PM -0800, Dave Jarvis wrote: Hello, again. Neeme Praks wrote: Have you ever had a look at Apache Cocoon project? That achieves all the Yes. benefits you outlined in your paper plus more. Here are a few items BOX addresses that Cocoon does not (as far as I can discern; please correct my errors): o doesn't provide an inherent state-based architecture (it's an aside, not focus) Nope, they threw out the reactor (state machine) pattern as being too hard to manage. o doesn't automatically apply a different view of logic based on the domain Certainly can :) Have a look at Cocoon 2's class org.apache.cocoon.selection.HostSelector. o extremely complex; it mixes multiple languages and odd syntax (e.g., connectDatabase) That's just your particular XSP, which uses an XML entity connectDatabase; to pull in other XSP. If you put your logic in logicsheets as intended, then your XSP pages are pure XML. o makes it easy to couple presentation and logic (see below) Actually, XSP makes it easy to mix *content* and logic (presentation is in XSLs). o lacks an integrated expression parser o doesn't expose a consistent syntax for doing tasks such as: - file I/O - sending XML to remote servers Have a look at Cocoon 2's xscript SOAP demo (xscript being an XSP equivalent of James Strachan's xtags taglib). - calling native code (Java, C, Perl, etc.) - SQL statements o cookies, FORM parameters, and URL encoded variables are not treated uniformly o doesn't use plain XML (i.e., embeds other language source directly) Anyway, if you've got time, hop on cocoon-dev.. I'm sure there's much mutual learning to be had (it's a fun place to lurk anyway). Cocoon 2 has a very generic architecture, and I've no doubt that your code could be integrated as an XSP alternative. --Jeff - In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
