February 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMSECURITY-36) Seam Security depends on SNAPSHOT version of seam-bom

by Jozef Hartinger (JIRA)

Seam Security depends on SNAPSHOT version of seam-bom ----------------------------------------------------- Key: SEAMSECURITY-36 URL: https://issues.jboss.org/browse/SEAMSECURITY-36 Project: Seam Security Issue Type: Bug Affects Versions: 3.0.0.Beta2 Reporter: Jozef Hartinger Assignee: Shane Bryzak Priority: Critical https://github.com/seam/security/blob/3.0.0.Beta2/pom.xml This makes it difficult to verify that appropriate artifacts are present in the dist bundle, etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (SEAMVALIDATE-1) Provide the possibility to specify the validation groups for method validation

by Gunnar Morling (JIRA)

Provide the possibility to specify the validation groups for method validation ------------------------------------------------------------------------------ Key: SEAMVALIDATE-1 URL: https://issues.jboss.org/browse/SEAMVALIDATE-1 Project: Seam Validation Issue Type: Feature Request Reporter: Gunnar Morling Assignee: Gunnar Morling The @AutoValidating annotation should provide the possibility to specify which validation groups should be considered for parameter and return value validation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFACES-78) Misc documentation issues

by Jozef Hartinger (JIRA)

Misc documentation issues ------------------------- Key: SEAMFACES-78 URL: https://issues.jboss.org/browse/SEAMFACES-78 Project: Seam Faces Issue Type: Bug Components: Documentation Affects Versions: 3.0.0.Beta2 Reporter: Jozef Hartinger Priority: Minor Fix For: 3.0.0.Beta3 * Syntax highlighting of Java samples is disabled in most cases - use 'role="XML"' attribute in <programlisting> tags * Section 9.1.1 ** "Each observer method must accept one method parameter:" - this is IMHO misleading since CDI observers do not required exactly one method parameter - multiple are allowed and each one is treated as an injection point ** (See the CDI Reference Guide for more information on events and observing.) - add hyperlink -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (SEAMINTL-23) Remove jboss-logging dependency

by Jozef Hartinger (JIRA)

Remove jboss-logging dependency ------------------------------- Key: SEAMINTL-23 URL: https://issues.jboss.org/browse/SEAMINTL-23 Project: Seam International Issue Type: Task Affects Versions: 3.0.0.Beta1 Reporter: Jozef Hartinger Assignee: Shane Bryzak Priority: Minor Fix For: 3.0.0.Beta2 Since version 3.0.0.Beta2 Seam Solder bundles jboss-logging. Thus, there is no need to declare an explicit dependency. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (SEAMINTL-24) Misc documentation issues

by Jozef Hartinger (JIRA)

Misc documentation issues ------------------------- Key: SEAMINTL-24 URL: https://issues.jboss.org/browse/SEAMINTL-24 Project: Seam International Issue Type: Bug Affects Versions: 3.0.0.Beta1 Reporter: Jozef Hartinger Priority: Minor Fix For: 3.0.0.Beta2 * Chapter 1 ** use <literal> for file names ** "by including the seam-international.jar and seam-international-api.jar" should be *** either "by including the seam-international-api.jar and seam-international-impl.jar" *** or just "by including the seam-international.jar" * Chapter 2 ** "through XML Config" should be "through Seam Config" - ideally with reference to the Seam Config project ** example 1 and 2 in section 2.1 and example 2 in section 2.3 - "<s:specializes/>" is no longer supported by Seam Config * Section 3.1 - s/XML Config/Seam Config -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (SEAMFACES-84) seam-faces.taglib has an typo

by Christof Van Hove (JIRA)

seam-faces.taglib has an typo ----------------------------- Key: SEAMFACES-84 URL: https://issues.jboss.org/browse/SEAMFACES-84 Project: Seam Faces Issue Type: Bug Reporter: Christof Van Hove It should be "http://java.sun.com/xml/ns/javaee/web-facelettaglibrary_2_0.xsd" instead of"http://java.sun.com/xml/ns/javaee/web-facelettaglibary_2_0.xsd". There is an 'r' missing in library -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-42) Unable to deploy JAXRS example to JBossAS 6

by Martin Gencur (JIRA)

Unable to deploy JAXRS example to JBossAS 6 ------------------------------------------- Key: SEAMCATCH-42 URL: https://issues.jboss.org/browse/SEAMCATCH-42 Project: Seam Catch Issue Type: Bug Affects Versions: 3.0.0.Beta1 Environment: JBoss AS 6 Final Reporter: Martin Gencur Assignee: Jason Porter Fix For: 3.0.0.Beta2 I tried to package and deploy the example according to the readme.md file in the example. "mvn clean package jboss:hard-deploy -Pjbossas" The JBossAS throws the following exception (the whole stacktrace in the attached file). The root cause is the following: Caused by: java.lang.annotation.AnnotationTypeMismatchException: Incorrectly typed data found for annotation element public abstract org.jboss.logging.Logger$Level org.jboss.logging.LogMessage.level() (Found data of type Lorg/jboss/logging/Logger$Level;.TRACE) at sun.reflect.annotation.AnnotationTypeMismatchExceptionProxy.generateException(AnnotationTypeMismatchExceptionProxy.java:38) [:1.6.0_21] at sun.reflect.annotation.AnnotationInvocationHandler.invoke(AnnotationInvocationHandler.java:56) [:1.6.0_21] at $Proxy175.level(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_21] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_21] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_21] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_21] at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:60) [jboss-reflect.jar:2.2.0.GA] at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:168) [jboss-reflect.jar:2.2.0.GA] at org.jboss.reflect.plugins.SecurityActions.invokeMethod(SecurityActions.java:78) [jboss-reflect.jar:2.2.0.GA] at org.jboss.reflect.plugins.AnnotationValueFactory.createAnnotationValue(AnnotationValueFactory.java:117) [jboss-reflect.jar:2.2.0.GA] ... 64 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-40) New example w/o REST

by Jason Porter (JIRA)

New example w/o REST -------------------- Key: SEAMCATCH-40 URL: https://issues.jboss.org/browse/SEAMCATCH-40 Project: Seam Catch Issue Type: Task Reporter: Jason Porter Assignee: Jason Porter Fix For: 3.0.0.Beta2 A new example should be done and the current one retired. Here's the email thread talking about an idea between myself and Dan Allen: >From Jason: Since we're being asked for examples to give to QE and Jozef has integrated catch into his module (and has some tests for it, and also asked me to remove the jaxrs example) I'm not quite sure what to do for a new example that wouldn't confuse because because Rest, Faces and Servlet all have Catch integrations. I could do one for wicket, but once wicket has an integration I'd need to retire that one as well. Do you have any ideas? >From Dan: I would go with simple and easy :) In your case, the example is going to be about show-and-tell more than test coverage. My suggestion would be to create an index page with a couple buttons. Catch error and: Show pretty error Redirect to page Log error and ignore You can just base the examples on a failing Servlet. You could also include an example of throwing an exception to Catch explicitly (instead of waiting for it to bubble from Servlet). But again, keep it simple. Just give the user a feel for what they can do. Make sure you have the simplest possible example in there, so that they can see the big picture. Then, add others that are fancier as you see fit. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4452) Enable LdapIdentityStore to access LDAP via SSL

by Marco Brizi (JIRA)

Enable LdapIdentityStore to access LDAP via SSL ----------------------------------------------- Key: JBSEAM-4452 URL: https://jira.jboss.org/jira/browse/JBSEAM-4452 Project: Seam Issue Type: Feature Request Affects Versions: 2.2.0.GA Environment: Ubuntu 9.04, JBoss AS 5.1.0 GA Reporter: Marco Brizi The current LdapIdentityStore offers a good support for integrate an LDAP repository. Unfortunately, at the moment, there is no configuration to access it via SSL. The minimum support could be done by adding a new boolean attribute (for ex. ssl-enabled) in the ldap-identity-store element to offer the possibility to choose or not a secure communication. I've tried to implement this extension changing security-2.2.xsd and the LdapIdentityStore class. In the second file my work has been on new attribute getter/setter and on initialiseContext(String principal, String credentials) method just adding the following lines : String ldapProtocol = "ldap"; if (isSslEnabled()) { ldapProtocol = "ldaps"; env.setProperty(Context.SECURITY_PROTOCOL, "ssl"); } String providerUrl = String.format("%s://%s:%d", ldapProtocol, getServerAddress(), getServerPort()); In addition get the server certificate and set the -D/usr/lib/jvm/java-6-sun=/path/to/keystore as JAVA_OPTS is needed. At the moment I'm able to initiate the communication with secure LDAP server but the Identity.authenticate causes a "javax.security.auth.login.LoginException: Login Failure: all modules ignored" The complete stacktrace is attached to the issue. -- 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

14 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-25) Examples in the Remoting module do not work now

by Martin Gencur (JIRA)

Examples in the Remoting module do not work now ----------------------------------------------- Key: SEAMREMOTING-25 URL: https://issues.jboss.org/browse/SEAMREMOTING-25 Project: Seam Remoting Issue Type: Bug Reporter: Martin Gencur Assignee: Shane Bryzak Fix For: 3.0.0.Beta2 A combination of the following commits caused the examples to not work: 97356ae - add web-fragment.xml 55514ba - SEAMREMOTING-1 use web-fragment.xml to define remoting servlet. Removed unnecessary web.xml files from examples There is probably some more configuration needed for this to work properly. None of the examples works correctly now. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2011