Hi Costin,
There's a number of people from Sun in the Xerces community, so I think
that if there were a problem with the way things are done we would have
heard about it. And this seems to make sense too, both for historical
reasons (JAXP 1.0 had no transformation component at all) and because if a
product claiming to implement JAXP had to implement both halves, then you'd
have to get parsing services through the intermediation of an XSLT
processor. Not being able to have a freestanding parser implementing an
API with the word "parse" in its name would be rather odd. :)
Cheers,
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: [EMAIL PROTECTED]
|---------+---------------------------->
| | Costin Manolache |
| | <cmanolache@yahoo|
| | .com> |
| | |
| | 11/06/2002 02:08 |
| | PM |
| | Please respond to|
| | general |
| | |
|---------+---------------------------->
>---------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: is there such a thing as a common xml-apis.jar
|
|
|
|
|
>---------------------------------------------------------------------------------------------------------------------------------------------|
Did anyone checked the license on jaxp ?
I know some JSRs do not allow distribution of modified ( incomplete )
APIs.
I think someone should check that.
It may help to have some link to point that if people want a
'JAXP' implementation they need to download both xalan and xerces
( or just xalan - as it includes both ). Xerces distribution only
has 1/2 of JAXP.
Costin
On Wed, 2002-11-06 at 10:37, [EMAIL PROTECTED] wrote:
> 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?
>
> Personally, I believe that were Xerces to start shipping the transform
> interfaces, confusion would simply migrate from lists like this to Xerces
> lists... In the final analysis there's no way to demonstrate this one
way
> or the other except by trying the experiment--and then there's no way
back.
> So unless there were some really compelling reason to change, I for one
> wouldn't want to see Xerces change in the near future.
>
> But there are lots of other xerces committers. :) If folks want to
lobby,
> xerces-j-dev is the place to go.
>
> Cheers,
> Neil
> Neil Graham
> XML Parser Development
> IBM Toronto Lab
> Phone: 905-413-3519, T/L 969-3519
> E-mail: [EMAIL PROTECTED]
>
>
>
>
> |---------+---------------------------->
> | | Joe Germuska |
> | | <[EMAIL PROTECTED]|
> | | > |
> | | |
> | | 11/06/2002 01:09 |
> | | PM |
> | | Please respond to|
> | | general |
> | | |
> |---------+---------------------------->
> >
---------------------------------------------------------------------------------------------------------------------------------------------|
> |
|
> | To: [EMAIL PROTECTED]
|
> | cc:
|
> | Subject: Re: is there such a thing as a common xml-apis.jar
|
> |
|
> |
|
> >
---------------------------------------------------------------------------------------------------------------------------------------------|
>
>
>
> At 12:29 PM -0500 2002/11/06, [EMAIL PROTECTED] wrote:
> >Xerces has never shipped the transform half of JAXP. That's because
we've
> >always felt it's misleading to users--especially newbies--to ship
> >interfaces we neither need nor implement. If you just want a parser,
you
> >don't need to know about the transform half of JAXP and you can happily
> >stick with xerces; if you need an XSLT processor, you can grab Xalan
which
> >will come with an appropriate xerces implementation and all the APIs you
> >need. (Does Xalan ship our xmlParserAPIs file? I doubt they do; I hope
> >they don't. :) )
>
> Having been bitten by the same thing as James this week (using a
> Maven xml-apis.jar that didn't have the transformation part of JAXP),
> I would tend to agree with Shane -- just ship a single XML jar with
> all of JAXP, all of SAX, and all of DOM.
>
> The confusion could be dealt with with documentation, and the classes
> can't add up to more than a few kilobytes. I think the current
> situation is more confusing.
>
> But then, I'm not a Xerces committer either.
>
> Just my 2 shekels,
> Joe
>
> --
> --
> * Joe Germuska { [EMAIL PROTECTED] }
> "It's pitiful, sometimes, if they've got it bad. Their eyes get
> glazed, they go white, their hands tremble.... As I watch them I
> often feel that a dope peddler is a gentleman compared with the man
> who sells records."
> --Sam Goody, 1956
>
> ---------------------------------------------------------------------
> 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]
>
---------------------------------------------------------------------
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]
