Java EE 5: Need to process a file by calling a native (long running) application

[tnektpb]

Hi,

I have a native application which I need to call when the user presses a button in my web application.

This application will take a while to finish and I've heard it's bad to call such applications (or perhaps any native application?) directly using a Stateless SessionBean.

How do you propose that I attack this problem?

[Hack]

Well, lets start with why do you need to call it and what do you expect it to do after you have called it?

[tnektpb]

The button is pushed when the user wants to download a series of MP3 files packaged into an ISO-file. We need to package the MP3-files into an ISO archive when the user wants the files. The packaging will take ca 2 minutes.

[Hack]

The button is pushed when the user wants to download a series of MP3 files packaged into an ISO-file. We need to package the MP3-files into an ISO archive when the user wants the files. The packaging will take ca 2 minutes.

Ok, that sounds pretty straightforward. I'm curious about this statement.

I've heard it's bad to call such applications (or perhaps any native application?) directly using a Stateless SessionBean.

What is bad about it?

Finally, regardless of what you have heard, have you actually tried, and failed, to call the application directly using a Stateless SessionBean?

[tnektpb]

Thank you for your continued help. We haven't tried it yet. :-) It might not only be an issue of whether it's possible without exceptions or not. There's also the question if this is a good approach or not? Perhaps stateless session beans are supposed to execute quickly so they're available to work for other sessions?

[Hack]

Well, actually I've never had any issues with Stateless SessionBeans

[tnektpb]

We'll do a trail and error. Thanks for your input!

[Hack]

Yes, please do. If it is happening to you, then in all likelyhood it will happen to someone else so what you find out could be beneficial to a number of folks.