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 <igor.vaynb...@gmail.com>: > 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 <a.zw...@finan.nl> 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 <a.zw...@finan.nl> 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
