actually you raise an interesting point. this is what we want to achieve, deployable wars that contains theme.
that would be possbile to have that with deployment descriptor like /WEB-INF/theme.xml. in that case the container would be capable to detect it and register it in a theme registry. What is left is the contract between the theme and the portal, i.e the API. For now it could be just request dispatching. Like you define the path for the theme in the theme.xml. You should work first on a simple theme deployer. That would scan war for theme.xml and register that against a registry that would be in the container. Something simple just a map of key to themes. Are you interested in ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866253#3866253 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866253 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
