Comments on: Calling EJB3 with Mule and test it with OpenEJB http://www.redstream.nl/2009/04/01/calling-ejb3-with-mule-and-test-it-with-openejb/ Pragmatic Integrators Tue, 18 Oct 2011 12:18:20 +0000 hourly 1 By: Pascal Alma http://www.redstream.nl/2009/04/01/calling-ejb3-with-mule-and-test-it-with-openejb/comment-page-1/#comment-332 Pascal Alma Wed, 01 Apr 2009 17:33:39 +0000 http://www.pascalalma.net/?p=703#comment-332 Hi Andrew, Thx for your comment. About the discrepancies: 1. I only guessed for a reason why EJB3 connector wasn't supplied as OOTB functionality. I read somewhere that JDK1.4 had to be supported by Mule but I guess that was an outdated article (always the risk when looking for info on the net, I guess) 2. I guess you have a point here. But the first thing I tried when I wanted to call an EJB3 bean from within Mule is to google around and all you find is 'complaints' that there is no OOTB functionality for it. So that's why I looked further and came to the above 'solution'. 3. Yep, I understand. And there is nothing wrong with it I guess, as soon as you know that this is the way to do it. That's why I wrote this post: to show others who are running into the same issue how they can solve it. In this post (http://www.mail-archive.com/user@mule.codehaus.org/msg10294.html) the writer says the component way is the natuaral way to go. Since I am fairly new to Mule I assumed that this meant it is also the 'best ' way to accomplish this, that's why I went for this solution. So, I hope this clarifies the thing a little. But nevertheless I am still impressed by the functionality that Mule offers and I will certainly look into it in more detail! Hi Andrew,
Thx for your comment.
About the discrepancies:
1. I only guessed for a reason why EJB3 connector wasn’t supplied as OOTB functionality. I read somewhere that JDK1.4 had to be supported by Mule but I guess that was an outdated article (always the risk when looking for info on the net, I guess)
2. I guess you have a point here. But the first thing I tried when I wanted to call an EJB3 bean from within Mule is to google around and all you find is ‘complaints’ that there is no OOTB functionality for it. So that’s why I looked further and came to the above ‘solution’.
3. Yep, I understand. And there is nothing wrong with it I guess, as soon as you know that this is the way to do it. That’s why I wrote this post: to show others who are running into the same issue how they can solve it.

In this post (http://www.mail-archive.com/user@mule.codehaus.org/msg10294.html) the writer says the component way is the natuaral way to go. Since I am fairly new to Mule I assumed that this meant it is also the ‘best ‘ way to accomplish this, that’s why I went for this solution.

So, I hope this clarifies the thing a little. But nevertheless I am still impressed by the functionality that Mule offers and I will certainly look into it in more detail!

]]> By: Pascal Alma http://www.redstream.nl/2009/04/01/calling-ejb3-with-mule-and-test-it-with-openejb/comment-page-1/#comment-732 Pascal Alma Wed, 01 Apr 2009 17:33:39 +0000 http://www.pascalalma.net/?p=703#comment-732 Hi Andrew, Thx for your comment. About the discrepancies: 1. I only guessed for a reason why EJB3 connector wasn't supplied as OOTB functionality. I read somewhere that JDK1.4 had to be supported by Mule but I guess that was an outdated article (always the risk when looking for info on the net, I guess) 2. I guess you have a point here. But the first thing I tried when I wanted to call an EJB3 bean from within Mule is to google around and all you find is 'complaints' that there is no OOTB functionality for it. So that's why I looked further and came to the above 'solution'. 3. Yep, I understand. And there is nothing wrong with it I guess, as soon as you know that this is the way to do it. That's why I wrote this post: to show others who are running into the same issue how they can solve it. In this post (http://www.mail-archive.com/user@mule.codehaus.org/msg10294.html) the writer says the component way is the natuaral way to go. Since I am fairly new to Mule I assumed that this meant it is also the 'best ' way to accomplish this, that's why I went for this solution. So, I hope this clarifies the thing a little. But nevertheless I am still impressed by the functionality that Mule offers and I will certainly look into it in more detail! Hi Andrew,
Thx for your comment.
About the discrepancies:
1. I only guessed for a reason why EJB3 connector wasn’t supplied as OOTB functionality. I read somewhere that JDK1.4 had to be supported by Mule but I guess that was an outdated article (always the risk when looking for info on the net, I guess)
2. I guess you have a point here. But the first thing I tried when I wanted to call an EJB3 bean from within Mule is to google around and all you find is ‘complaints’ that there is no OOTB functionality for it. So that’s why I looked further and came to the above ‘solution’.
3. Yep, I understand. And there is nothing wrong with it I guess, as soon as you know that this is the way to do it. That’s why I wrote this post: to show others who are running into the same issue how they can solve it.

In this post (http://www.mail-archive.com/user@mule.codehaus.org/msg10294.html) the writer says the component way is the natuaral way to go. Since I am fairly new to Mule I assumed that this meant it is also the ‘best ‘ way to accomplish this, that’s why I went for this solution.

So, I hope this clarifies the thing a little. But nevertheless I am still impressed by the functionality that Mule offers and I will certainly look into it in more detail!

]]> By: Andrew Perepelytsya http://www.redstream.nl/2009/04/01/calling-ejb3-with-mule-and-test-it-with-openejb/comment-page-1/#comment-333 Andrew Perepelytsya Wed, 01 Apr 2009 13:12:09 +0000 http://www.pascalalma.net/?p=703#comment-333 Hi Pascal, Nice entry, thanks for this post. I've noticed some discrepancies though: 1. Mule has been targeted for Java 5 for several releases now, not 1.4. 2. I'm not sure what you mean by 'ejb3 is not OOTB functionality'. There's nothing Mule can do here, ejb3 don't make remote interfaces mandatory, it's up to a user to provide and expose those if needed. 3. We deliberately didn't duplicate lookup functionality already available and working fine in Spring. In this blog an ejb is simply injected as a service component (and could come from anywhere). Another option could be to use Mule's ejb transport, however it requires ejb2-style interfaces exposed (again, this is the optional compatibility layer in ejb3 spec). Cheers! Hi Pascal,

Nice entry, thanks for this post. I’ve noticed some discrepancies though:

1. Mule has been targeted for Java 5 for several releases now, not 1.4.
2. I’m not sure what you mean by ‘ejb3 is not OOTB functionality’. There’s nothing Mule can do here, ejb3 don’t make remote interfaces mandatory, it’s up to a user to provide and expose those if needed.
3. We deliberately didn’t duplicate lookup functionality already available and working fine in Spring.

In this blog an ejb is simply injected as a service component (and could come from anywhere). Another option could be to use Mule’s ejb transport, however it requires ejb2-style interfaces exposed (again, this is the optional compatibility layer in ejb3 spec).

Cheers!

]]> By: Andrew Perepelytsya http://www.redstream.nl/2009/04/01/calling-ejb3-with-mule-and-test-it-with-openejb/comment-page-1/#comment-733 Andrew Perepelytsya Wed, 01 Apr 2009 13:12:09 +0000 http://www.pascalalma.net/?p=703#comment-733 Hi Pascal, Nice entry, thanks for this post. I've noticed some discrepancies though: 1. Mule has been targeted for Java 5 for several releases now, not 1.4. 2. I'm not sure what you mean by 'ejb3 is not OOTB functionality'. There's nothing Mule can do here, ejb3 don't make remote interfaces mandatory, it's up to a user to provide and expose those if needed. 3. We deliberately didn't duplicate lookup functionality already available and working fine in Spring. In this blog an ejb is simply injected as a service component (and could come from anywhere). Another option could be to use Mule's ejb transport, however it requires ejb2-style interfaces exposed (again, this is the optional compatibility layer in ejb3 spec). Cheers! Hi Pascal,

Nice entry, thanks for this post. I’ve noticed some discrepancies though:

1. Mule has been targeted for Java 5 for several releases now, not 1.4.
2. I’m not sure what you mean by ‘ejb3 is not OOTB functionality’. There’s nothing Mule can do here, ejb3 don’t make remote interfaces mandatory, it’s up to a user to provide and expose those if needed.
3. We deliberately didn’t duplicate lookup functionality already available and working fine in Spring.

In this blog an ejb is simply injected as a service component (and could come from anywhere). Another option could be to use Mule’s ejb transport, however it requires ejb2-style interfaces exposed (again, this is the optional compatibility layer in ejb3 spec).

Cheers!

]]>