[JBoss Seam] - Re: Named conversation and new instance redirected to Home?
by enda
I also thank you for the feedback so I tried this:
| <h:commandLink
| styleClass="left clearBoth"
| action="#{teamManager.select(teamItem)}" value="select">
| <s:conversationName value="teamHome"/>
| <s:conversationPropagation type="join" />
| </h:commandLink>
|
And it does not work, because then the navigation does not work.
I click the entry in table I want to edit and it does not redirect at all, method is called, but view stays in table. I think that to use <s:conversationPropagation type="join" /> I have to be inside a long-runnig conversation but I am not when I am in table page.
Solution Problem 1. manually join conversations (exactly as you said problem is with different stage of life-cycle) - But I would buy a better solution ;D
Solution Problem 2.
a)Either End conversation and create new one
b)Rename conversation in session bean
c)Assign unique id to a session bean for all its life (in this case 'new')
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126294#4126294
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126294
18 years, 2 months
[JBoss Portal] - Re: custom portal + css images
by PeterJ
You can package a theme in a war file with a layout like:
mytheme.war
| + mystyles.css
| + WEB-INF/
| + portal-themes.xml
| + web.xml
| + images/
| + mylogo.gif
| + myicon.ico
| + <lots more images>
The web.xml file is empty (just ) and the portal-themes.xml file contains:
<themes>
| <theme>
| <name>mytheme</name>
| <link rel="stylesheet" id="main_css" href="/mystyles.css" type="text/css"/>
| <link rel="shortcut icon" href="/images/myicon.ico"/>
| </theme>
| </themes>
|
In addition placing your theme under jboss-portal.sar/portal-core.war/themes is also acceptable, as long as you add the theme name to jboss-portal.sar/portal-core.war/WEB-INF/portal-themes.xml.
(Based on your post, I think you have done the above steps.)
If you want to use your theme as the default theme, you also need to change several files - do a search for the term "renaissance". Note, however, that you need to do this *before* you run the portal for the first time. If you have already run the portal, the best way to switch it to using your theme is to make that change in the management portlet.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126292#4126292
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126292
18 years, 2 months
[JBoss Seam] - Re: Seam & JBPM (WebConsole)
by mjung85
Thanks for your replies.
It seems to me that Seam uses JBPM in a very dirty way. I think the Web Console is one of the advantages of JBPM. I can use it to monitor the current tasks and the state of the business processes.
Without the console i have just the nearly undocumented built-in components and a database, where i can look what happens in a very uncomfortable way.
That makes the use of business processes in this way (Seam + JBPM) unattractive. It's like a black box where i put some process definitions and then i hope everything runs as expected.
1. Can you tell me where i can find it in the JBPM Wiki? I tried to use this .war archive.
http://wiki.jboss.org/wiki/Wiki.jsp?page=JbpmWebConsole
2. The version looked to be right for my jboss platform (AS 4.0.5, SEAM 1.2.0). I deployed it and then tried to access it (http://localhos:8080/jpbm/) but i get the following error, whats the problem?
2008-02-04 18:35:52,113 DEBUG [org.jbpm.webapp.filter.LogFilter] request http://localhost:8080/jbpm/
| 2008-02-04 18:35:52,113 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jbpm].[jsp]] Servlet.service() for servlet jsp threw exception
| java.lang.NoClassDefFoundError
| at java.lang.Class.forName0(Native Method)
| at java.lang.Class.forName(Class.java:164)
| at org.jbpm.webapp.context.Context.getPersistenceContext(Context.java:33)
| at org.jbpm.webapp.filter.PersistenceFilter.doFilter(PersistenceFilter.java:22)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jbpm.webapp.filter.ContextFilter.doFilter(ContextFilter.java:19)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jbpm.webapp.filter.LogFilter.doFilter(LogFilter.java:38)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126291#4126291
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126291
18 years, 2 months