cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Wagner" <dwag...@sa.kevric.com>
Subject RE: XMLResourceBundle
Date Fri, 30 Jun 2000 17:27:30 GMT
Neeme Praks wrote
> 
> I would also like to add the ability to have nested groups, but the
> implementation of this was a little bit too much for me right now.
> The idea is to allow this kind of contructs:
> 
> 	<res:group ref="/resources/forms/contacts-search/input">
> 		<res:group ref="field-to-search">
> 			<res:resource ref="email"/><!-- XPath:
> /resources/forms/contacts-search/input/field-to-search/email -->
> 			<res:group
> ref="/resources/forms/contacts-search/desc">
> 				<res:resource ref="searchfor"/><!--
> XPath: /resources/forms/contacts-search/desc/searchfor -->
> 			</res:group>
> 		</res:group>
> 		<res:resource ref="submit"/><!-- XPath:
> /resources/forms/contacts-search/input/submit -->
> 		<res:resource
> ref="/resources/forms/contacts-search/desc/from"/>
> 	</res:group>
> 
> And maybe also using ".." for going up one level? Something like
this:
> 
> 	<res:group ref="/resources/forms/contacts-search/input">
> 		<res:group ref="field-to-search">
> 			<res:group ref="../desc">
> 				<res:resource ref="searchfor"/><!--
> XPath: /resources/forms/contacts-search/desc/searchfor -->
> 			</res:group>
> 		</res:group>
> 	</res:group>
> 
> If someone would like to take a challenge and implement all these
> features then go ahead... I don't need it right now, so I 
> don't want to
> get a headache from this...
>
I have seen dicussed on this list the implementation of xml:base
handling.  If this is so, I'd suggest using the xml:base attribute on
your group elements for the path.  Use your ref attribute just for the
terminal resource name if this is needed on the group element.  No
need to reimplement that wheel!
-David

Mime
View raw message