[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-730) User/Role/Permission model
by Gavin King (JIRA)
User/Role/Permission model
--------------------------
Key: JBSEAM-730
URL: http://jira.jboss.com/jira/browse/JBSEAM-730
Project: JBoss Seam
Issue Type: Feature Request
Components: Security
Reporter: Gavin King
Assigned To: Shane Bryzak
Fix For: 1.2.0.BETA1
There should be an optional component which plugs into Seam/Security to provide the following model:
Role (name, description, manager??)
User extends Role (password, firstName, lastName, additionalNames, email)
RoleRole (role, role)
Permission(objectName, operationName)
RolePermission(role,permission)
RoleInstancePermission(objectName, operationName, objectId)
This model would be extensible by the user, simply using inheritance.
There would be a built-in management console for creating users and roles and assigning roles and permissions.
--
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
18 years, 1 month
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1371) Unable to use TestNG groups with SeamTest
by Samuel Mendenhall (JIRA)
Unable to use TestNG groups with SeamTest
-----------------------------------------
Key: JBSEAM-1371
URL: http://jira.jboss.com/jira/browse/JBSEAM-1371
Project: JBoss Seam
Issue Type: Bug
Components: Test Harness
Affects Versions: 1.2.1.GA
Reporter: Samuel Mendenhall
Priority: Minor
testng xml in build.xml
++++++++++++++++++++++++++++++
<testng outputdir="${basedir}/test-report" groups="SomeGroups">
<classfileset dir="classes" includes="**/*.class" />
<classpath path="${test.dir}" />
<classpath path="${embedded-ejb3.dir}" />
<classpath refid="build.classpath" />
</testng>
++++++++++++++++++++++++++++++
EmptyTest.java
++++++++++++++++++++++++++++++
public class EmptyTest extends SeamTest {
@Test(groups = {"SomeGroups"})
public void testNothing() throws Exception {
new FacesRequest() {
@Override
protected void invokeApplication() throws Exception {
assert true;
}
}.run();
}
@Test
public void testNothingAgain() throws Exception {
assert true;
}
}
++++++++++++++++++++++++++++++
command:
++++++++++++++++++++++++++++++
ant test
++++++++++++++++++++++++++++++
Exception:
++++++++++++++++++++++++++++++
[testng] java.lang.NullPointerException
[testng] at org.jboss.seam.mock.SeamTest$Request.run(SeamTest.java:418)
[testng] at com.mydomain.convotest.EmptyTest.testNothing(EmptyTest.java:10)
..
++++++++++++++++++++++++++++++
--
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
18 years, 1 month
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1858) Ability to avoid view path repetition in pages.xml
by Matt Drees (JIRA)
Ability to avoid view path repetition in pages.xml
--------------------------------------------------
Key: JBSEAM-1858
URL: http://jira.jboss.com/jira/browse/JBSEAM-1858
Project: JBoss Seam
Issue Type: Feature Request
Reporter: Matt Drees
Priority: Minor
It would be fantastic if instead of this:
<page view-id="/admin/modules/additionalExpenses/registrantTypeSettings.xhtml">
<navigation from-action="#{additionalExpensesAdminManager.newExpense}">
<redirect view-id="/admin/modules/additionalExpenses/editExpense.xhtml"/>
</navigation>
<navigation from-action="#{additionalExpensesAdminManager.newSectionHeader}">
<redirect view-id="/admin/modules/additionalExpenses/editSectionHeader.xhtml"/>
</navigation>
</page>
I could do this:
<pages view-scope="/admin/modules/additionalExpenses/">
<page view-id="registrantTypeSettings.xhtml">
<navigation from-action="#{additionalExpensesAdminManager.newExpense}">
<redirect view-id="editExpense.xhtml"/>
</navigation>
<navigation from-action="#{additionalExpensesAdminManager.newSectionHeader}">
<redirect view-id="editSectionHeader.xhtml"/>
</navigation>
</page>
</pages>
It would be best if <pages> could be nested in other <pages>, but there are probably some other ramifications of that, so maybe it'd be better to introduce another element. Maybe <view-scope> or something.
--
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
18 years, 1 month
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1990) Reloading app causes IllegalStateException when passivating session objects
by Matt Drees (JIRA)
Reloading app causes IllegalStateException when passivating session objects
---------------------------------------------------------------------------
Key: JBSEAM-1990
URL: http://jira.jboss.com/jira/browse/JBSEAM-1990
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.CR1
Environment: Tomcat 5.5
Reporter: Matt Drees
Priority: Minor
I haven't tested in other appservers.
Reloading the Hibernate example causes the following stacktrace:
Sep 26, 2007 9:15:37 PM org.apache.catalina.session.StandardSession passivate
SEVERE: Session attribute event listener threw exception
java.lang.IllegalStateException: Attempted to invoke a Seam component outside the an initialized application
at org.jboss.seam.contexts.Lifecycle.getApplication(Lifecycle.java:36)
at org.jboss.seam.contexts.Lifecycle.beginCall(Lifecycle.java:84)
at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:113)
at org.jboss.seam.intercept.RootInterceptor.invokeAndHandle(RootInterceptor.java:84)
at org.jboss.seam.intercept.JavaBeanInterceptor.callPrePassivate(JavaBeanInterceptor.java:135)
at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:77)
at org.jboss.seam.example.hibernate.HotelSearchingAction_$$_javassist_2.sessionWillPassivate(HotelSearchingAction_$$_javassist_2.java)
at org.apache.catalina.session.StandardSession.passivate(StandardSession.java:764)
at org.apache.catalina.session.StandardManager.doUnload(StandardManager.java:515)
at org.apache.catalina.session.StandardManager.unload(StandardManager.java:462)
at org.apache.catalina.session.StandardManager.stop(StandardManager.java:666)
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4345)
at org.apache.catalina.core.StandardContext.reload(StandardContext.java:2984)
at org.apache.catalina.manager.ManagerServlet.reload(ManagerServlet.java:906)
at org.apache.catalina.manager.HTMLManagerServlet.reload(HTMLManagerServlet.java:473)
--
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
18 years, 1 month
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1323) MultipartRequest class incorrectly parses form post when field boundary occurs near end of internal buffer
by ROB b (JIRA)
MultipartRequest class incorrectly parses form post when field boundary occurs near end of internal buffer
----------------------------------------------------------------------------------------------------------
Key: JBSEAM-1323
URL: http://jira.jboss.com/jira/browse/JBSEAM-1323
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.2.1.GA, 1.2.0.GA
Environment: Windows Vista, Firefox 2.0.0, Java 1.6u1, JBoss AS 4.0.5.GA, JBoss Seam 1.2.1
Reporter: ROB b
Fix For: 1.3.0.BETA1
When a form post is processed by a MultipartRequest class and it has a field boundary that occurs near the end of the internal buffer of the MultipartRequest class, it fails to recognize the field boundary and interprets the field boundary and the following header to be a part of the previous field's contents.
This bug can most easily be reproduced by creating a form of enctype="multipart/form-data" with 30 <h:inputText> fields. The fields should be submitted empty. This provides form post data with lots of field boundaries and little in between. One of the field boundaries is likely to be near the end of the 2KB class buffer. When the bug occurs, one of the blank fields will be shown to contain part of the form boundary text. The form may have to be submitted 5 or 10 times, before the bug occurs.
This same technique also occasionally causes the JBSEAM-1322 bug to occur (rarely, though).
Sorry, I don't have a suggested fix. The class has been kind of hard for me to debug.
Submitting the following XHTML source multiple times can be used to demonstrate the bug:
<!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:s="http://jboss.com/products/seam/taglib"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:rich="http://richfaces.ajax4jsf.org/rich" >
<h:form enctype="multipart/form-data">
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:inputText />
<h:commandButton />
</h:form>
</html>
--
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
18 years, 1 month
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1960) Calling #{session.flush} erroneously requiring hibernate-search
by Matthew Lieder (JIRA)
Calling #{session.flush} erroneously requiring hibernate-search
---------------------------------------------------------------
Key: JBSEAM-1960
URL: http://jira.jboss.com/jira/browse/JBSEAM-1960
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0.CR1
Environment: JDK 1.5, Tomcat 5.5.23, Hibernate 3.2.5
Reporter: Matthew Lieder
I'm using Hibernate-managed transactions. In components.xml, I have:
<transaction:hibernate-transaction session="#{session}" />
Everything works great, except when I try to call session.flush from an EL expression (in pages.xml or a pageflow.jpdl.xml). When I try to do that, I get the following exception:
DEBUG Contexts - found in conversation context: session
ERROR ExceptionFilter - handling uncaught exception
javax.servlet.ServletException: Servlet execution threw an exception
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281)
at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:150)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
at java.lang.Thread.run(Thread.java:595)
When I have debug mode disabled, I get another stack trace that's quite a bit more informative:
ERROR [Faces Servlet] - Servlet.service() for servlet Faces Servlet threw exception
java.lang.NoClassDefFoundError: org/apache/lucene/search/Query
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2395)
at java.lang.Class.privateGetPublicMethods(Class.java:2519)
at java.lang.Class.getMethods(Class.java:1406)
at org.jboss.el.util.ReflectionUtil$MethodCache.<init>(ReflectionUtil.java:158)
at org.jboss.el.util.ReflectionUtil$1.create(ReflectionUtil.java:146)
at org.jboss.el.util.ReflectionUtil$1.create(ReflectionUtil.java:145)
at org.jboss.el.util.ReferenceCache.get(ReferenceCache.java:241)
at org.jboss.el.util.ReflectionUtil.findMethod(ReflectionUtil.java:207)
at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:272)
at org.jboss.el.parser.AstMethodSuffix.getValue(AstMethodSuffix.java:59)
at org.jboss.el.parser.AstMethodSuffix.invoke(AstMethodSuffix.java:65)
at org.jboss.el.parser.AstValue.invoke(AstValue.java:96)
at org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
at org.jboss.seam.core.Expressions$2.invoke(Expressions.java:174)
at org.jboss.seam.navigation.Page.preRender(Page.java:275)
at org.jboss.seam.navigation.Pages.preRender(Pages.java:309)
at org.jboss.seam.jsf.SeamPhaseListener.preRenderPage(SeamPhaseListener.java:544)
at org.jboss.seam.jsf.SeamPhaseListener.beforeRenderResponse(SeamPhaseListener.java:455)
at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:146)
at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:116)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281)
at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:150)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
at java.lang.Thread.run(Thread.java:595)
Everything works fine if I include hibernate-search and its dependencies (including lucene). Calling session.flush from a Java class works fine, no matter if hibernate-search is available or not. Very strange...
--
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
18 years, 1 month