[JBoss Seam] - Re: Error selecting object
by laxu
I have downloaded jboss-seam-CVS.20070503
and rearranged libraries etc. to use it instead of 1.2.1GA but I cannot seem to get past the following exception.
Exception during request processing: javax.el.ELException: Error Parsing: #{isteklerAction.selectIstek(i)}
|
| com.sun.el.lang.ExpressionBuilder.createNodeInternal(ExpressionBuilder.java:140)
| com.sun.el.lang.ExpressionBuilder.build(ExpressionBuilder.java:157)
| com.sun.el.lang.ExpressionBuilder.createMethodExpression(ExpressionBuilder.java:208)
| com.sun.el.ExpressionFactoryImpl.createMethodExpression(ExpressionFactoryImpl.java:63)
| org.jboss.seam.core.Expressions$2.createExpression(Expressions.java:95)
| org.jboss.seam.core.Expressions$2.invoke(Expressions.java:99)
| org.jboss.seam.core.Pages.callAction(Pages.java:499)
| org.jboss.seam.core.Pages.enterPage(Pages.java:284)
| org.jboss.seam.jsf.AbstractSeamPhaseListener.enterPage(AbstractSeamPhaseListener.java:276)
| org.jboss.seam.jsf.AbstractSeamPhaseListener.beforeRender(AbstractSeamPhaseListener.java:214)
| org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:56)
| com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:214)
| com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140)
| javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
| org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
| org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:216)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
| org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:216)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
| org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:126)
| org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:248)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:216)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
| org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:276)
| org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
| org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
| org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
| org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042821#4042821
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042821
17 years, 4 months
[JBoss Portal] - finding solution to pass parameters from one portlet to 3 po
by moj_sham
Hi,
We are trying to find a solution to pass parameters from one portlet placed in the main page of the portal to 3 portlet that are placed on a different page and opens in a new window.
The senerio is like this. We have "userslist" portlet in the main page, it displays all the users with a link to view the details of that user in the new browser window. The url to view the user detail is a portal page url (eg. /portal/portal/default/UserDetailpg?userid=adminuser).
The user details page has 3 portlets that displays different details of the users like personal information, his documents list, his task list details. When the user clicks on the name of the user the url has a parameter and value userid=admin
We are trying to get the userid parameter passed in the url in portlets placed in the UserDetailpg and we always get null.
So is there a way in jboss portal framework to get this parameter value in all the 3 portlet in a new page.
With our past experience in the bea weblogic portal framework we had seen a way to handle this. From the portletrequest (Inner Request) we had a method to get the HttpServletRequest (OuterRequest) which can be used to get all the parameter that are passed in the URL.
Regards
Manoj
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042818#4042818
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042818
17 years, 4 months
[JBoss Seam] - Design Questions
by tony.herstell＠gmail.com
I have a seam bean, conversational, and in this bean I have delegated work out to another bean (8 actually!).
Since the main bean is conversational I require these delegated beans to do work within my conversation.
I biject these delegates using:
| /**
| * Biject the nameDescriptionStepController
| */
| @In(create=true) @Out
| private SectionStepController nameDescriptionStepController;
|
What should I set the beans to be as they really dont have a @Begin and @End?
They currently are :
| @CacheConfig(idleTimeoutSeconds=1800) // This keep the object "alive" longer than the session.
| @Stateful // A component stays in existance for the duration of the Scope (conversation in this instance).
| @Name("nameDescriptionStepController") // Name used within SEAM for an instance of this class.
| @Conversational // Scope that this class exists in.
|
but I get the occasional "not in long running conversational....
I use the contents of a beans in the GUI.. hence they are outjected.
I must be missing a piece oif the jigsaw.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042811#4042811
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042811
17 years, 4 months
[JBoss Seam] - Re: Trinidad PPR/Ajax and Seam
by chane
"smithbstl" wrote :
| I still can't find a way to propagate the conversation to the dialog window. I have tried the above mentioned Phase Listener and also the s:conversationPropagation tag in Seam's Library. Neither seem to work.
|
The test app I put together does propagate the conversation to the dialog. To see it do the following:
- on the first page there should be a conversation id on the page
- this is a temporary conversation
- click start button
- a new conversation id should be created
- this is a long running conversation
- click main (it's the second button)
- a new page should open up, the long running cid should be displayed
- click start dialog
- the dialog should open up and should be showing the long running cid
I need a long running conversation and I believe both the PhaseListener and ActionListener are needed. To bad it doesn't seem like we can figure out a way to get it to work without these modifications.
Maybe something in Seam 1.3. Probably need to use the trinidad-seam extension that the JBoss guys are creating with some added "glue" to get the conversation to propagate correctly across dialogs. Hopefully with this ground work they can think of something a little more elegant than this quick hack.
Chris....
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042806#4042806
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042806
17 years, 4 months
[Clustering/JBoss] - Re: Two-Node Cluster UDP OutOfMemoryError
by bstansberry＠jboss.com
It's hard to tell cause from effect in this kind of situation. Your log shows node1 being suspected by node2 and properly starting the process of closing down the channel to rejoin. Then a few ms later the vm runs out of memory.
Most likely whatever was going on that eventually led to the OOME was also making node1 unresponsive enough that node2 suspected it.
The question is why the OOME occurred. First, it's *extremely* unlikely the process of handling the suspicion and closing the channel is itself what caused the OOME. Second, the fact that UDP is what threw the OOME doesn't really mean it or JGroups was the underlying cause -- it just means UDP was the code trying to allocate an object when the heap was finally out of space.
JGroups 2.4.1.SP3 has an improvement to the FC (flow control) protocol that prevents an OOME condition that could occur when the channel is running under sustained overload. That may help. But, IMHO the odds are pretty low that that was the cause of your OOME. You're better off trying to profile your application to confirm you have no memory leaks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042805#4042805
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042805
17 years, 4 months
[JBoss jBPM] - Re: JBPM Timer Problem
by avivstav
I add the JobExecutorServlet to my configuration as mentiond and I get the following error while satrt up the application:
2007-05-03 15:18:00,328 ERROR [org.jbpm.job.executor.JobExecutorThread] exception in job executor thread. waiting 40000 milliseconds
org.hibernate.MappingException: invalid configuration
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1411)
at org.hibernate.cfg.Configuration.configure(Configuration.java:1352)
at org.jbpm.db.hibernate.HibernateHelper.createConfiguration(HibernateHelper.java:91)
at org.jbpm.persistence.db.DbPersistenceServiceFactory.getConfiguration(DbPersistenceServiceFactory.java:69)
at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:91)
at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:94)
at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:98)
at org.jbpm.persistence.db.DbPersistenceService.getJobSession(DbPersistenceService.java:352)
at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:563)
at org.jbpm.job.executor.JobExecutorThread.acquireJobs(JobExecutorThread.java:109)
at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:56)
Caused by: org.xml.sax.SAXParseException: Element type "value" must be declared.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.dom4j.io.SAXReader.read(SAXReader.java:465)
at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1408)
... 10 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042804#4042804
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042804
17 years, 4 months