I do, one that used SUN's jaxb. But since it was using <java
fork="true"> internally, most of the processing done should be easily
applicable to Oracle's Jaxb I suppose. I posted it in BugZilla a while
back. --DD
On 6/22/06, Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote:
Hi,
in the makes I am taking care now, we are using a macrodef built around
oracle.xml.jaxb.orajaxb. It has 3 disadvantages :
- *not* really failing on error,
- when the XSD's are wrong, the error message is laconic
- processes one schema at a time, not a complete fileset
Anyone has a custom task to do this ?
Regards,
Antoine
sample error message :
XML-32009: (Fatal Error) Failed to parse the input schema.
<java classname="oracle.xml.jaxb.orajaxb"
fork="true"
failonerror="true"
maxmemory="128m"
classpathref="orajaxb.path"
output="logs/jaxb.log"
append="true"
logError="true"
>
<!-- Have to split arguments because schema path has space in it.
-->
<arg value="-outputDir"/>
<arg value="@{outputDir}"/>
<arg value="-schema"/>
<arg value="@{schema}"/>
<arg value="-targetPkg"/>
<arg value="@{targetPkg}"/>
</java>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
