Re: pls. solve my problem

Hi Pandurang,

The part of stack trace you have posted doesn't convey enough. The root cause of
the exception needs to be examined by looking at the complete stack trace.

A lot of times, the DescriptorException is due to BeanAlreadyExistsException.
This indicates duplication, and violation of a uniqueness constraint. If you
have a BeanAlreadyExistsException, look for it's message to get a hint on which
element this exception is about. For example, let's assume you see an exception
like:
weblogic.descriptor.BeanAlreadyExistsException: Bean already exists:
weblogic.j2ee.descriptor.ServletBeanImpl@db3943e4(/Se
rvlets[Foo]
..

"/Servlets" indicates that <servlet> element's uniqueness
constraint is being violated. And, "[Foo]" indicates that the
duplicate value is "Foo". Now, if you look at the schema, you'd see
that <servlet-name> has to be unique among all occurrences of
<servlet>. That means that there are multiple <servlet> elements in
your DD that have the <servlet-name> set to "Foo".

In case BeanAlreadyExistsException is not the cause of your DescriptorExcep