Thanks for catching this.
Done in revision 539548.
-Donald
Jarek Gawor wrote:
In my case that would be SwitchingServiceRefBuilder.java. But I think
the same problem could happen in other builders too. I'm +1 for
log.warn() change.
Jarek
On 5/18/07, Donald Woods <[EMAIL PROTECTED]> wrote:
Whi
On May 18, 2007, at 10:42 AM, Jarek Gawor wrote:
In my case that would be SwitchingServiceRefBuilder.java. But I think
the same problem could happen in other builders too. I'm +1 for
log.warn() change.
I'm good with that...
Donald,
Can you make this happen?
--kevan
In my case that would be SwitchingServiceRefBuilder.java. But I think
the same problem could happen in other builders too. I'm +1 for
log.warn() change.
Jarek
On 5/18/07, Donald Woods <[EMAIL PROTECTED]> wrote:
Which changed file is throwing the exception? ResourceRefBuilder.java?
We can turn
Which changed file is throwing the exception? ResourceRefBuilder.java?
We can turn the throw() into a log.warn() for now, until this EJB case is
fixed
-Donald
Jarek Gawor wrote:
Recently the GERONIMO-348 patch was committed. That is causing
problems with EJB deployments. Here's an exam
Recently the GERONIMO-348 patch was committed. That is causing
problems with EJB deployments. Here's an example.
ejb-xml.jar has 2 ejbs, and one of the ejbs has a service-ref entry:
The G plan has corresponding entries for the beans and one service-ref
overwrite.
Now, during deploym
