please search this forum. it's been answered many times
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3938462#3938462
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3938462
the samples contain an AJAX portlet that you can take a look at.
There are some steps in th 2.4 code base to get things like a region or a
single portlet window to be rendered via AJAX requests, but its from complete.
View the original post :
it won't get you all the way. The render set only takes over at the region
level, the layout still renders the the HTML and body tag, etc.
If you look at the 2.4 code base there are MarkupCommands for Page, Region and
Window (Region and Window are untested at this point). Those commands are
what I am describing would use the same servlet as the full page render
process. It's a dfferent path in the core invocation stack, effectively
choosing another render command based on the URL that caused the request, but
that's it, the rest of the invocation would be the same (i.e. same
as long as your roles are fixed for the time span of the session of a user, you
can handle it all in the login module. You still might decide that it is best
to encapsulate your specific data base access into a custom user and/or role
module though. It simply depends on your requirements.
But
your app is accessed via the portal context. Security is checked there. The
portal uses a RequestDispatcher to dispatch to your app.
You need to place security constraints into the portal descriptor defining your
portal resources. (see examples in the default-object.xml in the core)
View the
not yet (as of 2.2) on a per user basis. This feature is referred to as
'dashboard' in this project.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3938271#3938271
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3938271
it is taken from a constant in the generic layout's index.jsp
to change that modify the index.jsp (and maximized.jsp) in
core/src/bin/portal-core-war/layouts/generic) , adn replace the constant with
what you want (JSTL ? )
| head
|title%= PortalConstants.VERSION.toString() %/title
no, no , no !
You are confusing concepts here.
What you should do is define a page with only the navigation portlet and the
CMS portlet on it. That page will then appear in the 'natural' navigation menu,
and when you select it, only the nav and the CMS portlets will show.
There is no need to
I'm not sure if this is a forum problem, or if you forgot the quotes around all
the attribute values that you write.
instead of:
| writer.write(FORM ACTION=);
| writer.write(renderResponse.createActionURL().toString());
| writer.write();
|
try
|
and what's wrong with using the Subject ?
Why do it any other way then the default login modules handle this case?
they create Groups and Principals and populate the Subject with them.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3935219#3935219
Reply to
| Subject currentSubject =
(Subject)PolicyContext.getContext(javax.security.auth.Subject.container);
|
but note that this call is subject to security manager access checks.
Not sure if there is any better way
View the original post :
sorry, I still don't get it. Are you saying that you create that URL yourself?
Or are you using a portal API to get it?
You want the portlet in the center area to be maximized, whenever you choose
one in the navigation?
Please try to be a bit clearer about the separation of page and portlet
you can solve this with either
* window properties, or
* portlet preferences
All it requires you to do is define a new window for each portlet assignment on
each page (i.e. for the same portlet on 3 pages, you'll need 3 windows so that
you can assign different preferences/window properties).
if you need a redirect, you should do it in any of your portlets. The layout
jsp is rendered at the very end of the rendering cycle, so it would be very
unwise to do all the work and then at the very last moment throw it all away.
What is your use case? Why do you need a redirect from the
you need to do that not in the render set, but in the theme.
The empty renderer doesn't create any markup other than what the portlet and
the layout produce. If you want to set the title color, font, etc. you'll need
to use the theme to do that.
So,
- use the divRenderer render set
- take
is your form using POST or GET ?
try form method='POST' action='
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3934464#3934464
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3934464
have you tried to log in as admin (pwd:admin)?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3934501#3934501
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3934501
---
the admin and user users are being created when you start your portal for the
first time. I'd drop your portal database and restart the portal. You should
either see some errors during startup , or get the admin and user users.
View the original post :
the security module is in a state of change. The links will be secured again
(i.e. not showing). The current behaviour is a bug in the 2.4 branch.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3934068#3934068
Reply to the post :
we are working on a feature called dashboard that will allow users to create
their own pages. You can of course place a CM portlet on any of those pages.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3933512#3933512
Reply to the post :
both are defined as part of the window definition in a page.
So look at the object descriptor (xyz-object.xml), or do it dynamically via the
management UI (once you log in as admin)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3932885#3932885
Reply to the
can you give us the errors you are referring to ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3932887#3932887
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3932887
I'm not sure what exactly you want here. Is it the data from the portlet.xml ?
The WindowResult class should give you all the portlet info you need. The
RenderContext and WindowContext allow you to get to the layout/theme specific
information.
If all of that doesn't suffice, you can always
would read-only access to the portlet preferences solve the issue for you ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3932892#3932892
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3932892
the way to solve this is the write your own navigation portlet , and use that
instead of the default one . You need some sort of paging
There are several threads in this forum about this, so you might be lucky and
someone has already written the code you need (Ihaven't seen any commits
the easiest way (I believe) is to use the declarative injection of header
content. In this case you can declare the js file to be included as link in the
head tag, by adding this to your jboss-portlet.xml descriptor :
|portlet
| portlet-nameMyAJAXPortlet/portlet-name
|
This thread is getting confusing for me:
You should be perfectly fine packaging your portlet(s) in a separate WAR and
deploying that to the appserver that hosts the portal. As long as all your
resources that the portlet uses are in the same context (WAR) you should be
fine; there are no class
agreed that the current implemetation is simplistic.
BUT: stay away from xsl
It's nice on the surface, but it is a HUUGE performance bottle neck , even
if you cache the templates / transformer (watch for thread safety!!)
and speaking of : at least xalan is not thread safe ! So
keletappi wrote :
| In jetspeed2 this is solved by adding initial language resources of page
names in psml files (one psml file defines one page in jetspeed2). Also
ordering of pages is in psml file. This makes it fast and easy to add language
resources. In jetspeed2 they also lack ability
arvind_pv wrote : Hi Everyone,
| I need to access HttpSession in Portlet class and also I need to access the
PortletSession in Struts Action class
|
access to the HttpSession is easy: use application scope , i.e :
portletRequest.getSession().getAttribute(blah,
What image are you referring to exactly ?
You most definitely don't have to create a new theme. You can always replace
the image in the current theme, or overlay the image via an inlined css
element, etc.
Once I understand better what image you try to replace, I'll be able to give
you more
keletappi wrote :
| BTW. I have just playing with this portal implementation for 3 days now.
After using jetspeed2 and other portals this system feels nice and flexible.
Much easier to deploy portal and edit layouts and themes.
|
Nice to see someone appreciates this ;)
keletappi wrote
to overwrite the styles for a portlet, you can use the css injection
there is a programmatic way, and a declarative way to inject a css. The
injected css overwrites the theme css in the scop of the portlet that injects
it. See the theme doc for details on how to do this.
Another option you
Since I came up with the render set, and wrote the doc , I'd like to know what
the confusing parts are. Could you please elaborate so that we can make it
better .
Thx !
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3923706#3923706
Reply to the post :
I don't know web models, but it sounds like writing a portlet bridge (or better
finding one that already exists) would be your best bet. That would allow you
to consume your app unchanged, similar to a JSF or struts app that works with
the appropriate portlet bridge.
View the original post :
do you see any errors or warnings on server startup ?
my guess would be that the stack trace you see is a result of something more
profound going wrong earlier (like no connection to the database, etc. )
View the original post :
see http://jira.jboss.com/jira/browse/JBPORTAL-578
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3922595#3922595
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3922595
PMO wrote :
| The layoutstrategy operates at the html page level, correct?
|
-- yes
PMO wrote :
| so, if write my own strategy it becomes possible to propagate a parameter
to every portlet by using the setAttribute() method of the PortletContext
correct?
|
-- no. the portlet
almost right ;)
Please don't confuse the Layout with the Theme. They are two very different
things.
The Layout is the one that lays out the general page and determines the
portlets, and the regions they are in.
The theme styles the rendered content using css.
Layouts are described in
as long as all your wars are deployed on the same server, you can use the
portlets in the same portal. In your *-object.xml descriptor you just need to
point the instance to the correct context and portlet name. No need to do WSRP
Here is a simple test: package a standard 168 portlet in a war
You're missing the action that is allowed. Add an action-name element like:
| security-constraint
| policy-permission
|role-nameAuthenticated/role-name
|action-nameview/action-name
| /policy-permission
|
see http://jira.jboss.com/jira/browse/JBPORTAL-467
please vote for it ;)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3919639#3919639
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3919639
I really like this question. It made me realize that we're missing this in the
layout strategy. That's where I beliefe this should be available. Currently,
however, there is no way that I can see that would allow you to access the
window/page/portal properties from the StrategyContext
We
you are correct. This seems to be a regression. The
StrategyContext.getTargetPortlet() method should give you the PortletContext
for any portlet that is directly addressed by the current request via a
ctrl:window= URL parameter
Please enter a JIRA issue for this
View the original post :
ego2002 wrote :
| I've just installed 2.2 portal version and I've tried the management
portlet to create new pages...
| It looks like it works well, but where are new pages saved phisically? In
wich file? Where does JBoss load them from?
|
They are stored in the database (via Hibernate)
make sure you are adding your web.xml entries in the correct war file.
There are several wars involved here !
Note that the portal's login page is actually defined in the portal-server.war
, and not in the portal-core war !
View the original post :
noicangi wrote :
| also i'am trying to edit the maple theme (it's horrible) but how can i edit
de *.css using a html page to see what i'm doing?
|
No need to edit it if it's horrible ! You can just write your own.
I don't understand your question? What is it that you want to do ?
The
There is an excellent theme and layout guide as part of the user documentation.
Check it out.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3917892#3917892
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3917892
axh1359 wrote :
| so I get a full portlet on top of the page, I add for every page with
NavigationPortletWindows, so how do I assign default properties to
NavigationPortletWindow thanks.
|
I'm afraid there is no way to do this currently. You'll have to assign the
properties to each
you can get the lastest code from cvs HEAD
The way this currently works (images and links for modes and states) is that
the renderSet injects div tags with class attributes that are matched by the
theme. So it is the theme that determines the image and the arrangement
(lookfeel). You can
PMO wrote :
| I am deploying two virtual portals A and B.Both are using the same portlet
P (deployed in A)
|
| | Scope
| | When deploying a page, window and instance of P in portal B I can refer
to the portlet P using the scope A in the compoent-ref tag, correct?
| | |
|
to be perfectly honest , I get those confused all the time.
What I do is look at the available themes after I deployed them in the theme
selector portlet. the appID that shows up there is what you want.
(and for the record: I think it's the context root, or the war file name (minus
the .war)
I just looked at the code. It's not available.
I created http://jira.jboss.com/jira/browse/JBPORTAL-555 for this
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3916691#3916691
Reply to the post :
You can secure the portal, or an instance of it, or a window of an instance of
it, via roles. You can do that either via a security-constraint element in the
jboss-portlet.xml , or in the *-object.xml, or you can use the management UI to
do the same after the portlet is deployed.
View the
no need to change the interceptor. The interceptor is the one that detects that
there was no strategy set. The strategy is set via a portal property, like:
| deployments
|deployment
| parent-ref/
| if-existskeep/if-exists
| portal
|
'old style' layouts still work in 2.2 (see the phalanx theme for example)
Do you get any kind of error , warning, etc. ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3916425#3916425
Reply to the post :
please enter a JIRA issue for this
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3916426#3916426
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3916426
---
This SF.net
again: it's the renderSet that does that (inject the html that ultimately
displays the images for the modes and states , in combination with the theme
css). So do what I showed in the previous post and you get your tool tips.
I actually changed the cvs HEAD to have that OTB now.
View the
PMO wrote :
| By the way, I understand that it is possible to not specify any parent ref
for an object. The object is then not a part of the tree and therefore sort of
hidden from the admin tree. Correct?
|
Not sure, I haven't tried that, but it sounds plausible.
PMO wrote :
| There
Are your filter and your portlet deployed in the same WAR context ?
Rembember: each context has its own distinct session!
There is a config option to share the portal's session across all contexts
though. Check the docs for how to activate that.
View the original post :
you'll havwe to get the code from CVS:
| cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/jboss co jboss-portal-2.2
|
the strategy is in the theme module :
jboss-portal-2.2/theme/src/main/org/jboss/portal/theme/impl/strategy/MaximizingStrategyImpl.java)
View the original post :
The title attribute can be added to the render set. The markup that spans the
portlet decoration is generated by the renderSet. In the default OTB case of
the portal, this is a class called
/theme/src/main/org/jboss/portal/theme/impl/render/DivDecorationRenderer
you can change the code, or
the decoration is done in the renderSet. There is no interceptor stack for
this. The LayoutStrategyInterceptor handles the layout strategy (as the name
implies :) ;
The strategy is something you might be able to use for the other feature you
are mentioning here: it is called when the portal,
please be careful with the term you are using. I'm still confused by your use
of 'portlet', but anyway: I hope I got it now.
You can have a layout for the entire portal, but you can overwrite it for
individual pages via page properties. You can define a jsp that does your
layout with top,
vmarco wrote :
| Doesn't this prevent me from controlling the title per page? Doesn't it
also means to control the title of my site I am now required to create my own
layout? I must be missing something here. I should have the ability to
specify both a site-wide title or per page title in
jency wrote :
| Do you mean we cannot change the name default for the default page(tab)?
|
At the moment (2.2), yes, that's what I'm saying. Not without coding.
jency wrote :
| The title for portlets can be changed via portlet.xml; but the default
page contains a portlet whose title is
does your maximized.jsp select for the maximized region ?
| p:region regionName='maximized' regionID='regionMaximized'/
|
Via
| property
|namelayout.strategyId/name
|valuemaximizedRegion/value
| /property
|
you are using the maximized region
All PortalObjects make up the 'portal tree'
These are the portals, pages, and portlet windows that are defined in your
portal runtime.
A page is a child of a portal, a window is a child of a page. Pages can have
children pages. To express where you want a page to be placed in that tree (as
a
the behaviour of the maximizing strategy is that once a portlet is maximized,
it will ommit the render process for all other portlets. It assumes that at the
end of the render process all you want to display is the one maximized portlet,
so it saves the portlet container the effort to render
jency wrote :
| The title for portlets can be changed via portlet.xml; but the default
page contains a portlet whose title is JBoss portal and I could not find any
reference to it portlet.xml. Which files should I modify to change this?
|
This portlet is the CMSPortlet. It sets the title
did you try http://localhost:8080/portal/carris/Registration ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3915290#3915290
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3915290
The title that is shown in the browser is set by the layout.
In the portal core war look for layouts/generic/index.jsp , and there for the
title tag.
The title of each portlet is set in the portlet.xml descriptor
Look for the portlets you want to change the title for (their title) and change
not sure, but I think your definition of layout is probably different from
mine, so I don't know if what I can tell you makes sense to you.
Let's try anyway:
The layout is the jsp that renders the returned markup (the entire page). So it
is the part that creates the HTML, TITLE, BODY ,
the content type interceptor determines the content type that the browser
requested / can handle. The portal takes this content type as the allowed
content type for the current request. Portlets that want to set a particular
content type need to first check if the current request supports that
there are at least two ways to get this result:
1) create a new layout that places this special portlet whereever you want,
using the theme's portlet tag
2) add a special layout region to your layout that will host this special
portlet. Each page then has to have a window definition for this
where did you get the idea of using the nodecoration property ?
This shouldn't be in the docs nore in the samples. If it is, please accept my
appologies.
The correct way to do this is by using the window properties, but instead of
setting the nodecoration prop, you can now specify the
Thanks ! You spare me from having to write this ;)
I started the tabbed nav very late in the 2.2 cycle so it didn't get very far.
Some things I'd like to see in it are:
* limit the amound of visible tabs ; add a paging mechanism for too many tabs
to display
* a bread crumb would be nice
the only thing I can think of right now is to intrduce a component invocation
interceptor that does what you are interested in.
PortletFilter are one possible new feature for the future Portlet 2.0 spec.
View the original post :
ooops, sorry. that should not have made it into the final doc.
It's corrected in cvs. Sorry for that!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3915368#3915368
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3915368
ahem, I guess in theory it should ;)
You are right. It is hard coded for now. I wasn't aware of that.
Time for some community contributions :)
Since we're on this topic, does anyone have experince with CC/PP?
How would that fit into this discussion.
My current thinking is that this , or a
To my knowledge the 'default' is hard coded in 2.2. I don't know any way around
it without coding. So I guess you did what was necessary.
see also http://jira.jboss.com/jira/browse/JBPORTAL-465
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3915392#3915392
correct : the layout is one part of that. There are several pieces that work
together here. The page definition assigns portlets to regions. The layout
strategy can move portlets temporarily (for the timespan of the current
request) to any other region, and the layout is the one that takes the
there are two new layouts in 2.2: phalanx and generic
phanlanx uses the same constructs as you saw them in 2.0.
generic uses the new default approach, where the theme takes over a lot more
of the look and feel of the portal. The portal now comes with four default
themes that all work with the
what you see there are (currently) pages, not portlets.
But the good news is: yes, you can do that.
You will have to create those pages, place the desired portlets on them, and
then secure them via a security constraint that allows the mentioned roles
read access to the individual page. As a
you can also introduce a hierarchie in your pages. Only the root level pages
are displayed in the tabbed navigation, so you could organize your pages in a
much smaller set of top level pages (that will be displayed as tabs) , and
children pages of those.
View the original post :
pages can feature portlets from any portlet app (WAR) deployed to the portal.
when you add a portlet window to a page, make sure that the instance it points
to references the portlet in the desired context, like:
|deployment
| if-existskeep/if-exists
| instance
|
you are using portal 2.2, right ?
there is a new descriptor that replaces the old 2.0 style ones.
*-object.xml combines the -pages, -portal , and -instance descriptors.
If you are on 2.0 , then you're right: you need to restart to get the changes
to be recognized. A touch of the web.xml of
good idea.
I think we should keep in synch with the portlet spec and use the xml:lang
attribute to separate the display-name for different languages, like:
|page
| page-nameHello World/page-name
| display-name xml:lang=enHello/display-name
|
Look at the Test page . It contains a sample page (Event test) with two
portlets that communicate (one portlet telling the other what color to use to
display text )
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3912999#3912999
Reply to the post :
hmm, works for me. What exactly are you doing ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3913003#3913003
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3913003
---
not sure about the struts bridge, but the portal allows you to deploy separate
wars containing portlet artifacts. You can do that with portlets, page,
portals, themes, layouts, etc.
All that should be required is the appropriate descriptor bundled into the war
you deploy. So for example, if
I think I understand what your requirement is, but we'll see ;)
What JBossPortal offers you is role based access control for portlets, portlet
instances, portlet windows, pages and portals. So each one of them or any
combination , can define security constraints that tie a role and actions to
it is possible to set the theme for the page:
in JBP 2.2 you would do that via page properties, like:
| page
| page-nameSecure Policy Config/page-name
| property
|nameorg.jboss.portal.property.theme/name
|valueNphalanx/value
anonymous wrote :
| the JBoss portal reference guide in the chapter 5 (about theme and layouts)
says that left, center and right are acceptable values for regionName.
Are there other values? If so which are?
|
Effectively, you can use any. All there is to know is that the region you
not in JBP2.0, but in JBP 2.2
Portal 2.2 offers the possibility to dynamically create security constraints
for portal objects like portals, pages, and winodows. Note, however, that the
API and meaning of portlet security has changed in 2.2
View the original post :
Layouts and Themes are (currently) being deployed as part of a war file (which
can optionally be contained in an ear).
I said currently because we are looking into getting themes to be deployable
via Content Management for JBP 2.4.
A layout consists of one or more JSP or Servlets , and a
sent on it's way
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3909546#3909546
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3909546
---
This SF.net email is sponsored
np, just tell me where to send it (I won't be back until next Monday though ...)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3908779#3908779
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3908779
I just took your layout jsp and deployed it in a separate app (war part of an
ear) and picked it as layout in my portal, and all is well.
In other words: your jsp is fine.
There must be a packaging issue. Are you packaging any of the portal jars with
your archive ? You don't have to. You
1 - 100 of 173 matches
Mail list logo
