[ http://issues.apache.org/jira/browse/XALANJ-2119?page=all ]

Brian Minchau updated XALANJ-2119:
----------------------------------

     Environment: 
     Description: 
The SAX startElement() call on a serializer does some extra fix up to ensure 
that a namespace declaration exists for the element's namespace. This is in the 
code ToStream.ensurePrefixIsDeclared(String ns, String rawName).

I think that the user of the serializer should give the startPrefixMapping() 
call, before the startElement() call, rather than have the serializer cover up 
for the callers usage bug.

This is a performance issue as a fair chunk of time can be spent doing this for 
every element.

  was:
The SAX startElement() call on a serializer does some extra fix up to ensure 
that a namespace declaration exists for the element's namespace. This is in the 
code ToStream.ensurePrefixIsDeclared(String ns, String rawName).

I think that the user of the serializer should give the startPrefixMapping() 
call, before the startElement() call, rather than have the serializer cover up 
for the callers usage bug.

This is a performance issue as a fair chunk of time can be spent doing this for 
every element.

    fix-priority: fp4

Set to fp4 due to JIRA meeting on June 7,2005.

> The SAX serializer accepts startElement() calls for elements whose prefix is 
> not yet declared.
> ----------------------------------------------------------------------------------------------
>
>          Key: XALANJ-2119
>          URL: http://issues.apache.org/jira/browse/XALANJ-2119
>      Project: XalanJ2
>         Type: Bug
>   Components: Serialization
>     Reporter: Brian Minchau
>     Priority: Minor

>
> The SAX startElement() call on a serializer does some extra fix up to ensure 
> that a namespace declaration exists for the element's namespace. This is in 
> the code ToStream.ensurePrefixIsDeclared(String ns, String rawName).
> I think that the user of the serializer should give the startPrefixMapping() 
> call, before the startElement() call, rather than have the serializer cover 
> up for the callers usage bug.
> This is a performance issue as a fair chunk of time can be spent doing this 
> for every element.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to