Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Asynchronous bean Websphere - is it part of J2EE already?

 
Gajen Logandan
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I need to port asynchronous bean (provided by websphere) support in App servers like weblogic and jboss.

Is this feature already part of J2EE specification?

Or should I use some other external package to get this feature?

If so what are those async bean like features for weblogic and jboss?

Thanks.
 
Jaikiran Pai
Marshal
Pie
Posts: 10447
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't know what asynchronous bean in WebSphere looks like, but starting Java EE 6 (which is supported by all major vendors) Asynchronous EJB methods are supported by the spec. See this for details http://docs.oracle.com/javaee/6/tutorial/doc/gkkqg.html
 
Gajen Logandan
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What actually are the difference between Asynchronous EJB methods and Work manager (async bean from web sphere)?

They both seem to be doing the same thing, but if some one has any experience in using both, please let me know the difference.

Thanks
 
Claude Moore
Ranch Hand
Posts: 793
7
IBM DB2 Java Netbeans IDE
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As far as I know, WorkManagers were introduced just to allow developers to execute tasks asynchronously, when asynchronous methods invocation wasn't still available (of course, it depends on which version of WAS you 're using).

WAS 8.5.x supports JEE 6.0, so you have full, Async EJB method invocation support: I think that under the hood a WorkManager is still used by EJB container to support async invocations, but you may want to define and configurate a WorkManager instance and tell the EJB container to use that as default instance for async EJB method calls.

In my humble opionion, I would prefer to use standars instead of product specific extensions.
 
Marcel Friedmann
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Implementing asynchronous stuff with the WorkManager is quite exhausting. For heavy workloads you need a sophisticated websphere configuration - the standard does not work so well for that.
The programming model is also not neat.
Since Java EE 6 you can simply add an @Asynchronous Annotation to mark an method as async. Thats a lot easier to handle. You can also combine this quite easily with Java Futures.
However you may have to break down your WorkManager-code for that.

This blog post explains briefly how to use asynchronous methods in WebSphere
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic