| Bug in plugin.xml parsing in Eclipse. [message #443928] |
Mon, 04 October 2004 16:24  |
 Harry Pendergrass
Messages: 10
Registered: July 2009 |
Junior Member |
|
|
It seems that in the process of parsing the plugin.xml file, the xml is
divided up into 2K chunks. The ExtensionParser method characters(char[],
int, int) has these chunks passed to it by the SAXParser class in the
process of filling in the value of the currentConfigElement. If one of your
xml elements happens to cross the 2K border, it is possible for its value to
be processed in two substring which are then concatenated. The problem is
that though the method calls translate on the individual pieces of the
string, it does not call translate on the concatenated string. So, if the
value of an element is a key into the .properties file and it happens to
fall across the 2K boundary, it will not be translated. Instead the key
will be used as the value of the element.
Has anybody else run into mysterious cases where resource keys in the
plugin.xml file are being used verbatim rather than substituted with their
values from the plugin.properties file? If so, this may be why.
-Harry Pendergrass,
IBM
|
|
|
| Re: Bug in plugin.xml parsing in Eclipse. [message #443934 is a reply to message #443928] |
Mon, 04 October 2004 16:58  |
Veronika Irvine
Messages: 1272
Registered: July 2009 |
Senior Member |
|
|
You should ask this question in the eclipse.platform newsgroup.
news://news.eclipse.org/eclipse.platform
"Harry Pendergrass" <htpender@us.ibm.com> wrote in message
news:cjrslj$19v$1@eclipse.org...
> It seems that in the process of parsing the plugin.xml file, the xml is
> divided up into 2K chunks. The ExtensionParser method characters(char[],
> int, int) has these chunks passed to it by the SAXParser class in the
> process of filling in the value of the currentConfigElement. If one of
> your
> xml elements happens to cross the 2K border, it is possible for its value
> to
> be processed in two substring which are then concatenated. The problem is
> that though the method calls translate on the individual pieces of the
> string, it does not call translate on the concatenated string. So, if the
> value of an element is a key into the .properties file and it happens to
> fall across the 2K boundary, it will not be translated. Instead the key
> will be used as the value of the element.
>
> Has anybody else run into mysterious cases where resource keys in the
> plugin.xml file are being used verbatim rather than substituted with their
> values from the plugin.properties file? If so, this may be why.
>
> -Harry Pendergrass,
> IBM
>
>
|
|
|
| Re: Bug in plugin.xml parsing in Eclipse. [message #443936 is a reply to message #443934] |
Mon, 04 October 2004 17:41 |
Harry Pendergrass
Messages: 10
Registered: July 2009 |
Junior Member |
|
|
Okay. You are right. My mistake. I'll do that.
Thanks Veronika.
"Veronika Irvine" <veronika_irvine@oti.com> wrote in message
news:cjrv6o$6gn$1@eclipse.org...
> You should ask this question in the eclipse.platform newsgroup.
>
> news://news.eclipse.org/eclipse.platform
>
> "Harry Pendergrass" <htpender@us.ibm.com> wrote in message
> news:cjrslj$19v$1@eclipse.org...
> > It seems that in the process of parsing the plugin.xml file, the xml is
> > divided up into 2K chunks. The ExtensionParser method
characters(char[],
> > int, int) has these chunks passed to it by the SAXParser class in the
> > process of filling in the value of the currentConfigElement. If one of
> > your
> > xml elements happens to cross the 2K border, it is possible for its
value
> > to
> > be processed in two substring which are then concatenated. The problem
is
> > that though the method calls translate on the individual pieces of the
> > string, it does not call translate on the concatenated string. So, if
the
> > value of an element is a key into the .properties file and it happens to
> > fall across the 2K boundary, it will not be translated. Instead the key
> > will be used as the value of the element.
> >
> > Has anybody else run into mysterious cases where resource keys in the
> > plugin.xml file are being used verbatim rather than substituted with
their
> > values from the plugin.properties file? If so, this may be why.
> >
> > -Harry Pendergrass,
> > IBM
> >
> >
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02885 seconds
] 
Search
Help
Register
Login
Home
