, 20 de janeiro de 2011 20:53
Para: dev@shindig.apache.org
Assunto: Re: Define container.js in a war project
Thank you all.
I like the final Idea from Maxwell.
I think it is a good idea to give a possibilities to handle custom
resources
ourselves.
I will try to install the properties from my
Thank you all.
I like the final Idea from Maxwell.
I think it is a good idea to give a possibilities to handle custom resources
ourselves.
I will try to install the properties from my shindig module.
Just FYI, I am using in my project a dependency on shindig and I do not want
to patch shindig jar
Hey everyone,
I'm trying to write a new EndToEnd test patterned after the others that are
under java/server. However, when I attempt to use gadgets.util.hasFeature
() or gadgets.util.getFeatureParameters() functions they always return
null. I am adding tests for some new changes so I may have
You can provide your own shindig.properties by putting it in a local
classpath before the shindig jar. You might consider implementing a
system property to override the path (look at how we did it with
shindig.port)
On Wed, Jan 19, 2011 at 2:47 PM, Ryan J Baxter rjbax...@us.ibm.com wrote:
Hi
I do not like the idea to work with classpath priorities, I did create a
simple PropertiesModule in my project, something like:
CustomPropertiesModule extends AbstractModule {
public void configure(){
install(new PropertiesModule(your-properties-file);
}
}
I think would be a better approach,
