I tried trunk, setting the expiration cache works correctly.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017739#4017739
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017739
__
No it is fixed in the code already.
There is even a test case to make sure it works.
I'm also trying it again, but i feel like i am loosing my time.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017722#4017722
Reply to the post :
http://www.jboss.com/index.
The way to resolve it, is to download and change the source code.
Is there any other way to resolve the problem ?
Is there a simple way to make two portlet communicate ?
Regards
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017713#4017713
Reply to the post
It's marked as resolved.
Are you sure it doesn't work ?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017711#4017711
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017711
__
It's not what I want to do.
Have you look to the tutorial page I try to folow ?
http://www.doc.ic.ac.uk/~mo197/portlets/portlet_messaging/
The portlet 1 put a String in an APPLICATION_SCOPE named b_var.
Then, the porlet 2 read it and show it.
But, because I can set the expiration-cache to 0, the
It is in the JRA, I think.
I found this forum thanks to a link in this jra page :
http://jira.jboss.com/jira/browse/JBPORTAL-1104;jsessionid=BD4B2865E2711BAD3A9442763E0DB0D7?page=com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel
The reason I came to this forum is that I've don't
"bmcgovern" wrote : I agree. I've tried setting the expiration-cache value to
0 explicitly in portlet.xml and programatically in doView, each time it doesnt
set.
|
| I'm stuck on this cause i need a work around for my situation..
|
| first time a form submits - processAction is called
"mylas" wrote : Why the JBoss' team haven't fix this problem in the 2.6alpha
version ?
Because ASAIK it is not in Jira. It's hard to keep everything if nobody even
dare to file a bug report.
I'm looking at it.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4
Where is the "fragment cache info" that your are talking about ?
Why the JBoss' team haven't fix this problem in the 2.6alpha version ?
|// Update the fragment cache info only if the value has not been
|// overridden during render processing
|
|if (
fragmentResult.getPrope
Please open a JIRA issue
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984084#3984084
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984084
___
jboss-user mailing list
jboss-
Just to clarify...the 168 spec only says that you should be able to do the
following:
public void doView(RenderRequest request, RenderResponse response) throws
PortletException, IOException, UnavailableException
| {
| ...
| response.setProperty( RenderResponse.EXPIRATION_CACHE, "
Can you supply more code, specifically what your importing. It looks like
fragmentCache is specific to jboss and that may work but i was hoping for a non
platform specific fix. I was hoping it was something in the 168 spec that i
was messing up? Does anyone have any idea?
View the original
I think the code snippet I posted above will fix this bug. Did you try it or
are you saying that it doesn't fix it for your particular situation?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979696#3979696
Reply to the post :
http://www.jboss.com/index.ht
I agree. I've tried setting the expiration-cache value to 0 explicitly in
portlet.xml and programatically in doView, each time it doesnt set.
I'm stuck on this cause i need a work around for my situation..
first time a form submits - processAction is called then doView. doView checks
for exis
Yes, as a matter of fact I got back to this issue a few days ago and hadn?t got
around to posting my findings.
Unless I am missing something, it doesn?t appear that this was implemented
anywhere (as of the 2.4 final release). I believe the problem is on line 65 of
org.jboss.portal.portlet.as
Were you able to figure this out? Im having the same problem.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979428#3979428
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979428
_
16 matches
Mail list logo