Thanks!

Looking through the forums and the blog example I got some ideas:

-For requests pages.xml can be used for view-ids such as article/* and 
gallery/*. The actions called can then use a FacesContext to get the parameters 
encoded in the URL through facesContext.getExternalContext().getPathInfo().

-For generated links (s:link, h:outputLink, ...?) I'll have to supply 
alternatives (extended versions) which support alternative ways of formatting 
the result, probably through a formatter class.

I haven't tested any of these and actually not written any code using Facelets 
and Seam yet, but does this sound reasonable? :-) I'll run some tests tomorrow. 
If it works it might be worthwhile to add extended tags (s:link, ...) which 
support different URL formatters and actions which parse different types of 
URLs to the Seam distribution. Please comment!

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967603#3967603

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967603
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to