Hi All,
I am just review my watched topics now I am already go deep with my seam +
portal apps, but still found some problem like I post in different topic, is
there anybody here have success story with seam + jsf+ facelets + jboss portal
combination? please share your experience with me,
I am considering using Seam + JSF (MyFaces) for a future portlet project and
wanted to know if it would be possible to deploy the portlet on any JSR-168
compliant portal or only Jboss Portal? Seam 1.1 is supposed to run on any
container or AS, but in this thread no one has made mention of using
In theory it should work. But you would need to try it out for yourself. I know
that somebody got Seam working in Liferay.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3999185#3999185
Reply to the post :
Hi Gavin, nice to see your post again :)
I want to share my experience when using seam+portlet+jsf+facelets, may be I
also have post some of them in the diferent topic, but I found some new problem
yesterday.
Here is my spec :
- Seam 1.1.0 GA
- Jboss portal 2.4 GA
I have an application which
Gavin Please review this thread :)
thanx and regards,
-haric-
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3999279#3999279
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3999279
perwik wrote : I've followed the development of Seam for about a year now,
but it's only recently that I've started to build something with it. I see a
need for splitting my project into modules (call them portlets if you like).
|
| The problem with these modules is that, as far as I
Just a bit more on this discussion - mainly in response to the following:
[EMAIL PROTECTED] wrote : Portal does solve some big issues. jboss.org runs
on portal, and I couldn't imagine trying to do something with that scope by
building up all the components in Seam. There are too many moving
I personally also wouldn't use a portal system to build a plain old interactive
website (now matter how large it is). A templating solution should be able to
solve all the modularization problems within a single applicaton, from a UI
perspective.
I think that the value of a portal is mostly as
What is missing from seam applications is independent state maintenance for the
various portlets on the page. We have many applications that we want to bring
together under one site. These sites are all intranet based so the weight
isn't as much of an issue (this can be ameliorated to a
Sorry - I hope nobody took me to be promoting portal usage. Portals are a
great idea, but I don't have any significant experience with JSR 168 or JBoss
Portal to know when/where they should be used. I like the idea, but my
knowledge of them begins and ends with my conversations with the guys
On the other hand, maybe I just wasn't very clever with the way I did the
application. If someone has a suggestion for a simpler way to go about it, I'm
all ears. :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3998315#3998315
Reply to the post :
swestbom wrote : What is missing from seam applications is independent state
maintenance for the various portlets on the page. We have many applications
that we want to bring together under one site. These sites are all intranet
based so the weight isn't as much of an issue (this can be
On your last point, my standard Spring bash is Spring - a much simpler way to
write broken J2EE applications. :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3998329#3998329
Reply to the post :
Here's another slant on this topic and your statement:
anonymous wrote : hopefully that seam and portal will be a good match in the
future
I did a fair amount of work with JBoss Portal about a year and a half ago.
This last year, I've mainly worked with Seam + Facelets and JSF. I've recently
Portal does solve some big issues. jboss.org runs on portal, and I couldn't
imagine trying to do something with that scope by building up all the
components in Seam. There are too many moving pieces, developed by different
teams that need to come together. Things like that really need
I agree with Smithy. Right now it is proving to be just too difficult to work
out the right combinations of artifacts to get Seam and Portal and jBPM and
Facelets and AJAX etc working together.
Even the JBoss guys have not yet been able to do it !
I also agree with Norman, that Portal does
I wish I could help. I haven't figured out portal yet. :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3998125#3998125
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3998125
___
[EMAIL PROTECTED] wrote :
anonymous wrote :
| some time later, when a future version of Portal becomes available that
fixes our problems, we can move our Seam app towards pure portlets.
|
Is this mean that at this time, it would be a huge PAIN if I am trying to
combine
18 matches
Mail list logo
