| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
PR: 96631
Submitted by: Ion-Mihai Tetcu <itetcu@people.tecnik93.com>
|
| |
|
|
|
|
|
|
|
| |
- Use 'exec' in the launcher shell script to comply with Porter's Handbook
guidelines
- Use OPTIONS to add support for JDom and XOM [1]
PR: 86093 [1]
Suggested by: Rene Ladan <r.c.ladan@student.tue.nl> [1]
|
| | |
|
| |
|
|
|
|
| |
Saxon 8.6.x is a complete and conformant implementation of the Candidate
Recommendations for XSLT 2.0, XQuery 1.0, and XPath 2.0 published on 3 November
2005
|
| |
|
|
|
|
|
|
| |
- No longer install saxon8-jdom.jar ; it will be back soon but as an OPTIONal
component
PR: 86093
Submitted by: Rene Ladan <r.c.ladan@student.tue.nl>
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
it is not possible (AFAICT) to port for now, due to the GUI installer used by
Sun. JAXP 1.3 is included in J2SE 1.5 so Saxon 8.2 will be back in the ports
tree when we get a working JDK 1.5.
- Rename a temporary variable to keep portlint(1) happy
|
| |
|
|
| |
- Use SUB_FILES/SUB_LIST for launcher shell script
|
| |
|
|
|
| |
- Track the recent changes to java/javavmwrapper
- Various cosmetic changes
|
| |
|
|
|
|
|
|
| |
parser are included in JDK 1.4+ Standard API)
- Tweaked CLASSPATH in launcher script: Only Saxon installed JARs are indeed
required for command-line operations (see above)
- Added some more "" in launcher script to ensure spaces in paths and args will
not break anything
|
| |
|
|
|
|
|
|
|
|
| |
- New launcher script 'saxon-xquery' to perform XQuery queries
- PREFIX -> LOCALBASE in launcher script
- (CP ; CHOWN) -> CPIO
- Register run dependency on Xerces-J
- Dynamic plist
- More relevant homepage URL in pkg-descr
- Take maintainership
|
| |
|
|
|
|
|
|
|
|
| |
by bsd.java.mk during the build. This fixes a problems where the
javavmwrapper (used by the script) could have potentially picked an
incorrect JDK to use.
. Bump PORTREVISION.
PR: 69157
Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
|
|
|
"The Saxon 8.0 package is a collection of tools for processing XML documents.
The main components are:
- An XSLT 2.0 processor, that can be used from the command line, or invoked
from a Java application by use of the standard JAXP API. Saxon can be
integrated with Java applications using the JAXP API, which means it is
possible for a Java application to switch between different XSLT processors
without changing the application code. As well as conforming closely with the
XSLT 2.0 specification, Saxon offers a number of powerful extensions.
- An XPath 2.0 processor accessible via an API to Java applications.
- An XQuery 1.0 processor that can be used from the command line, or invoked
from a Java application by use of an API.
- An XML Schema 1.0 processor. This can be used on its own to validate a schema
for correctness, or to validate a source document against the definitions in
a schema. It is also used to support the schema-aware functionality of the
XSLT and XQuery processors.
So you can use Saxon to process XML by writing XSLT stylesheets, by writing
XQuery queries, by writing Java applications, or by combinations of the
approaches."
PR: 68637
Submitted by: Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
|
