The following issue has been updated:

    Updater: Jason Childers (mailto:[EMAIL PROTECTED])
       Date: Mon, 8 Nov 2004 3:10 AM
    Comment:
Andrew,

Thanks for the feedback, I was wondering if that was the case.  I had seen the 
container-configuration tag, but didn't think it worked for Jboss 3.2 in the 
same way that the invoker-proxy-bindings do.  My latest attached patch.diff 
contains the added XDtConfig:ifConfigParamEquals with a value of 3.2.

Incidentally, I've been looking for an explanation of the difference between 
the jboss_xml.xdt and the jboss-bean-body.xdt files.  I can't seem to tell if 
the tags I've added should contain the same code, or if everything is as it 
should be.

I'm gonna be on vacation all of next week, so if I don't reply in the 
meantime... that's likely why.

Thanks,
-Jason





    Changes:
             Attachment changed to patch.diff
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1138?page=history

---------------------------------------------------------------------
View the issue:
  http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1138

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XDT-1138
    Summary: jboss.invoker-proxy-binding tag for MDBs needed
       Type: New Feature

     Status: Open
   Priority: Major

 Original Estimate: 2 days
 Time Spent: Unknown
  Remaining: 2 days

    Project: XDoclet
 Components: 
             JBoss Module
   Versions:
             1.2.2

   Assignee: xdoclet-devel (Use for new issues)
   Reporter: Jason Childers

    Created: Sat, 6 Nov 2004 4:22 PM
    Updated: Mon, 8 Nov 2004 3:10 AM

Description:
We need a way to specify the jboss.invoker-proxy-binding so that MDBs can bind 
to different JMSProviders other than the DefaultJMSProvider.  The appropriate 
xml for an MDB should look something like...

<message-driven>
    <ejb-name>FooMDB</ejb-name>                
<destination-jndi-name>queue/FooQueue</destination-jndi-name>
    <invoker-bindings>
        <invoker>
<invoker-proxy-binding-name>whatever-message-driven-bean</invoker-proxy-binding-name>
        </invoker>
    </invoker-bindings>
</message-driven>

This issue can be noted from in the jboss forums: 
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=43817
Search for: "How do I configure an MDB to talk to remote queue."

-Jason


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/xdoclet/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to