Hi Sudarshan,
I think this may be because of Weblogic trying to load the application more
than once
since there is some problem in deployment descriptor as per the cause of
this exception
looking at the stack strace lines -
Caused by: weblogic.descriptor.BeanAlreadyExistsException: Bean alrea
Hi Sudarshan,
I think this may be because of Weblogic trying to load the application more
than once
since there is some problem in deployment descriptor as per the cause of
this exception
looking at the stack strace lines -
Caused by: weblogic.descriptor.BeanAlreadyExistsException: Bean alread
Hi Ritesh,
I am trying to deploy a Tepastry 5 application context in my Weblogic 9.2
domain, which is configured with Sun's 1.5 JDK (jdk1.5.0_12)
However, when I try to activate changes in my Weblogic 9.2 console post
deployment activities, I get the following message in my Admin console
--
I've had very bad results with JRockit. At one client BEA had to
encourage the client to deploy with Sun's JDK owing to a memory
management issue that caused great memory thrash on load. This was a
BEA Portal app - no tapestry. It was crazy. And we validated the
problem with a sample ap
