You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by Niklas Gustavsson <ni...@protocol7.com> on 2009/08/03 12:43:59 UTC
Re: svn commit: r800255 - in /mina/sandbox/vysper/trunk/server/core/src/main:
config/ java/org/apache/vysper/xmpp/state/presence/ resources/
On Mon, Aug 3, 2009 at 10:32 AM, <be...@apache.org> wrote:
> move ehcache.xml to config/ where it resides together with the other configurations.
ehcache.xml should probably be in src/main/resources if we want to
ship it with Vysper, or in src/test/resources if we only want it for
our unit tests. Currently, mvn test fails and having it in
src/main/config also requires manual setup in IDEs. We should probably
look into moving all config files in either src/main/resources or
src/test/resources.
/niklas
Re: svn commit: r800255 - in /mina/sandbox/vysper/trunk/server/core/src/main:
config/ java/org/apache/vysper/xmpp/state/presence/ resources/
Posted by Bernd Fondermann <bf...@brainlounge.de>.
Ashish wrote:
> On Mon, Aug 3, 2009 at 5:23 PM, Niklas Gustavsson<ni...@protocol7.com> wrote:
>> On Mon, Aug 3, 2009 at 1:44 PM, Ashish<pa...@gmail.com> wrote:
>>> ehcache.xml shall ship with Vysper. Also, it may need to be customized by user.
>> If we stick it in src/main/resources,
+1
>> it might be hard to customize by
>> the user unless ehcache has some reasonable way of handling multiple
>> configurations on the classpath.
All the config files are in .../config respective .../resources (and we
should move them all to /resources, but not scatter them around). This
works pretty good as far as I can see.
>
> Not sure if ehcache can handle multiple classpath entries. Working on
> resolving this
>
> Otherwise what's the best way to handle such situation?
I think you did the right thing. You just missed the "/" in
getResource(). It worked for me, see my latest commit on this.
Bernd
Re: svn commit: r800255 - in /mina/sandbox/vysper/trunk/server/core/src/main:
config/ java/org/apache/vysper/xmpp/state/presence/ resources/
Posted by Ashish <pa...@gmail.com>.
On Mon, Aug 3, 2009 at 6:20 PM, Niklas Gustavsson<ni...@protocol7.com> wrote:
> On Mon, Aug 3, 2009 at 2:15 PM, Ashish<pa...@gmail.com> wrote:
>> Not sure if ehcache can handle multiple classpath entries. Working on
>> resolving this
>>
>> Otherwise what's the best way to handle such situation?
>
> One way would be not loading from classpath but instead feed the
> configuration from a user configured value (like set using DI or a
> system property).
This is better. Let me create a JIRA for this.
As of now, lets use a constructor for passing the file name and can
refine this if needed
wdyt?
> /niklas
>
--
thanks
ashish
Blog: http://www.ashishpaliwal.com/blog
My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: svn commit: r800255 - in /mina/sandbox/vysper/trunk/server/core/src/main:
config/ java/org/apache/vysper/xmpp/state/presence/ resources/
Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Mon, Aug 3, 2009 at 2:15 PM, Ashish<pa...@gmail.com> wrote:
> Not sure if ehcache can handle multiple classpath entries. Working on
> resolving this
>
> Otherwise what's the best way to handle such situation?
One way would be not loading from classpath but instead feed the
configuration from a user configured value (like set using DI or a
system property).
/niklas
Re: svn commit: r800255 - in /mina/sandbox/vysper/trunk/server/core/src/main:
config/ java/org/apache/vysper/xmpp/state/presence/ resources/
Posted by Ashish <pa...@gmail.com>.
On Mon, Aug 3, 2009 at 5:23 PM, Niklas Gustavsson<ni...@protocol7.com> wrote:
> On Mon, Aug 3, 2009 at 1:44 PM, Ashish<pa...@gmail.com> wrote:
>> ehcache.xml shall ship with Vysper. Also, it may need to be customized by user.
>
> If we stick it in src/main/resources, it might be hard to customize by
> the user unless ehcache has some reasonable way of handling multiple
> configurations on the classpath.
Not sure if ehcache can handle multiple classpath entries. Working on
resolving this
Otherwise what's the best way to handle such situation?
> /niklas
>
--
thanks
ashish
Blog: http://www.ashishpaliwal.com/blog
My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: svn commit: r800255 - in /mina/sandbox/vysper/trunk/server/core/src/main:
config/ java/org/apache/vysper/xmpp/state/presence/ resources/
Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Mon, Aug 3, 2009 at 1:44 PM, Ashish<pa...@gmail.com> wrote:
> ehcache.xml shall ship with Vysper. Also, it may need to be customized by user.
If we stick it in src/main/resources, it might be hard to customize by
the user unless ehcache has some reasonable way of handling multiple
configurations on the classpath.
/niklas
Re: svn commit: r800255 - in /mina/sandbox/vysper/trunk/server/core/src/main:
config/ java/org/apache/vysper/xmpp/state/presence/ resources/
Posted by Ashish <pa...@gmail.com>.
> On Mon, Aug 3, 2009 at 10:32 AM, <be...@apache.org> wrote:
>> move ehcache.xml to config/ where it resides together with the other configurations.
>
> ehcache.xml should probably be in src/main/resources if we want to
> ship it with Vysper, or in src/test/resources if we only want it for
> our unit tests. Currently, mvn test fails and having it in
> src/main/config also requires manual setup in IDEs. We should probably
> look into moving all config files in either src/main/resources or
> src/test/resources.
ehcache.xml shall ship with Vysper. Also, it may need to be customized by user.
Thinking about this, should we think about a cache provider like
implementation, wherein we can plugin custom providers like ehcache,
jboss cache,or oscache?
Configuring it by use of properties would be big plus
Kept it in resources, as my tests weren't able to find it in config :-(
+1 to keep it in resources
--
thanks
ashish