Yeah... this is not at all consistent. We've got some env entries that
persist (older ones), but the new ones that we've added recently won't
stick. I've also noticed that orion-ejb-jar.xml acts very strangely when we
freshly deploy an app that has one included in the ear file. It isn't
copied over, and so we have to manually copy it into place, and even then,
this other rewriting thing happens. Seems like that area of the code got
thoroughly messed up in the last release. We didn't have this problem in
older versions.
Thanks all for the info... we'll work around it until the bug fix comes out.
Rian
----- Original Message -----
From: Alex Paransky <[EMAIL PROTECTED]>
To: Orion-Interest <[EMAIL PROTECTED]>
Sent: Saturday, July 21, 2001 10:35 AM
Subject: RE: Disappearing env-entry-mapping from orion-ejb-jar.xml
> That's strange, we have made extensive modifications to our orion-ejb-jar
in
> the area of query specifications, and they seem to persist ok. The thing
we
> could not get working is the max-tx-retry parameter keeps resetting to
"3",
> but Magnus said it was fixed in the next release, 1.5.3 I assume.
>
> -AP_
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of elephantwalker
> Sent: Friday, July 20, 2001 9:59 PM
> To: Orion-Interest
> Subject: RE: Disappearing env-entry-mapping from orion-ejb-jar.xml
>
>
> not just env-entry-mapping, its just about everything in the
> orion-ejb-jar.xml file.
>
> This is bug 512. I had the problem with group-role mapping. Buts its the
> same thing, when server restarts or redeploys the app the
orion-ejb-jar.xml
> is GENERATED and not COPIED.
>
> You will have to regress to version 1.5.1 as a workaround.
>
> Regards,
>
> the elephantwalker
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Rian Schmidt
> Sent: Friday, July 20, 2001 9:21 PM
> To: Orion-Interest
> Subject: Disappearing env-entry-mapping from orion-ejb-jar.xml
>
>
> Hi,
>
> Does anyone have any idea why we would be seeing an env-entry-mapping
> disappear from orion-ejb-jar.xml upon deployment? There is a stateless
> session bean that reads a value
> <env-entry-mapping name="databaseType">MSSQL</env-entry-mapping>
> from a stateless session beans entry in orion-ejb-jar.xml.
> And upon deployment the first time, it spits out the right value over and
> over (we're forcing it to read the value each time another bean uses the
> stateless session bean to read it). But when we restart the server, the
> bean reports the default value instead of the mapped one. What's more,
the
> entry is completely gone from the orion-ejb-jar.xml file.
>
> I can provide more information, but I thought I'd check first if this
smacks
> of anything obvious.
>
> Thanks,
> Rian
>
>
>
>
