This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
This is not implemented as a PropertyPlaceholderConfigurer though. The loading happens in the XMLObjectFactory. The parsing is implemented as an IXMLObjectDefinitionsPreprocessor. Check the PropertiesPreprocessor class for that.
We currently don't support ResourceLoader, but I think we might refactor the XMLObjectFactory to use this.
Do you have any specific use case where this functionality could be used?
My flex app is being used within MDM Zinc and Adobe AIR, so I am not loading the app via a webpage. Currently I load the context via an embedded XML file and passing that into the Prana context via "addConfig".
My question is will the property file you mentioned above still work in this scenario? How will the context attempt to locate <property file="application-context.properties.txt"/>?
Regarding ResourceLoaders, i already created my own use for this. My need stems from the ability to make it easier to embed and access things in an app. I created an EmbeddedResourceService, which takes a custom class that implements an IEmbedder interface. You then call embeddedResourceService.getResource([key]) and it yields a ByteArray of the data.
The developer must simply create a custom class in the project that uses my library and he defines all the Embeds for his entire project there in one place, keying them by a unique name. This class must just implement the IEmbedder interface which defines an "getResource(key:String)" method.
It helps to keep the overall app cleaner by centrally locating all Embeds for an application.
I tried to move my my configuration data into a property file assuming that they follow the usual Java syntax until I found out that comments (lines starting with #) do not work at all. It would be desirable to be able to add comments for documentation purpose and to play with settings (like URLs) by commenting/uncommenting while debugging or testing.