facebook

Websphere MDB xdoclet Configuration

💡
Our Forums Have Moved

For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub

  1. MyEclipse Archived
  2.  > 
  3. Application Servers and Deployment
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #235542 Reply

    halkasimi
    Member

    Websphere requires that the listener port be specified for an MDB. The xdoclet website shows that you can use @websphere.mdb tag to sepcify the listener port as in :


    @websphere
    .mdb listenerPort=”MyListenerPort”

    The MyEclipse xdoclet doesn’t seem to recognize this tag and it’s not available in auto-completion. I was thinking it might be that the xdoclet that comes with MyEclipse is a different version than the one on the website, but apparently the @websphere.mdb tag has been there for quite a whilte. Is there something I’m missing here ?

    Thanks,
    Hyder

    #235575

    Riyad Kalla
    Member

    Hyder,
    Do you have a link handy? I’ml ooking here and don’t see .mdb: http://xdoclet.sourceforge.net/xdoclet/ant/xdoclet/modules/ibm/websphere/ejb/WebSphereSubTask.html

    #235617

    halkasimi
    Member
    #235623

    Riyad Kalla
    Member

    I was able to reproduce this problem, thank you for the link. I will file this issue.

    #235649

    Riyad Kalla
    Member

    Hyder,
    After further analysis it seems that the XDoclet autocomplete is actually intelligently culling the autocomplete list based on the TYPE of class you are trying to complete for (e.g. it won’t give you EJB autocompletes if you are adding tags to a POJO).

    What is the full definition of the class you are trying to use @websphere tag on? What does it extend? What is the full class hierarchy of that class?

    I need to know because I need to create a reproducable test case to file with this issue.

    #235702

    halkasimi
    Member

    Hi,

    The class is an MDB that implements MessageDrivenBean and and MessageListener (see below). As you can see from the code, I manually added the @websphere.mdb tag but the ANT xdoclet still didn’t recognize it and didn’t add the proper entry to the META-INF/ibm-ejb-jar-bnd.xmi websphere file.

    Thanks,
    Hyder

    —————————————————————————————————
    package hello.ejb;

    import javax.ejb.EJBException;
    import javax.ejb.MessageDrivenBean;
    import javax.ejb.MessageDrivenContext;
    import javax.jms.Message;
    import javax.jms.MessageListener;

    /**
    * XDoclet-based Message Driven entity bean.
    *
    * To generate EJB related classes using XDoclet:
    *
    * – Add Standard EJB module to XDoclet project properties
    * – Customize XDoclet configuration
    * – Run XDoclet
    *
    * Below are the xdoclet-related tags needed for this EJB.
    *
    * @ejb.bean name=”HelloMDB”
    * display-name=”Name for HelloMDB”
    * description=”Description for HelloMDB”
    * destination-type=”javax.jms.Queue”
    * acknowledge-mode=”Auto-acknowledge”
    * @websphere.mdb listenerPort=”TaskListenerPort”
    */
    public class HelloMDB implements MessageDrivenBean, MessageListener {

    ….

    #235703

    Riyad Kalla
    Member

    Hyder,
    I’m using a internal build of 4.0 GA (will be released Monday) and autocomplete for @websphere at the class level works fine, I selected mdb and entered in all the information, this might be a bug in this version of MyEclipse you are using, but Monday try and upgrade to Eclipse 3.1 and MyEclipse 4.0 GA and see if everything is kosher. (we did a big refresh of the XDOclet libs for 4.0, so that might be it).

    #235709

    halkasimi
    Member

    Ok, I’ll try 4.0 GA on Monday and let you know if it work. By the way, I’m currently using 4.0 M3.

Viewing 8 posts - 1 through 8 (of 8 total)
Reply To: Websphere MDB xdoclet Configuration

You must be logged in to post in the forum log in