August 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAM-94) Shaded jars like seam-solder instead of seam-solder-api and seam-solder-impl result in the same classes twice in the classpath (possibly different versions)

by Geoffrey De Smet (JIRA)

Shaded jars like seam-solder instead of seam-solder-api and seam-solder-impl result in the same classes twice in the classpath (possibly different versions) ------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: SEAM-94 URL: https://issues.jboss.org/browse/SEAM-94 Project: Seam 3 Distribution Issue Type: Bug Reporter: Geoffrey De Smet Shaded jars (like seam-solder) are highly problematic in itself, see WELD-935. Trying to avoid the shaded jars, is impossible, as this example shows: {code} $ mvn dependency:tree ... [INFO] +- org.jboss.seam.solder:seam-solder-api:jar:3.0.0.Final:compile ===========> my compile dependency on solder-api (the non-shaded jar) [INFO] +- org.jboss.seam.solder:seam-solder-impl:jar:3.0.0.Final:runtime ==========> my runtime dependency on solder-impl (the non-shaded jar) [INFO] +- org.jboss.seam.security:seam-security-api:jar:3.0.0.Final:compile ... [INFO] +- org.jboss.seam.security:seam-security-impl:jar:3.0.0.Final:compile [INFO] | +- org.jboss.seam.solder:seam-solder:jar:3.0.0.Final:compile ============> transitive dependency on solder (the shaded jar) which shades the classes of solder-api {code} Now suppose I depend on solder-api 3.0..Final instead (still with seam-security-impl 3.0.0.Final): I 'd have 2 different versions of solder in my classpath. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-4553) Support formal integration with PicketLink

by Shane Bryzak (JIRA)

Support formal integration with PicketLink ------------------------------------------ Key: JBSEAM-4553 URL: https://jira.jboss.org/jira/browse/JBSEAM-4553 Project: Seam Issue Type: Task Components: Security Reporter: Shane Bryzak Assignee: Shane Bryzak Fix For: 3.0.0.BETA1 We need formal support for PicketLink, at least documentation and possibly some code. -- 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

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-4503) <s:token> - cookie identifying the browser (javax.faces.ClientToken) might contain illegal characters

by dragos cernahoschi (JIRA)

<s:token> - cookie identifying the browser (javax.faces.ClientToken) might contain illegal characters ----------------------------------------------------------------------------------------------------- Key: JBSEAM-4503 URL: https://jira.jboss.org/jira/browse/JBSEAM-4503 Project: Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.2.0.GA Reporter: dragos cernahoschi The cookie that uniquely identifies the browser is randomly generated and contains illegal characters, for example: semicolon (;) This cause org.jboss.seam.ui.UnauthorizedCommandException: viewId: /restricted/desktop.xhtml - Form signature invalid -- 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

12 years, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-31) Create example to demonstrate ACL permissions

by Shane Bryzak (JIRA)

Create example to demonstrate ACL permissions --------------------------------------------- Key: SEAMSECURITY-31 URL: https://issues.jboss.org/browse/SEAMSECURITY-31 Project: Seam Security Issue Type: Task Reporter: Shane Bryzak Assignee: Shane Bryzak Fix For: 3.0.0.Beta2 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (SEAMSERVLET-22) Test Seam Servlet in an EAR with multiple web apps

by Dan Allen (JIRA)

Test Seam Servlet in an EAR with multiple web apps -------------------------------------------------- Key: SEAMSERVLET-22 URL: https://issues.jboss.org/browse/SEAMSERVLET-22 Project: Seam Servlet Issue Type: Feature Request Components: Compliance, Producers, Test Suite Affects Versions: 3.0.0.Alpha2 Reporter: Dan Allen Assignee: Dan Allen We want to verify that we haven't broken any assumptions, such as whether the correct ServletContext is injected. Should be relatively easy to solve with Arquillian. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
9
0 / 0

[JBoss JIRA] Created: (SEAMSERVLET-42) Seam Servlet broken in multi-war ear deployment

by Jozef Hartinger (JIRA)

Seam Servlet broken in multi-war ear deployment ----------------------------------------------- Key: SEAMSERVLET-42 URL: https://issues.jboss.org/browse/SEAMSERVLET-42 Project: Seam Servlet Issue Type: Bug Affects Versions: 3.0.0.Final Reporter: Jozef Hartinger Fix For: 3.0.1.Beta1 The Servlet specification requires a java library to be bundled within the WEB-INF/lib folder for its web-fragment.xml to be read. Therefore, if multiple web applications using Seam Servlet are bundled within an EAR, they all have to package Seam Servlet within their WEB-INF/lib folders. The CDI specification is not clear in defining the application scope in an EAR (See https://issues.jboss.org/browse/CDI-129 for details.) JBoss AS 7 implements the application scope as per-ear. This results in conflicts between multiple instances of Seam Servlet. Therefore, when the ear is deployed, the deployment fails with AmbiguousResolutionException like the following one: 15:14:42,467 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.deployment.unit."test.ear".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.ear".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-001409 Ambiguous dependencies for type [HttpServletRequest] with qualifiers [@Default] at injection point [[field] @Inject private org.jboss.seam.servlet.http.CookieParamProducer.request]. Possible dependencies [[Producer Method [HttpServletRequest] with qualifiers [@Any @Default] declared as [[method] @Produces @Typed @RequestScoped protected org.jboss.seam.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest()], Producer Method [HttpServletRequest] with qualifiers [@Any @Default] declared as [[method] @Produces @Typed @RequestScoped protected org.jboss.seam.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest()]]] at org.jboss.as.weld.services.WeldService.start(WeldService.java:96) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001409 Ambiguous dependencies for type [HttpServletRequest] with qualifiers [@Default] at injection point [[field] @Inject private org.jboss.seam.servlet.http.CookieParamProducer.request]. Possible dependencies [[Producer Method [HttpServletRequest] with qualifiers [@Any @Default] declared as [[method] @Produces @Typed @RequestScoped protected org.jboss.seam.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest()], Producer Method [HttpServletRequest] with qualifiers [@Any @Default] declared as [[method] @Produces @Typed @RequestScoped protected org.jboss.seam.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest()]]] at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:274) at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:106) at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:129) at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:351) at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:336) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:404) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82) at org.jboss.as.weld.services.WeldService.start(WeldService.java:89) ... 5 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (SEAM-58) seam-booking - functional tests fail although the application works as expected

by Jozef Hartinger (JIRA)

seam-booking - functional tests fail although the application works as expected ------------------------------------------------------------------------------- Key: SEAM-58 URL: https://issues.jboss.org/browse/SEAM-58 Project: Seam 3 Distribution Issue Type: Bug Components: Shared Examples Affects Versions: 3.0.0.CR3 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 3.0.0.Final FAILED CONFIGURATION: @BeforeMethod setUp java.lang.AssertionError: Login failed. at org.jboss.seam.examples.booking.ftest.AbstractBookingTest.login(AbstractBookingTest.java:69) at org.jboss.seam.examples.booking.ftest.AbstractBookingTest.login(AbstractBookingTest.java:53) at org.jboss.seam.examples.booking.ftest.AbstractBookingTest.setUp(AbstractBookingTest.java:45) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:74) at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) ... Removed 28 stack frames -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-18) Ssl and authentication is not properly supported

by Marek Smigielski (JIRA)

Ssl and authentication is not properly supported ------------------------------------------------ Key: SEAMMAIL-18 URL: https://issues.jboss.org/browse/SEAMMAIL-18 Project: Seam Mail Issue Type: Bug Reporter: Marek Smigielski 1. When ssl is configured client hung on: at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at com.sun.mail.util.TraceInputStream.read(TraceInputStream.java:106) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) - locked <0x00000000f84a7420> (a java.io.BufferedInputStream) at com.sun.mail.util.LineInputStream.readLine(LineInputStream.java:84) at com.sun.mail.smtp.SMTPTransport.readServerResponse(SMTPTransport.java:1742) at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1523) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:453) at javax.mail.Service.connect(Service.java:291) - locked <0x00000000f849d258> (a com.sun.mail.smtp.SMTPTransport) at javax.mail.Service.connect(Service.java:172) at javax.mail.Service.connect(Service.java:121) 2. Despite setting authentication credetntials i get from gmail server: Caused by: com.sun.mail.smtp.SMTPSendFailedException: 530-5.5.1 Authentication Required. Learn more at 530 5.5.1 http://mail.google.com/support/bin/answer.py?answer=14257 q18sm1346208bka.15 at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1668) [:1.4.2] at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:1207) [:1.4.2] at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:735) [:1.4.2] at javax.mail.Transport.send0(Transport.java:191) [:1.4.2] at javax.mail.Transport.send(Transport.java:120) [:1.4.2] at org.jboss.seam.mail.core.BaseMailMessage.send(BaseMailMessage.java:452) [:3.0.0-SNAPSHOT] ... 244 more Configuration: MailConfig mailConfig = new MailConfig(); mailConfig.setServerHost("smtp.gmail.com"); mailConfig.setServerPort(465); mailConfig.setSsl(true); mailConfig.setUsername("username"); mailConfig.setPassword("password"); mailConfig.setAuth(true); Session session = MailUtility.buildMailSession(mailConfig); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
8
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-12) Cleanup JavaDocs on API

by Cody Lerum (JIRA)

Cleanup JavaDocs on API ----------------------- Key: SEAMMAIL-12 URL: https://issues.jboss.org/browse/SEAMMAIL-12 Project: Seam Mail Issue Type: Task Reporter: Cody Lerum Assignee: Cody Lerum Fix For: 3.0.0.Alpha1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-22) Follow Seam 3 example naming scheme

by Jozef Hartinger (JIRA)

Follow Seam 3 example naming scheme ----------------------------------- Key: SEAMMAIL-22 URL: https://issues.jboss.org/browse/SEAMMAIL-22 Project: Seam Mail Issue Type: Task Reporter: Jozef Hartinger Priority: Minor Please, follow these naming constraints for the sample application to be consistent with other Seam 3 demos. {noformat} folder name: {example} artifact id: seam-{module}-example-{example} context path: {module}-{example} package: org.jboss.seam.{module}.examples.{example} {noformat} * use dashes as delimiters * if the example name uses dashes ( - ), these are removed in the package name Currently, the context path (finalName) and package name are wrong. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2011