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 already exists: "weblogic.j2ee.descriptor.filterbeani...@3018f5(/Filters[app])" at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:207) at weblogic.j2ee.descriptor.WebAppBeanImpl.setFilters(WebAppBeanImpl.java:703) Try to figure out why it is loading the same application again. I don't think it is because of Tapestry. Actually the application may be not configured on Weblogic server. Have a great time working on Tapestry....=) Regards from, Ritesh Sandupatla JAVA Developer -- View this message in context: http://www.nabble.com/Weblogic-9.2-with-JRockit-R26.0-throws-exception-for-Tapestry-Filter-tp15408301p21788877.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
