Given that componentA uses the screens of componentB and componentB makes use
of its own decorator screens.
After some analysis, I discovered that when componentB's screen uses its own
decorator screens specified with
location="${parameters.mainDecoratorLocation}", the value of 'location'
attribute actually refers to componentA's directory as specified in
componentA's web.xml.
Hence, I can solve the problem by, when referring to decorator screens,
replacing location="${parameters.mainDecoratorLocation}" to
location="component://componentB/widget/CommonScreens.xml#SomeDecoratorScreen".
Ie. hardcoding the location of componentB's decorator screen file.
Thanks all for helping out.
Wai
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/one-component-includes-a-screen-from-another-component-clarification-tp3875463p3878611.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
