You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure if this is possible with pojosr.
But given you have a blueprint XML file and use property-placeholder's, and you
define this in the XML file
<cm:property-placeholder id="myProperties" persistent-id="foo"/>
Then with Aries Blueprint, then because the pid is foo, then it will load the
etc/foo.cfg file from the file path that has the .properties.
I wonder if pojosr could support this convention. Then it allows you to keep
the XML as is, and still use pojosr to test it.
Any thoughts?
PS: Only by changing the XML and for example use default properties
<cm:property-placeholder id="blue" persistent-id="foo.cfg">
<cm:default-properties>
<cm:property name="bar" value="hello2"/>
</cm:default-properties>
</cm:property-placeholder>
Then I can properties works. But this is not desireable, as I want to maintain
the .cfg file and load the properties from that. Just as the real OSGi
container does.
Original issue reported on code.google.com by [email protected] on 24 Nov 2012 at 3:47
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 24 Nov 2012 at 3:47The text was updated successfully, but these errors were encountered: