[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2514) EntityQuery can't be used in PAGE Scope
by Martin Hoffmann (JIRA)
EntityQuery can't be used in PAGE Scope
---------------------------------------
Key: JBSEAM-2514
URL: http://jira.jboss.com/jira/browse/JBSEAM-2514
Project: JBoss Seam
Issue Type: Feature Request
Components: Framework
Affects Versions: 2.0.0.GA
Environment: Seam 2.0.0.GA, JBoss AS 4.2.2.GA
Reporter: Martin Hoffmann
Priority: Optional
The EntityHome is not able to operate in PAGE scope and the documentation says nothing about compatible scopes and framework classes.
It throws an exeption:
aused by: javax.el.ELException: /client/claim_list.xhtml @16,52 value="#{testList.dataModel}": Error reading 'dataModel' on type de.iseki.garantieext.card.Test
List_$$_javassist_0
at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.ja
va:76)
at javax.faces.component.UIOutput.getValue(UIOutput.java:173)
... 69 more
Caused by: java.lang.IllegalStateException: EntityManager is closed
at org.hibernate.ejb.EntityManagerImpl.getSession(EntityManagerImpl.java
:42)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2301) JBoss EL bug handling overloaded methods with varargs mixed in
by Matthew Lieder (JIRA)
JBoss EL bug handling overloaded methods with varargs mixed in
--------------------------------------------------------------
Key: JBSEAM-2301
URL: http://jira.jboss.com/jira/browse/JBSEAM-2301
Project: JBoss Seam
Issue Type: Bug
Components: EL
Affects Versions: 2.0.0.GA
Reporter: Matthew Lieder
Doing facesMessages.add("Message") from an EL expression doesn't work, complaining about the String class not being compatible with the FacesMessage class. The problem is caused by a combination of two things:
1. There are two FacesMessages.add(...) that can accept one parameter: add(FacesMessage facesMessage) and add(String messageTemplate, Object... params)
2. The FacesMessages.add(...) that accepts a String as the first parameter can optionally accept additional parameters through a vararg
If only one of those was the case, it'd work fine. However, having both at the same time triggers the error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2231) Setup wizard for wiki
by Christian Bauer (JIRA)
Setup wizard for wiki
---------------------
Key: JBSEAM-2231
URL: http://jira.jboss.com/jira/browse/JBSEAM-2231
Project: JBoss Seam
Issue Type: Feature Request
Components: Wiki
Reporter: Christian Bauer
Assigned To: Christian Bauer
Write a setup wizard that replaces the manual wiki-data.sql editing and import. We should have the following setup procedure:
- Get the recommended environment ready (JBoss AS, MySQL)
- Deploy the wiki-ddl.sql on a new database
- Deploy the wiki.war on the appserver
- Open http://server/wiki/ and go through the setup wizard
The wizard will first import the minimum dataset (guest/admin users, roles, start page) and then ask the usual setup questions (site base URL, etc.). Depending on the future of the plugin API, it could also optionally allow you to configure some plugin defaults so you don't have to go into the Admin screen to change them after the install. Also, we can offer prepackaged datasets for certain use cases that can be imported with the wizard, e.g. "Help Documents", "Blog Website", "Forum Website".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2452) Event logging and notification system
by Christian Bauer (JIRA)
Event logging and notification system
-------------------------------------
Key: JBSEAM-2452
URL: http://jira.jboss.com/jira/browse/JBSEAM-2452
Project: JBoss Seam
Issue Type: Feature Request
Components: Wiki
Reporter: Christian Bauer
Assigned To: Christian Bauer
Notification system that supports user personalization:
- All actions should throw events with a payload (otherwise context lookup in the generic event listener gets complicated)
- A generic event listener is the router for these events, pushes events to more specialized registered listeners (how do we observe all wiki.* events?)
- There has to be some asynchronous processing at that point, the generic event listener should not block
- Specialized listeners can register on the generic listener based on groups of events, e.g. "Document actions" or "User actions"
- The API for the specialized listeners (and how they are registered) has to be usable for the core and plugins
In a second step, implement the following core specialized listeners:
- access logging (document reads, etc.)
- channels bound to user, e.g. a user can build his own channel(s) by picking event groups he is interested in
Not sure at this point how notification looks like, that is, how listeners can push notifications (or whole channels?) to some endpoint (e-mail).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1563) create "bin" distribution
by Dan Allen (JIRA)
create "bin" distribution
-------------------------
Key: JBSEAM-1563
URL: http://jira.jboss.com/jira/browse/JBSEAM-1563
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.0.BETA1, 1.3.0.ALPHA, 1.2.1.GA
Reporter: Dan Allen
The current releases of Seam are ridiculously large, weighing in at around 80MB. That is almost as big as the JBoss AS download! While it is critical to offer the entire bundle for Seam developers, contributors, and source builders, I think it would be appropriate to offer a "bin" distribution that is intended just to run Seam. Perhaps just spin off seam-gen as its own download. That should give people exactly what they need to run Seam, and nothing more.
Below is a comparison table of some competing projects:
Spring Framework: 10MB (2.6MB if you pull it from the maven repository)
Ruby on Rails: 2.2 MB (standalone version)
I remember when I first discovered Seam, I put off trying it out because it was too hefty of a download. Let's make it more attractive.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1557) Seam is peforming a redirect in when running as a portlet, rather than using the portlet lifecycle
by Neil Griffin (JIRA)
Seam is peforming a redirect in when running as a portlet, rather than using the portlet lifecycle
--------------------------------------------------------------------------------------------------
Key: JBSEAM-1557
URL: http://jira.jboss.com/jira/browse/JBSEAM-1557
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.2.1.GA
Environment: WinXP / Liferay 4.3.0 / Tomcat 6.0.13
Reporter: Neil Griffin
Background: I found this problem when attempting to package the Seam "Registration" example as a portlet under Liferay Portal.
Section 7.4.2 of the JSF 1.1 specifcation says that since redirects are not possible in the case of portlets. Nevertheless, the Seam Conversation Manager (Manager.java) is forcing the portal to redirect outside its portal pages, rather than use the portlet lifecycle.
The way this would be manifested to the user would be like this: If a Seam application was contained within a portlet, and the portlet were placed on a portal page, then when the user clicks on a button that invokes navigation to a different JSF view, then the Seam application would "jump out" (so to speak) of the rectangular portlet container, and become a full-browser-page thing. This is incorrect. If a Seam application starts out as a portlet, then it must remain a portlet for its entire lifespan. In addition, the current behavior of Seam is not conforming to section 7.4.2 of the JSF 1.1. specification.
Now, it might be the case that this redirect works under JBoss Portal, but it causes exceptions to be thrown under Liferay Portal. This is because Liferay Portal expects JSF-based portlets to not perform redirects, as they must not do that anyway.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months