Question of language : It is not a limitation... It is a non addressed feature.
But I agree with you, JBP lake of this sort of feature.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236257#4236257
Reply to the post :
http://www.jboss.org/index.html?module=b
I'm almost happy of my application building within JBoss portal but I encounter
a somewhat complicated problem. I want to use a ThirdParty application which
will embed the Authentication business. This Application is a sort of SSO
handler with a backoffice application where we can add User And R
Have a look to the *-object.xml file descriptor.
You can define portals, pages
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236085#4236085
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236085
___
I encounter the same restriction. My use case is that I'm building an
application composed by a few modules (each modules comes as a portlet package
in a war).
I use some page spaces in order to compose different views of my application
(base on the role or the application context (summary page
It's not the portlet packaging which dazed me, but more the portal packaging. A
bundle with portlets, themes, layout, sso, etc.
After reading Peter presentation, I think I'm able to package my application as
an EAR which will contains portlets and themes and then use scripts to update
the princ
Hi,
I'm currently trying to answer a question. Is JBP designed to fit my
requirements ?
I don't really want to use JBP as a Web Site Portal but like an Application
composed by a few Portlets.
Portlets seems to be the component I'm looking for. It permits me to create
some modular features lik
