This seems to be clean :-)

But I wish you could redesign -object.xml usage since it's quite confusing. 

I'm new to JBP (2 weeks) but I've used other portals. What I miss most in JPB 
is a import/export module (or backup/restore). There should be a way to 
redeploy a portal with its content easily. This is why probably many of us use 
-object.xml files, to keep a externalized definition of portal content.

But my impression is that these descriptors where designed as bootstrappers, 
i.e. to quickly build a portal core, and not as whole portal definition. This 
is why there are design issues like this (tab localization), which don't fit 
this goal.

What I'd like is to keep these descriptors as simple bootstrappers (i.e. 
without handling localization) and be able to export and import portal : 
structure, content, configuration, users, ... I've seen this was planned for 
2.8, great :-)

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

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

Reply via email to