Andy Clark wrote :
> > > (-) Remove the Attribute Entity Information
> >
> > If you are talking about removing all the entity related methods
> > from the XMLAttributes interface and adding utility classes instead,
> > it would be a good idea 'cause attributes donot have entity
> > references when we use a schema grammar.
>
> I don't see how this is related to simplifying the
> XMLAttributes interface.
>
Your point was, remove all the entity related stuff from the XMLAttributes
interface and use the non-normalized value to get the entity information thro'
a utility class which breaks it up and retrieves the entity information.
Agreed to this.
But in addition to that, i have one other point in mind which supports the above
removal.
When we deal with Schemas, we have only predefined entites and character
references (no general & parameter entities) appearing within attribute values
which means there's not much to be done with entities in this case. So,
including methods like addAttributeEntity(),removeEntityAt()... in XMLAttribute
interface and entityCount,entityName[]... in XMLAttributesImpl is a significant
overhead.
> > > (+) Add Non-Normalized Value to Internal Entity Decl
> >
> > This is, of course, needed if we remove the entity related methods from
> > XMLAttributes interface.
>
> That's not really the point of adding the information but,
> you're right, it does allow the entity information to be
> retrieved if the entities are removed from the
> XMLAttributes interface. But the added information in the
> callback would also be useful for knowing what parameter
> entities were used within other parameter entities. This
> is the point that I started thinking about after hearing
> of James Clark's tool.
>
Agreed.
Pavani
--
Pavani Mukthipudi
Sun Microsystems Inc.
Phone: 080 - 2298989 Extn: 87390
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
