[JBoss Portal] - Re: Feedback wanted. Would you choose JB Portal again?
by chris.laprunï¼ jboss.com
"wheezer" wrote :
| Liferay gets a lot of attention, mainly because of these available portlets, and it's what attracted us to it. From just a few weeks of experience in their forums, I can comfortably claim that this is what has motivated hundreds of other users, as well. My sense, however, is that JBoss Portal is a better architecture for our longer term goals, so I am eager to know much more about it. Presumably, the portlets we develop there will be reasonably portable.
|
Your points are valid. Then again, if you like Liferay's portlets (and presuming that they are JSR 168 compliant), what is preventing you from using these portlets in JBoss Portal?
Another aspect is, with JBoss Portal 2.6, we are starting to integrate with non-JEE portals. You can for example very easily use Google widgets with a Portal page with support for other (NetVibes comes to mind) probably coming up...
Also, I often see this argument where people want to benefit from an open source community of portlets to modify and use in their projects. How is it though that these people rarely contribute their portlets back to the community? Hint: useful, reusable portlets take time and attention to develop. Most people write a custom solution and don't care about making it reusable. From my perspective, and that's only mine, the return on investment on open-source portlets is very low. First, it's not clear what portlets the community wants. Second, we would probably spend a significant amount of time developing them but they would probably not fit all users needs and the more generic we make them (to try to make them easier to reuse), the more time we would have to spend on them, also running the risk of making them more complex. What do we have to gain from doing this? Increased visibility in the community (which is great) and market share. But how much of this would translate to paying customers? Would it be enough to justify the time we spent on them as opposed to working on the core product (which IS making us money)? Hard questions to answer...
A community doesn't build itself. It's a two way street... We provide an open repository http://labs.jboss.com/portletswap/ for portlets... It is not as great as it could be, and we are aware of that, but like most things, this takes time and, from my point of view, with seemingly low interest from the community, I'd currently rather spend that time on improving the Portal server.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099592#4099592
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099592
18Â years, 6Â months
[JBoss Portal] - Re: Feedback wanted. Would you choose JB Portal again?
by wheezer
Chris,
I complete respect what you're saying about the far more important design, stability and usability of the portal, independent of the portlets. Let me clarify my post and perspective a bit. I suppose my post was geared more toward a view of the portal as a ready-to-run production environment for a large (social) web site. As more of a portal user than a core developer, I am very interested in the existing applications that a good portlet catalog could provide (from any author or vendor).
In most reviews and remarks about many portals, and the promotional materials of some of the portal sites themselves, the issue of off-the-shelf portlet quantity and quality receives far more than a trivial mention. Like us, not everyone choosing an enterprise portal is a large enterprise, able to just crank out the code for a custom portlet to meet their needs. More often, they want to modify something that comes close to their requirements, and go from there.
The jsr168 approach provides a huge step up from the wild, wild, west that is the open source portal world outside the JavaEE sphere. But the advantage of some of those products is a wide array of third party plug ins that can jump start many kinds of projects. I don't think it's a stretch to wonder if such a community of portlets could be fostered in the JavaEE world too.
Liferay gets a lot of attention, mainly because of these available portlets, and it's what attracted us to it. From just a few weeks of experience in their forums, I can comfortably claim that this is what has motivated hundreds of other users, as well. My sense, however, is that JBoss Portal is a better architecture for our longer term goals, so I am eager to know much more about it. Presumably, the portlets we develop there will be reasonably portable.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099585#4099585
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099585
18Â years, 6Â months
[JBoss Seam] - Re: To Gavin.King--how to start a conversation from pages.xm
by ybxiang.wolf
"modoc" wrote :
|
| I suspect if you copy a non-unicode xhtml file from the english OS, the chinese OS will attempt to parse it perhaps using unicode, which would create a ton of garbage sequences. Or perhaps it's something else. However I suspect that OS language difference is the culprit.
| ~~~~~Perfect explanation!!! Thanks!!!!
|
|
| Even if it were dom4j, that's not a Seam bug.
|
| As a side note, just on forum etiquette, as Jason said, posting 6 times in 40 minutes isn't a good idea.
| ~~~~~I am really sorry for that and i'll change the bad matter.
|
|
| also, try to keep your punctuation to a reasonable level.
| ~~~~~Ok, I will try my best to learn english better and make things clearer. I wish i were an american, but i am a pity chinese. We common chinese have no chance to practice english. Please forgive us.
|
| Tripling everything and using exclamation points everywhere make it sound like you're shouting non-stop.
| ~~~~~You are right. I should ask questions with good manner.
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099580#4099580
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099580
18Â years, 6Â months