Next steps for JRun and where it fits in the product calendar continue to be under discussion at the Product Manager level and such evaluation will be communicated to customers as soon as it becomes available.
I've felt for a few years now that JRun should have been end-of-life'd (is that even English?) as a standalone product. Frankly, it never has been terribly well supported (community-wise), and there was even one time where I called in a web connector bug and the engineer who literally wrote the code didn't understand what her code was doing!
I don't think it should be adandoned entirely though. Rather, I feel that any fixes and/or enhancements should be in the context of making complementary server products such as Adobe ColdFusion MX, Adobe LiveCycle, and Adobe Flex Data Services operate better.
If this is the end of the road for JRun, so long, and thanks. It's been a good (and sometimes frustrating) experience!
If JEE features are needed, there's always Geronimo, Glassfish, or JBoss.
I do hope that the talent on the JRun teams gets brought over to the ColdFusion/LiveCyle/FDS teams though.
one can dream :)
> framework-based CF8?
> one can dream :)
Yeah, and one can also have nightmares, too. With all respects to Bluedragon, I REALLY don't want to see a .NET-based Coldfusion.
For one thing, that either means that they have to manage two implementations of the Coldfusion engine (and so much of how it currently runs is based on Java that they would have to literally rewrite it from the ground up) or give up on being truly multi-platform.
All existing CF applications that in any way made calls to Java would have to be refactored.
I know some people really, really, really love Microsoft so much, but for the rest of us, why mess with a platform combo (CF on Java) that works so well?
Signs point to Macromedia dropping JRun from product line
http://www.newsforge.com/business/03/08/06/1413257...
If Jrun will be discontinued, what will happen to CF enginee? It will continue to be shiped with the regular JRun version (even in the Standard edition) and this version will continue to be improved? I don't think so. What about 64bit support and J2EE 1.4 (jrun is a J2EE 1.3 compliance)? If Adobe retires JRun, CF will be ported to a different java container (I don't think Adobe will kill CF). Will be TomCat? Will be JBoss? Will be an open or proprietary product? Nobody knows, but those on the Scorpio beta program has a clue.
Server Error
The server encountered an internal error and was unable to complete your request.
Could not connect to JRun Server.
Hmmmm.
Damon
I'm truely waiting for the next release of JRun and I hope it will be supported for many years to come!
http://www.onjava.com/pub/a/onjava/2005/09/21/onja...
""
...JRun has fallen to three percent, so there seems to be more standardization on the major players.
""
I just don't see Adobe providing any value with JRun in what's quickly becoming a commoditized market. I think their best bet is to certify all of their software on JBoss/Tomcat and put JRun on the path towards EOL. I suspect that one of the reasons CF has had a hard time winning over Java developers is that there still isn't a supported open-source deployment option. Most Java teams scoff at JRun and are left only with high-priced containers from BEA, IBM or Oracle as the remaining deployment options. FDS and Livecycle both run on JBoss so I think we'll see them move CF in that direction eventually.
I'd like to see how many of those customers bought JRun post 2004 or so.
He's dead, Jim.