Re: wicket.properties conflict 1.2.6 vs 1.4.1

[nino martinez wael]

You can use a named class loader...

So EarA and EarB will not have the same class loaders.. Unless they
use the same class loader, which you would have to specify separately,
further more you can bring JBoss back to compliance by a setting
AFAIK.

2009/9/14 Olivier Bourgeois :
> I think you have to put them in different wars and not to use
> UnifiedClassloader. The wars have access to the ear classloader (otherwise
> they would not have access to the EJBs) so putting 1.2.3 on the ear
> classpath and 1.4.x on the war classpath should not work.
>
> 2009/9/14 nino martinez wael 
>
>> I meant ear files
>>
>> 2009/9/14 nino martinez wael :
>> > You can if you put them in different wars.. That will work.
>> >
>> > We have a similar setup that does this.
>> >
>> > 2009/9/14 Olivier Bourgeois :
>> >> Except that you can parameter JBoss to use an "optimization" of its own
>> :
>> >> UnifiedClassloader :
>> >>
>>
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: wicket.properties conflict 1.2.6 vs 1.4.1

[Olivier Bourgeois]

I think you have to put them in different wars and not to use
UnifiedClassloader. The wars have access to the ear classloader (otherwise
they would not have access to the EJBs) so putting 1.2.3 on the ear
classpath and 1.4.x on the war classpath should not work.

2009/9/14 nino martinez wael 

> I meant ear files
>
> 2009/9/14 nino martinez wael :
> > You can if you put them in different wars.. That will work.
> >
> > We have a similar setup that does this.
> >
> > 2009/9/14 Olivier Bourgeois :
> >> Except that you can parameter JBoss to use an "optimization" of its own
> :
> >> UnifiedClassloader :
> >>
>

Re: wicket.properties conflict 1.2.6 vs 1.4.1

[Igor Vaynberg]

if the two apps are deployed as two separate apps then they should not
see each other's jars and therefore should not see each other's
wicket.properties files.

-igor

On Mon, Sep 14, 2009 at 4:08 AM, A. Zwaan  wrote:
> Sorry about the late reply, the migration was put on hold for a couple of 
> days as some higher priority project needed some extra resources.
>
> The wicket 1.2.6 jar is in an ear file, which is one of the applications. The 
> 1.4.1 jar is included in a war file, which is the other application. Both are 
> deployed with the same JBoss instance.
>
> To my knowledge this should work as both wicket versions use different 
> packages and therefore should not conflict with each other. The only problem 
> seems to be in that both wicket versions still look for ALL the 
> wicket.properties files, which probably results in one being overwritten and 
> both applications trying to load the same Initializer class.
>
>
> -Original Message-
> From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
> Sent: woensdag 9 september 2009 17:47
> To: users@wicket.apache.org
> Subject: Re: wicket.properties conflict 1.2.6 vs 1.4.1
>
> are you sharing your wicket jars? is both 1.2.6 and 1.4.1 in a servlet
> container's shared lib dir?
>
> -igor
>
> On Wed, Sep 9, 2009 at 6:09 AM, A. Zwaan  wrote:
>> Hello all,
>>
>>
>>
>> At the moment we migrated one of our applications to wicket 1.4.1 to
>> solve an issue, but some of our other application are still running on
>> wicket 1.2.6.
>>
>>
>>
>> Now we ran into a problem with wicket.properties, both wicket versions
>> use the same file and both versions look up ALL the wicket.properties
>> files on the classpath, which results in one of both application loading
>> the wrong Initializer class. Running in separate server instances is a
>> possibility of course, but atm we already have too many of them, so we
>> prefer to run within one server instance.
>>
>>
>>
>> Is there any way around this issue?
>>
>>
>>
>> Also why didn't wicket choose to use a differently named properties file
>> (only used internally) for the new wicket version?
>>
>> It would have allowed to run both version within the same instance
>> without much problems (packages are different already anyway).
>>
>>
>>
>> Thanks in advance.
>>
>>
>>
>>
>>
>> Met vriendelijke groet,
>>
>>
>>
>> Arjan Zwaan
>>
>> F I N A N  F i n a n c i a l   A n a l y s i s
>>
>>
>> Koggelaan 5-D
>> 8017 JH Zwolle
>>
>> ( Tel. : +31 88 77 88 990
>>
>> 7 E-mail: a.zw...@finan.nl <mailto:a.zw...@finan.nl>
>>
>> : Internet: www.finan.nl <http://www.finan.nl/>
>> (Findesk BV) KvK nr. 29039392
>>
>>
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: wicket.properties conflict 1.2.6 vs 1.4.1

[nino martinez wael]

It depends if the 1.2.6 one is in a shared class loader of that ear...

But as you mention the 1.4.1 will only be visible in the one war file.
However in that one it would have both 1.2.6 and 1.4.1 visible thus
having a conflict..:(

2009/9/14 Igor Vaynberg :
> if the two apps are deployed as two separate apps then they should not
> see each other's jars and therefore should not see each other's
> wicket.properties files.
>
> -igor
>
> On Mon, Sep 14, 2009 at 4:08 AM, A. Zwaan  wrote:
>> Sorry about the late reply, the migration was put on hold for a couple of 
>> days as some higher priority project needed some extra resources.
>>
>> The wicket 1.2.6 jar is in an ear file, which is one of the applications. 
>> The 1.4.1 jar is included in a war file, which is the other application. 
>> Both are deployed with the same JBoss instance.
>>
>> To my knowledge this should work as both wicket versions use different 
>> packages and therefore should not conflict with each other. The only problem 
>> seems to be in that both wicket versions still look for ALL the 
>> wicket.properties files, which probably results in one being overwritten and 
>> both applications trying to load the same Initializer class.
>>
>>
>> -Original Message-
>> From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
>> Sent: woensdag 9 september 2009 17:47
>> To: users@wicket.apache.org
>> Subject: Re: wicket.properties conflict 1.2.6 vs 1.4.1
>>
>> are you sharing your wicket jars? is both 1.2.6 and 1.4.1 in a servlet
>> container's shared lib dir?
>>
>> -igor
>>
>> On Wed, Sep 9, 2009 at 6:09 AM, A. Zwaan  wrote:
>>> Hello all,
>>>
>>>
>>>
>>> At the moment we migrated one of our applications to wicket 1.4.1 to
>>> solve an issue, but some of our other application are still running on
>>> wicket 1.2.6.
>>>
>>>
>>>
>>> Now we ran into a problem with wicket.properties, both wicket versions
>>> use the same file and both versions look up ALL the wicket.properties
>>> files on the classpath, which results in one of both application loading
>>> the wrong Initializer class. Running in separate server instances is a
>>> possibility of course, but atm we already have too many of them, so we
>>> prefer to run within one server instance.
>>>
>>>
>>>
>>> Is there any way around this issue?
>>>
>>>
>>>
>>> Also why didn't wicket choose to use a differently named properties file
>>> (only used internally) for the new wicket version?
>>>
>>> It would have allowed to run both version within the same instance
>>> without much problems (packages are different already anyway).
>>>
>>>
>>>
>>> Thanks in advance.
>>>
>>>
>>>
>>>
>>>
>>> Met vriendelijke groet,
>>>
>>>
>>>
>>> Arjan Zwaan
>>>
>>> F I N A N  F i n a n c i a l   A n a l y s i s
>>>
>>>
>>> Koggelaan 5-D
>>> 8017 JH Zwolle
>>>
>>> ( Tel. : +31 88 77 88 990
>>>
>>> 7 E-mail: a.zw...@finan.nl <mailto:a.zw...@finan.nl>
>>>
>>> : Internet: www.finan.nl <http://www.finan.nl/>
>>> (Findesk BV) KvK nr. 29039392
>>>
>>>
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: wicket.properties conflict 1.2.6 vs 1.4.1

[nino martinez wael]

I meant ear files

2009/9/14 nino martinez wael :
> You can if you put them in different wars.. That will work.
>
> We have a similar setup that does this.
>
> 2009/9/14 Olivier Bourgeois :
>> Except that you can parameter JBoss to use an "optimization" of its own :
>> UnifiedClassloader :
>>
>>
>> http://www.jboss.org/community/wiki/classloadingconfiguration
>>>
>>> In jboss-3.2.3, the jbossweb-tomcat41.sar is configured to use a unified
>>> class loader as the web application class loader. This is controlled by the
>>> UseJBossWebLoader attribute in the
>>> jbossweb-tomcat41.sar/META-INF/jboss-service.xml descriptor. The use of a
>>> unified class loader means that the classes available in the war inside of
>>> the WEB-INF/classes and WEB-INF/lib are incorporated into the default shared
>>> class loader repository. This may not be what you want as its contrary to
>>> the default servlet 2.3 class loading model and can result in sharing of
>>> classes/resources between web applications. You can disable this by setting
>>> this attribute to false.
>>>
>>
>>
>> That is, if this setting is activated all webapps are sharing the same
>> classloader, which is of course not J2EE standard, and you can't use two
>> different versions of Wicket.
>>
>> 2009/9/14 Igor Vaynberg :
>>> if the two apps are deployed as two separate apps then they should not
>>> see each other's jars and therefore should not see each other's
>>> wicket.properties files.
>>>
>>> -igor
>>>
>>> On Mon, Sep 14, 2009 at 4:08 AM, A. Zwaan  wrote:
 Sorry about the late reply, the migration was put on hold for a couple of
>> days as some higher priority project needed some extra resources.

 The wicket 1.2.6 jar is in an ear file, which is one of the applications.
>> The 1.4.1 jar is included in a war file, which is the other application.
>> Both are deployed with the same JBoss instance.
>>
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: wicket.properties conflict 1.2.6 vs 1.4.1

[nino martinez wael]

You can if you put them in different wars.. That will work.

We have a similar setup that does this.

2009/9/14 Olivier Bourgeois :
> Except that you can parameter JBoss to use an "optimization" of its own :
> UnifiedClassloader :
>
>
> http://www.jboss.org/community/wiki/classloadingconfiguration
>>
>> In jboss-3.2.3, the jbossweb-tomcat41.sar is configured to use a unified
>> class loader as the web application class loader. This is controlled by the
>> UseJBossWebLoader attribute in the
>> jbossweb-tomcat41.sar/META-INF/jboss-service.xml descriptor. The use of a
>> unified class loader means that the classes available in the war inside of
>> the WEB-INF/classes and WEB-INF/lib are incorporated into the default shared
>> class loader repository. This may not be what you want as its contrary to
>> the default servlet 2.3 class loading model and can result in sharing of
>> classes/resources between web applications. You can disable this by setting
>> this attribute to false.
>>
>
>
> That is, if this setting is activated all webapps are sharing the same
> classloader, which is of course not J2EE standard, and you can't use two
> different versions of Wicket.
>
> 2009/9/14 Igor Vaynberg :
>> if the two apps are deployed as two separate apps then they should not
>> see each other's jars and therefore should not see each other's
>> wicket.properties files.
>>
>> -igor
>>
>> On Mon, Sep 14, 2009 at 4:08 AM, A. Zwaan  wrote:
>>> Sorry about the late reply, the migration was put on hold for a couple of
> days as some higher priority project needed some extra resources.
>>>
>>> The wicket 1.2.6 jar is in an ear file, which is one of the applications.
> The 1.4.1 jar is included in a war file, which is the other application.
> Both are deployed with the same JBoss instance.
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: wicket.properties conflict 1.2.6 vs 1.4.1

[Olivier Bourgeois]

Except that you can parameter JBoss to use an "optimization" of its own :
UnifiedClassloader :


http://www.jboss.org/community/wiki/classloadingconfiguration
>
> In jboss-3.2.3, the jbossweb-tomcat41.sar is configured to use a unified
> class loader as the web application class loader. This is controlled by the
> UseJBossWebLoader attribute in the
> jbossweb-tomcat41.sar/META-INF/jboss-service.xml descriptor. The use of a
> unified class loader means that the classes available in the war inside of
> the WEB-INF/classes and WEB-INF/lib are incorporated into the default shared
> class loader repository. This may not be what you want as its contrary to
> the default servlet 2.3 class loading model and can result in sharing of
> classes/resources between web applications. You can disable this by setting
> this attribute to false.
>


That is, if this setting is activated all webapps are sharing the same
classloader, which is of course not J2EE standard, and you can't use two
different versions of Wicket.

2009/9/14 Igor Vaynberg :
> if the two apps are deployed as two separate apps then they should not
> see each other's jars and therefore should not see each other's
> wicket.properties files.
>
> -igor
>
> On Mon, Sep 14, 2009 at 4:08 AM, A. Zwaan  wrote:
>> Sorry about the late reply, the migration was put on hold for a couple of
days as some higher priority project needed some extra resources.
>>
>> The wicket 1.2.6 jar is in an ear file, which is one of the applications.
The 1.4.1 jar is included in a war file, which is the other application.
Both are deployed with the same JBoss instance.

RE: wicket.properties conflict 1.2.6 vs 1.4.1

[A. Zwaan]

Sorry about the late reply, the migration was put on hold for a couple of days 
as some higher priority project needed some extra resources.

The wicket 1.2.6 jar is in an ear file, which is one of the applications. The 
1.4.1 jar is included in a war file, which is the other application. Both are 
deployed with the same JBoss instance.

To my knowledge this should work as both wicket versions use different packages 
and therefore should not conflict with each other. The only problem seems to be 
in that both wicket versions still look for ALL the wicket.properties files, 
which probably results in one being overwritten and both applications trying to 
load the same Initializer class.


-Original Message-
From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] 
Sent: woensdag 9 september 2009 17:47
To: users@wicket.apache.org
Subject: Re: wicket.properties conflict 1.2.6 vs 1.4.1

are you sharing your wicket jars? is both 1.2.6 and 1.4.1 in a servlet
container's shared lib dir?

-igor

On Wed, Sep 9, 2009 at 6:09 AM, A. Zwaan  wrote:
> Hello all,
>
>
>
> At the moment we migrated one of our applications to wicket 1.4.1 to
> solve an issue, but some of our other application are still running on
> wicket 1.2.6.
>
>
>
> Now we ran into a problem with wicket.properties, both wicket versions
> use the same file and both versions look up ALL the wicket.properties
> files on the classpath, which results in one of both application loading
> the wrong Initializer class. Running in separate server instances is a
> possibility of course, but atm we already have too many of them, so we
> prefer to run within one server instance.
>
>
>
> Is there any way around this issue?
>
>
>
> Also why didn't wicket choose to use a differently named properties file
> (only used internally) for the new wicket version?
>
> It would have allowed to run both version within the same instance
> without much problems (packages are different already anyway).
>
>
>
> Thanks in advance.
>
>
>
>
>
> Met vriendelijke groet,
>
>
>
> Arjan Zwaan
>
> F I N A N  F i n a n c i a l   A n a l y s i s
>
>
> Koggelaan 5-D
> 8017 JH Zwolle
>
> ( Tel. : +31 88 77 88 990
>
> 7 E-mail: a.zw...@finan.nl <mailto:a.zw...@finan.nl>
>
> : Internet: www.finan.nl <http://www.finan.nl/>
> (Findesk BV) KvK nr. 29039392
>
>
>
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: wicket.properties conflict 1.2.6 vs 1.4.1

[Igor Vaynberg]

are you sharing your wicket jars? is both 1.2.6 and 1.4.1 in a servlet
container's shared lib dir?

-igor

On Wed, Sep 9, 2009 at 6:09 AM, A. Zwaan  wrote:
> Hello all,
>
>
>
> At the moment we migrated one of our applications to wicket 1.4.1 to
> solve an issue, but some of our other application are still running on
> wicket 1.2.6.
>
>
>
> Now we ran into a problem with wicket.properties, both wicket versions
> use the same file and both versions look up ALL the wicket.properties
> files on the classpath, which results in one of both application loading
> the wrong Initializer class. Running in separate server instances is a
> possibility of course, but atm we already have too many of them, so we
> prefer to run within one server instance.
>
>
>
> Is there any way around this issue?
>
>
>
> Also why didn't wicket choose to use a differently named properties file
> (only used internally) for the new wicket version?
>
> It would have allowed to run both version within the same instance
> without much problems (packages are different already anyway).
>
>
>
> Thanks in advance.
>
>
>
>
>
> Met vriendelijke groet,
>
>
>
> Arjan Zwaan
>
> F I N A N  F i n a n c i a l   A n a l y s i s
>
>
> Koggelaan 5-D
> 8017 JH Zwolle
>
> ( Tel. : +31 88 77 88 990
>
> 7 E-mail: a.zw...@finan.nl 
>
> : Internet: www.finan.nl 
> (Findesk BV) KvK nr. 29039392
>
>
>
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

wicket.properties conflict 1.2.6 vs 1.4.1

[A. Zwaan]

Hello all,

 

At the moment we migrated one of our applications to wicket 1.4.1 to
solve an issue, but some of our other application are still running on
wicket 1.2.6.

 

Now we ran into a problem with wicket.properties, both wicket versions
use the same file and both versions look up ALL the wicket.properties
files on the classpath, which results in one of both application loading
the wrong Initializer class. Running in separate server instances is a
possibility of course, but atm we already have too many of them, so we
prefer to run within one server instance.

 

Is there any way around this issue?

 

Also why didn't wicket choose to use a differently named properties file
(only used internally) for the new wicket version?

It would have allowed to run both version within the same instance
without much problems (packages are different already anyway).

 

Thanks in advance.

 

 

Met vriendelijke groet,

 

Arjan Zwaan

F I N A N  F i n a n c i a l   A n a l y s i s 

 
Koggelaan 5-D
8017 JH Zwolle

( Tel. : +31 88 77 88 990

7 E-mail: a.zw...@finan.nl  

: Internet: www.finan.nl  
(Findesk BV) KvK nr. 29039392