Is there any chance you can post your cs code again if you still have it? The current link is broken. Much appreciated.

if you haven`t done so, please check the Prana forum. There is a post about using embedded xml within the container and Erik recently added support for this. See the post at http://prana.herrodius.com/viewtopic.php?f=3&t=19

To answer your questions:

1. I haven`t done that before but I think it should be perfectly `legal` to do so.

2. There hasn`t been any design to handle naming conflicts right now. The last object will always win I suppose. I`ll try to check how spring handles this.

I’ve been trying to use Prana to make our app modular or rather make Cairngorm modular which means that each module can add to the service locator and create its own controller. Because in my case it makes more sense to load embedded XMLs I implemeneted my own XML factory which just takes an XML object. On top of sits custom ApplicationContext which is just a wrapper around the factory. The factory mimics what the original XMLObjectFactory does (no XML merging, no imports though) by calling the XMLObjectDefinitionParser. With the orignal and my own implementations I tried two approches when each module adds to a single ApplicationContext instance or creates new ones. Some differences in behaviour in the latter case broght two questions I wanted to ask you:

1. Should the load/loadConfigLocation method be called only once in a factory/application context life time?
2. I found that the custom implmentations does not have issues with naming conflicts although in debug mode I can see that all of the objects defined in both files are there. It is not the case with the XMLApplicationContext and the underlying XML object factory. When lets say both configs contain a serviceLocator named the same the singleton won’t have services added later on. A similar thing happens with the CairngormFrontController - if the parameter holding commands’ package name is called the same it fails since the first value is applied to the instance created later on. Just wondering if it is an intended behaviour and if lack of those errors with the custom implementation is a side effect of some kind…

Cheers,
Bartek

[ResourceBundle(”forms”)]
public class MultiFileUpload extends UIComponent { … }

and set values in the class with resourceManager.getString(’form’,'MY_KEY’)
but how/can do I get them to update AFTER the class has been instantiated?

For example I have a FileUpload class and want UI elements (column titles of a file list data grid) to changes if the language is changed.

Thanks a lot

the broswer of amfphp see the data base ans their enter but dont give me their value.
bye

Thanks for this fix. As a side note, you will also get this error if you make a mistake when inputting VM arguments. For instance, I forgot the ‘-’ in front of one of my VM args and got the same error, so if the above fix doesn’t work then check your VM args.