run.jar pointing to the sun parser shouldn't matter if you just remove the
parser jar file and add another one to the classpath.
Tom
On Fri, 9 Mar 2001, Kimpton,C (Chris) wrote:
> Hi,
>
> > > > -----Original Message-----
> > > > From: Tom Cook [mailto:[EMAIL PROTECTED]]
> > > >
> > > > On Wed, 7 Mar 2001, Kimpton,C (Chris) wrote:
> > > >
> > > > >
> > > > > NOTE The jars in the project are still the sun ones - and
> > > > will need to be
> > > > > until the scripts/other libs are independant of them too....
> > > >
> > > > Is that necessary? Why not just build with the sun stuff,
> > > > then you can
> > > > put apache/whatever in later if you want...
> > > >
> > >
> >
>
> > But this is exactly what I'm trying to help you avoid. Deciding which
> > parser jboss should use should be a configure-time/runtime
> > decision. It
> > shouldn't matter whether build.xml refers to it or not, you
> > should just be
> > able to change a configuration file on the deployed server
> > and it'll all
> > work.
> >
>
> Strangely ;-) - that is what I am trying to do - I think we are close to
> this now - what stops us, is the fact that jbossmq relies on the sun parser
> - so we can't replace it on a deployed server yet. Also the run.jar has the
> sun parser jar file hardcoded into its classpath (in the manifest file).
>
> I have tried changing jbossmq - but for some reason it did not restart post
> my change and I havn't tracked down the problem yet...
>
> Although, I think it cleaner if the parser can be changed at any point and
> thus the thoughts on changing build.xml etc.
>
> > Sorry, I'm being over-persistent - but I am trying to save you effort.
> >
>
> No problem - I do tend to wander a little too easily these days - maybe I am
> getting old - or just not enough practice using XP ;-)
>
> Chris
>
>
>================================================================================================
> This electronic message (email) and any attachments to it are subject to copyright
>and are sent for the personal attention of the addressee. Although you may be the
>named recipient, it may become apparent that this email and its contents are not
>intended for you and an addressing error has been made. This email may include
>information that is legally privileged and exempt from disclosure. If you have
>received this email in error, please advise us immediately and delete this email and
>any attachments from your computer system.Rabobank International is the trading name
>of Co�peratieve Centrale Raiffeisen-Boerenleenbank B.A. which is incorporated in the
>Netherlands. Registered with the Registrar of Companies for England & Wales No.
>BR002630 and regulated by the SFA for the conduct of investment business in the UK.
>
> The presence of this footnote also confirms that this email has been automatically
>checked by Rabobank International for the presence of computer viruses prior to it
>being sent, however, no guarantee is given or implied that this email is virus free
>upon delivery.
>
>
>
>
--
"If you mess with something for long enough it will break."
- Schmidt's law of engineering
