The J2EE spec requires different sessions for different WAR files , even if the
sesison id is the same. That's why you see what you see.
However: JBossPortal has a configuration option where all portlet WARs can be
configured to use the Portal's session (I don't remember where it is though ;)
You could simply make it a 'hardcoded' reference in the layout's jsp
Otherwise you'll need to add it the each theme that you are using (it's one
line in the theme descriptor for each theme that you'd have to add)
View the original post :
I assume you mean you added the selectors to the css, and now you want the
portal to render markup that contains the classes/ids to activate the
selectors, right?
If that's the case. look at the layout's jsp(s) (depending on what layout you
are using), and the renderSet classes (most likely
There is no check during deployment if the URL you provided in the descriptor
actually points to a valid JSP/Servlet. Check that the jsp is actually
available via a request dispatcher under the provided URL...
there should also be information in the log about how far the invocation gets
(i.e.
By default the transaction is suspended before the call to the portlet
container. You need to flag your portlet to require a transaction in the portal
object descriptor. There are examples for that in the standard descriptor
examples.
After flagging your portlet there, you should be able to
Perhaps you could get what you wnat by using several strategies?
The strategy has no access to config info, that is correct. But you could
configure different strategies for different layouts, or pages. Not perfect,
but perhaps enough?
View the original post :
Where is your configuration, and what does it look like?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3979729#3979729
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3979729
___
generate the client stubs, and use them in the portlet. There is no difference
in calling the WS from a portlet to any other client. Look at the examples that
come with your SOAP engine (AXIS, JBoss-WS, )
WSRP is something completely different. It used WS as a transport protocol, but
a) are you authenticated at the time?
b) is this code in the processAction() or doView(), doEdit(), ...
You need to be authenticated, and changing prefs can only be done in
processAction()
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3979108#3979108
preferences are stored in the database.
I haven't looked at that part of the code, but knowing Julien, the preference
store is probably pluggable ;)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3979165#3979165
Reply to the post :
Currently it is not possible to get what you want via the descriptor.
Look at
| org.jboss.portal.theme.deployment.jboss.PortalThemeMetaDataFactory
|
That's where the descriptor gets unmarshalled. As you can see there, everything
but script and link tags will be ignored.
Not sure if you
It's more or less random.
What happens behind the scenes is that WindowContext implements Comparable, and
the compare method only considers the order to calculate the return value
| package org.jboss.portal.theme.page;
| public final class WindowContext implements Comparable, Serializable
lok at the LayoutStrategy. You can write your own strategy to get what you are
describing here.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3978548#3978548
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3978548
set the caching time to infinit (-1). That way the content should be cached
after the first render until the portlet receives a render or action request
that is directly targeted at the instance (in theory at least ;)
View the original post :
you don't have to modify portal src!
The correct way to appoach this is the layout strategy. Take a look at the
MaximizingStrategy as an example. In the strategy you get all the portal
objects and their navigational state and you have the ability to change their
state or position on the page,
nope, it's not there
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3977894#3977894
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3977894
___
jboss-user mailing list
Look at portlet properties and preferences.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3978002#3978002
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3978002
___
jboss-user
In your case the code is ignored because the xml descriptor is parsed in a
standard way (i.e. ignoring comments).
BUT: You can do it via code. In the portlet's doView() etc. you can inject any
HTML you want. Look for the ContentRewritePortlet in the portlet examples (in
core).
|
are you pointing at the JSF itself, or at the JSF via the JSF controller?
You might have a chance if you point to it via the controller, but I'm not
sure
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3976967#3976967
Reply to the post :
sorry to be such a pain, but it still doesn't work, even after removing the
thirdparty directory and starting from scratch. Any other ideas: JDK, env vars,
...?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3976989#3976989
Reply to the post :
forgot the error message:
| ==
| ==
| == Executing 'most' in module 'test'...
| ==
| ==
|
| configure:
| Overriding previous definition of reference to apache.ant.classpath
|
| _default:compile-classes:
|
thanks Thomas!
I guess that's what I get for blindly following the instructions under
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossPortalFromScratch
it works now ;) ... almost.
Now I get
| configure:
| Overriding previous definition of reference to apache.ant.classpath
|
|
+1
checcking out trunc from : http://anonsvn.jboss.org/repos/portal
| C:\work\jboss\jboss-portal-2.6\buildls
| build-thirdparty.xml build.bat build.sh build.xml distrib.xml etc ide
licences misc
|
| C:\work\jboss\jboss-portal-2.6\buildant
| Buildfile: build.xml
|
|
this is described in the doc, but perhaps not easy to find ;)
You can do what you are looking for. It is controlled via the layout strategy
for one, and then via the layout itself. The layout can describe individual
layout JSPs (or Servlets) for each 'state'. The state is set by the layout
It should be possible to write a jsp expression using the request attribute
PAGE (LayoutConstants.ATTR_PAGE), which is of type
org.jboss.portal.theme.page.PageResult . Use the getPageName() method on the
PageResult. That should give you the name of the page as is was specified in
the
25 matches
Mail list logo
