| issue with XDocletBuilder [message #144664] |
Thu, 20 October 2005 11:25  |
Eclipse User |
|
|
|
Hi,
We are using WTP 0.7 and in the ejb project we are having a peculiar
issue. We a stateless session bean called CustomerFacadeBean. When we make
any changes to CustomerFacadeBean, it generated CustomerFacadeSession (and
other interfaces). First time there isnt any problem. But if we make a
change again to CustomerFacadeBean it generated CustomerFacadeSession and
also it made CustomerFacadeSession as a stateless session bean and
generated it CustomerFacadeSessionSession (all the other interfaces for
CustomerFacadeSession ).
I went through the XDoxletAnnotationUtil code and found that XDocletFinder
is checking if it is a XDoclet resource and couldnt find any issue.
After some playing i found the issue.
it boiled to the following xdoclet sub tag
@weblogic.enable-call-by-reference True
if this tag is the last one in the defination, it gives a error so i mode
this above the @ejb.bean tag like this
* <!-- begin-xdoclet-definition -->
*
* @weblogic.enable-call-by-reference True
*
* @ejb.bean name="CustomerFacade"
* description="CustomerFacade for accessing customer
information"
* display-name="CustomerFacade"
* jndi-name="CustomerFacade"
* local-jndi-name="CustomerFacadeLocal"
* type="Stateless"
* transaction-type="Container"
*
*
*
* <!-- end-xdoclet-definition -->
then this error happens.
if i remove the @weblogic.enable-call-by-reference True , this doesnt
happen.
So i think the AST syntax (or the way the XDocletFinder checking) has a
issue
regards,
Lachu
|
|
|
| Re: issue with XDocletBuilder [message #144732 is a reply to message #144664] |
Thu, 20 October 2005 13:15  |
| Eclipse User |
|
|
|
Originally posted by: david.schneider.unisys.com
I encountered similar problems using the word "Session" in my bean names.
Since then, I stopped using key words at the end of my bean names and
haven't had any further problems. Based on this experience, I'd be very
cautious using anything with Session, Local, Util, Home, ... at the end of
my bean names.
"Lachu" <lakshmanan.ramakrishnan@citigroup.com> wrote in message
news:6ece69f4e297d4468d5c678e0a15fb9e$1@www.eclipse.org...
> Hi,
>
> We are using WTP 0.7 and in the ejb project we are having a peculiar
> issue. We a stateless session bean called CustomerFacadeBean. When we make
> any changes to CustomerFacadeBean, it generated CustomerFacadeSession (and
> other interfaces). First time there isnt any problem. But if we make a
> change again to CustomerFacadeBean it generated CustomerFacadeSession and
> also it made CustomerFacadeSession as a stateless session bean and
> generated it CustomerFacadeSessionSession (all the other interfaces for
> CustomerFacadeSession ).
>
> I went through the XDoxletAnnotationUtil code and found that XDocletFinder
> is checking if it is a XDoclet resource and couldnt find any issue.
> After some playing i found the issue.
>
> it boiled to the following xdoclet sub tag
>
> @weblogic.enable-call-by-reference True
> if this tag is the last one in the defination, it gives a error so i mode
> this above the @ejb.bean tag like this
>
> * <!-- begin-xdoclet-definition -->
> * * @weblogic.enable-call-by-reference True * * @ejb.bean
> name="CustomerFacade" * description="CustomerFacade for
> accessing customer information"
> * display-name="CustomerFacade"
> * jndi-name="CustomerFacade"
> * local-jndi-name="CustomerFacadeLocal"
> * type="Stateless" * transaction-type="Container"
> *
> * * * <!-- end-xdoclet-definition -->
> then this error happens.
>
> if i remove the @weblogic.enable-call-by-reference True , this doesnt
> happen.
>
> So i think the AST syntax (or the way the XDocletFinder checking) has a
> issue
>
> regards,
> Lachu
>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03094 seconds
Home