- This topic has 7 replies, 7 voices, and was last updated 18 years, 9 months ago by
.
-
Posts
-
The driver for the choice was primarily time to market and the lack of maturity for java portals when compared to PHP. We could write or own solution, but that would be silly and would add nothing to our ability to offer improved MyEclipse features and capabilities. Not to mention loss of focus and time.
We chose an open source portal framework that offered us the most features with minimum support requirements. As we continue to grow, we will consider alternatives. If you have a Java solution (that will not break the bank) you feel very strongly about, please let us know. I’m sure our webmaster would be happy to look into it.
Best Regards
Jim K.wasn’t there a free java framework that was posted by the javalobby about 6 months or so ago that did just this?
@subscriptions wrote:
If you have a Java solution (that will not break the bank) you feel very strongly about, please let us know. I’m sure our webmaster would be happy to look into it.
since you’re currently using phpnuke, you might be interested in this..
from:http://jboss.org/developers/projects/nukes/index
NUKES ON JBOSS: OPEN SOURCE CMS
Nukes on JBoss project started when we tried to run the popular postnuke open source project for our website. PHP/Postnuke didn’t scale. After analyzing the PHP codebase we found some dubious ways of caching data and decide to port the framework to JBOSS.
Nukes on JBoss is a full fledged Content Management System (CMS) with advanced user/group management, security rules and pluggable components. Components can be deployed at runtime while the application is running. It is all written in JBoss and most importantly nukes powers jboss.org.
Excellent input. We will definitely take under advice.
A little bit of history though. We evaluated multiple java and asp solutions for the MyEclipse portal. Many of the free/OSS solutions lacked feature depth, module integration framework, broad market install and support base, and most importantly the ability to handle user classification and fine-grained security to support the MyEclipse Subscription model.
As for JBoss Nukes, We experienced the same scaling issues at first, and to be honest that gave us quite a scare. However, we quickly identified the source of the bottlenecks and expect this portal to support our growth plans well into 2004. I don’t think the JBoss team gave it the same consideration and simply gravitated into what they are familiar with.
We constantly evaluate emerging solutions in light of added benefits and conversion costs. The JBoss Nukes solution is very interesting, but we need to give it some time to see if the market will embrace it through the emergence of a secondary module offering. You see, the portal framework by itself is of limited value in absence of this emerging secondary market to keep growing and enhancing portal features. One company can not do it by itself, and it doesn’t make sense for us to rebuild feature that already exist on a different platform simply to keep our bloodline pure 🙂
Jim K.
I noticed that someone mentioned the Javalobby portal project. That would be available at http://www.jlcp.org and we’ve been making quite a few strides on its development over the past few weeks. The forums have seen a big improvement since the last released version, and the version available in CVS has come a long way. If you have questions, feel free to let me know at matt at javalobby.org.
if the shoe fits … i don’t know why you purists are getting all teary eyed.
off topic: any intentions of adding php syntax highlighting to the myeclipse offering?
