Thanks for your response. Sorry I haven't been able to get back to you sooner.
"Putting it in the request scope" equals using request parameters throughout the page, right? Is there an easy way to do this, ie does s:link for example have an option to forward existing page parameters automatically, or do I have to add param-tags to all the links?
Also, for links that should be clickable both when this variable is set, and when it's not .. how do I solve this?
I tried putting it all in a conversation instead, but then the problem of the variable not being updated remained.
/Sebastian
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069035#4069035
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069035
"anders3" wrote : Then the portal told me that MyFacesGenericPortlet did'nt exist any longer.
| ...
| The problem seems to be that the jboss-container has switched from myfaces to Sun RI.
|
Yes.
"anders3" wrote : One solution is to backport this change... Nice wiki (http://wiki.jboss.org/wiki/Wiki.jsp?page=Running2.6WithJBossAS4.2.xAndMyF...)
| But NO NO NO NO.. what if another of my portlet suppliers uses Sun RI
| I am i chock that the page can exist. But anybody can write in the WIKI.. This cannot be a suggestion from the portal team?
|
We need to update the wiki. The instructions were needed for people who wanted to use MyFaces instead of JSF RI at the AS level and still make sure it worked with Portal. Prior to 2.6.1.GA there was an issue with our JSF "meta" bridge so that was required. As of 2.6.1.GA, there shouldn't be anymore issues with bundling a JSF implementation with your portlets (e.g. MyFaces if you wish to use it instead of the Sun RI).
In essence, the wiki is confusing as of 2.6.1.GA. There shouldn't be an issue with JSF anymore but if you do find one, please let us know.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069034#4069034
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069034
You're almost there (assuming that the button refreshes the table correctly). In your a:support tag change it to:
<a:support event="onkeyup" action="#{staffCourseList.find}" reRender="dataTableStaffCourseList"/>
This will update the value of classTitle in your Bean with each keystroke. Assuming that your dataTable is populated with a query that uses this parameter, then it will work fine.
Cheers,
Damian.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069033#4069033
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069033
Hi,
I got working app on JBoss 4.0.5 using Seam scheduler (also working fine). Now I try to run my app on tomcat 5.5. Everythink I think so far works, but when I try to start my scheduler i get null pointer exception on processor.
Do I need to do some anythink special to run my scheduler on tomcat?
here is my source code:
| @In(create=true)
| EngineProcessor processor;
|
| try {
|
| long interval = 2 * 1000;
| @SuppressWarnings("unused")
| Timer timer = processor.scheduleBuildings(new Date(), interval, null);
| }
| catch (RuntimeException e) {
| log.error("Scheduler ->engineControler - calcTasks(): " + e.getMessage());
| }
|
and here i get processor = null
|
On JBoss this works.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069032#4069032
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069032
Thanks for the info. I saw examples where the entities had @Name notations on them, so I started doing that, but that actually caused me a lot of confusion. When I use an outjection I can control the scope of components which are not @Named entities, but if it is @Named then the @Name setting controls the scope... that confused me a lot. It seems easier to just not put a @Name on the various entities, and use @Name only for actions. Then if I want to alias something I'll do that in components.xml, but I don't even need to do that. I would prefer to access userHome.instance instead of just user, because to me there's less ambiguity about which user I'm talking about with userHome.instance.
Thanks for clearing this up.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069024#4069024
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069024