Oliver,
please look at recent comments that I added to
https://issues.apache.org/jira/browse/XALANJ-2264
The first issue is one of the user interface. I had suggested an option
something like:
-XMLPARSER setXIncludeAware(true)
and to use reflection to turn such options into API calls on the factory to
set the features.
But there is another issue.... that SAXParserFactory and
DocumentBuilderFactory are created in a number of places in the code.
Perhaps a central place would be better, this allowing a consistent setting
of options/features.
- Brian
Oliver Paulus
<[EMAIL PROTECTED]
ect.org> To
[email protected]
02/25/2006 07:58 cc
AM
Subject
Re: Fw: Xalan-J, Xerces-J XInclude
Please respond to question
xalan-dev
Hello Brian,
> sorry I didn't pick this up earlier.
No problem. I did not know if the mailinglist was the right one.
> You are interested in using the Process command rather than via some
> JAXP APIs, is that correct?
Yes, I want to use Xalan from the commandline and set XML parser
"features". I
am using Xalan as a normal user and want - if possible - avoid programming.
At
work I have to develop an XSLT to transform XML to XML. Currently the
XInclude
issue with XML Base (xml:base) is a problem to me because I am not
permitted to modify the target DTD.
The topic you have listed below is only for the XInclude issue - I think it
would be nice to have a general approach to give Xalan any "passthrough"
parameters for the XML parser. e.g. I call Xalan from the commandline
and Xalan
calls the setFeature (JAXP) Method for the given parameters. Is something
like
this possible?
Regards
Oliver Paulus
e-mail private: [EMAIL PROTECTED]
e-mail work: [EMAIL PROTECTED]
Quoting Brian Minchau <[EMAIL PROTECTED]>:
>
> Hi Oliver,
> sorry I didn't pick this up earlier. The xalan-dev mailing list is the
> correct one for this issue. You are interested in using the Process
command
> rather than via some JAXP APIs, is that correct?
>
> Recently opened was this JIRA issue which looks to be what you are
> interested in.
> http://issues.apache.org/jira/browse/XALANJ-2264
>
> That issue was opened by Rudolf Weber, but his attached patch is not
robust
> enough to be applied. This issue was discussed at the JIRA meeting and
the
> developers were concerned about the number of possible options in this
> area, so Xalan would probably be more interested in a generic way to pass
> through parameters to the XML parser rather than XInclude specifically.
So
> if you have suggestions that would be great.
>
> - Brian
> - - - - - - - - - - - - - - - - - - - -
> Brian Minchau
> XSLT Development, IBM Toronto
> e-mail: [EMAIL PROTECTED]
>
>
>
> "Paulus Oliver"
> <[EMAIL PROTECTED]
> emens.com> To
> <[email protected]>
> 02/24/2006 01:47 cc
> AM
> Subject
> RE: Xalan-J, Xerces-J XInclude
> Please respond to question
> general
>
>
>
>
>
>
>
>
>
> I have made my proposal on the xalan-dev mailing list some days ago but
> no one replied until now. Do you have any suggestion how to get in
> contact
> with the xalan development team?
>
> Regards
> Oliver Paulus
>
> -----Original Message-----
> From: Michael Glavassevich [mailto:[EMAIL PROTECTED]
> Sent: Sonntag, 19. Februar 2006 04:40
> To: [email protected]
> Subject: RE: Xalan-J, Xerces-J XInclude question
>
> "Paulus Oliver" <[EMAIL PROTECTED]> wrote on 02/16/2006 01:40:27
>
> AM:
>
>> Hello Peter,
>>
>> thank you for your help (so far). I have seen in the Xalan java code
>> that there is no option to give him "passthrough" parameters for the
> XML
>> parser (Xerces in this case). I think it could be useful for the users
> -
>> what do you think?
>
> Sounds useful to me. You might want to start a discussion on the
> xalan-dev
> [1] mailing list.
>
> [1] http://xml.apache.org/mail.html#xalan-dev
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: [EMAIL PROTECTED]
> E-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> 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]
>
>
>
> ---------------------------------------------------------------------
> 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
