[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3349) LDAPIdentityStore generates invalid filter on listUsers method
by Vinicius Carvalho (JIRA)
LDAPIdentityStore generates invalid filter on listUsers method
--------------------------------------------------------------
Key: JBSEAM-3349
URL: https://jira.jboss.org/jira/browse/JBSEAM-3349
Project: Seam
Issue Type: Bug
Components: Security
Affects Versions: 2.1.0.BETA1
Reporter: Vinicius Carvalho
The Filter generated by the component is creating an invalid query, the format is this:
(objectClass={0})(objectClass={1})
Where it should be:
(&(objectClass={0})(objectClass={1}))
We've fixed it by overriding the method with our own ldapidentitystore, below is just the minimal chage:
StringBuilder userFilter = new StringBuilder();
userFilter.append("(&");
Object[] filterArgs = new Object[getUserObjectClasses().length];
for (int i = 0; i < getUserObjectClasses().length; i++)
{
userFilter.append("(");
userFilter.append(getObjectClassAttribute());
userFilter.append("={");
userFilter.append(i);
userFilter.append("})");
filterArgs[i] = getUserObjectClasses()[i];
}
userFilter.append(")");
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3685) Add "rendered" attribute to s:decorate
by Chris Simons (JIRA)
Add "rendered" attribute to s:decorate
--------------------------------------
Key: JBSEAM-3685
URL: https://jira.jboss.org/jira/browse/JBSEAM-3685
Project: Seam
Issue Type: Feature Request
Affects Versions: 2.1.0.SP1, 2.1.0.GA, 2.1.0.CR1, 2.1.0.BETA1, 2.1.0.A1, 2.0.3.CR1, 2.0.2.SP1, 2.0.2.GA, 2.0.2.CR2, 2.0.2.CR1, 2.0.1.GA, 2.0.1.CR2, 2.0.1.CR1, 2.0.0.GA
Reporter: Chris Simons
Add an optional "rendered" attribute to s:decorate, if possible. If evaluated to false, this would preclude rendering of the template/component.
I haven't seen a request like this in the past (I hope I didn't miss anything).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3666) Natural Conversations: conversation id evaluated to null
by Arron Ferguson (JIRA)
Natural Conversations: conversation id evaluated to null
--------------------------------------------------------
Key: JBSEAM-3666
URL: https://jira.jboss.org/jira/browse/JBSEAM-3666
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.0.SP1
Environment: Ubuntu/Linux 7.10, Tomcat 6.0.16
Reporter: Arron Ferguson
This is a repost of https://jira.jboss.org/jira/browse/JBSEAM-3368 which was closed but not fixed.
The following errors occur with natural conversations (based on the attached use case):
If I'm at page 4 (http://localhost:8080/test/register4.html) and I type: http://localhost:8080/test/register2.html (i.e., without the natural conversation id appended at the end like this: http://localhost:8080/test/register1.html?memberID=2), I get the following evaluated to null error:
conversation id evaluated to null: regmem
The exception is spewed to the log file but shouldn't be and should use the rules in the pages.xml file for error handling (see attached project). However, even if I type http://localhost:8080/test/register1.html?memberID=2, this is still broken because the rules in the pages.xml file are not being honored. The pages.xml file specifies:
<rule if="#{memberreg.acceptedInformation}">
<redirect view-id="/register3.xhtml"/>
</rule>
Which states that this state should cause a redirect which is not happening. So, to recap,
The included test project includes the Ant build script, and in the third party directory a list of the jar files used. Note: you don't need the DA.jar file. The jboss-archive-browsing.jar file is not included in the JBoss Seam download and so I had to grab it from the JBoss site. The version of the jboss-archive-browsing.jar (according to the manifest in the jar) is:
Implementation-Version: 2.0.2.Alpha
As I mentioned in the previous version of this bug report that was closed, Shane mentioned that there was a little more "noise" in the file than needed. It was quickly discovered however that this project test file was useful for spotting other bugs (I believe he said it helped him find another bug) and so I'm hoping that the same perspective will be used this time around as well. This example project in particular can be used to test many of the use cases and ensure that natural conversation processing is robust.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1592) <s:graphicImage> should accept raw byte[] without conversion
by Gena Batalski (JIRA)
<s:graphicImage> should accept raw byte[] without conversion
------------------------------------------------------------
Key: JBSEAM-1592
URL: http://jira.jboss.com/jira/browse/JBSEAM-1592
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF
Affects Versions: 2.0.0.BETA1, 1.3.0.ALPHA, 1.2.1.GA
Environment: latest from repo
Reporter: Gena Batalski
Priority: Minor
It would be helpful to feed the <s:graphicImage> with raw byte[] (possible also ByteArray - stream) without converting it to BufferedImage or something else. Also the content type could be manually entered. Of course, its in the responsibility of the developer, to take care about the correctness of input. Optional attributes (forceContentType, forceImage or something else) could do this job on the UI side.
Background of the request:
if i comment out the byte[] handling in Image.class (line 404 method readImage()) as in a following snipplet, i get an expected quality. Otherwise, the image quality decreases significantly, especially for small images (icons, thumbnails).
/*
byte[] b = (byte[]) input;
readImage(new ByteArrayInputStream(b));
*/
output = (byte[]) input;
I also would have some possibility, to prepare the image on demand. Currently i'm using two servlets: one SeamResource and one for my images. My servlet receives an URI and selects an image LOB from DB, because it isn't necessary to store the images in memory (they could be large) and the images could stay unrequested. What i need is some kind callback (converter?) which asks me for byte[] or stream representation of an image uri.
Thanks
Gena
--
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
15 years, 1 month
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1855) FacesMessages.instance().addToControl and Datatable do not work properly
by Andy Bosch (JIRA)
FacesMessages.instance().addToControl and Datatable do not work properly
------------------------------------------------------------------------
Key: JBSEAM-1855
URL: http://jira.jboss.com/jira/browse/JBSEAM-1855
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 1.2.0.GA
Reporter: Andy Bosch
It is possible do add FacesMessages via the Seam functionality with FacesMessages.instance().addToControl. In the parameters you have to pass the component id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In the JSF-way you have to pass the client-id.
With normal input components you can use both ways. But when you work with datatables, you MUST work with the client-id, the Seam-way with using only the component-id does NOT work.
Explanation: When using a datatable-tag, you only have one component. The renderer generates the various rows. In the component-tree there is yet only one component! If you want to add a FacesMessage to one row, you can only work with client-ids (because you have to include the row-index).
My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.
--
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
15 years, 1 month
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2921) Wiki permission checking sometimes results in "no file extension in servlet path"
by Christian Bauer (JIRA)
Wiki permission checking sometimes results in "no file extension in servlet path"
---------------------------------------------------------------------------------
Key: JBSEAM-2921
URL: http://jira.jboss.com/jira/browse/JBSEAM-2921
Project: Seam
Issue Type: Bug
Components: Wiki
Reporter: Christian Bauer
Assigned To: Christian Bauer
I've seen this in the live log sometimes, couldn't reproduce it until now: Trigger a @Factory method on a page, the component that has the @Factory method has
@Create
public void create() {
if (!Identity.instance().hasPermission("User", "isAdmin", (User)Component.getInstance("currentUser") ) ) {
throw new AuthorizationException("You don't have permission for this operation");
}
}
This is from AdminHome.java. So for example try to access 'systemPreferenceEntities' variable without being an admin. This will result in a permission exception which is hidden and obscured by another exception in the exception handling phase:
>>> 12:45:02,053 DEBUG [org.jboss.seam.contexts.FacesLifecycle] >>> Begin exception recovery
>>> 12:45:02,055 DEBUG [org.jboss.seam.core.Manager] No stored conversation, or concurrent call to the stored conversation
>>> 12:45:02,059 DEBUG [org.jboss.seam.exception.Exceptions] reading exception mappings from /WEB-INF/pages.xml
>>> 12:45:02,064 DEBUG [org.jboss.seam.faces.Navigator] redirecting to: /wiki.xhtml
>>> 12:45:02,064 DEBUG [org.jboss.seam.contexts.FacesLifecycle] After render response, destroying contexts
>>> 12:45:02,066 DEBUG [org.jboss.seam.contexts.FacesLifecycle] <<< End JSF request for /wiki/
>>> 12:45:02,066 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/wiki].[default]] Servlet.service() for servlet default threw exception
java.lang.IllegalArgumentException: no file extension in servlet path: /
at org.jboss.seam.mock.MockViewHandler.getActionURL(MockViewHandler.java:44)
at org.jboss.seam.jsf.SeamViewHandler.getActionURL(SeamViewHandler.java:74)
at org.jboss.seam.faces.FacesManager.redirect(FacesManager.java:162)
at org.jboss.seam.faces.Navigator.redirect(Navigator.java:50)
at org.jboss.seam.exception.RedirectHandler.handle(RedirectHandler.java:51)
at org.jboss.seam.exception.Exceptions.handle(Exceptions.java:76)
at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70)
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:56)
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:158)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:613)
--
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
15 years, 1 month