September 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMMAIL-17) Test cases fails and errors

by Marek Smigielski (JIRA)

Test cases fails and errors --------------------------- Key: SEAMMAIL-17 URL: https://issues.jboss.org/browse/SEAMMAIL-17 Project: Seam Mail Issue Type: Bug Reporter: Marek Smigielski 1.testTextMailMessage junit.framework.AssertionFailedError: Didn't receive the expected amount of messages. Expected 1 got 0 at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.seam.mail.MailMessageTest.testTextMailMessage(MailMessageTest.java:131) 2. template.html.vm resource not mapped correctly 3. testVelocityTextMailMessage junit.framework.AssertionFailedError: Didn't receive the expected amount of messages. Expected 1 got 0 at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.seam.mail.VelocityMailMessageTest.testVelocityTextMailMessage(VelocityMailMessageTest.java:133) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

6
9
0 / 0

[JBoss JIRA] Created: (SEAMREPORTS-20) Support for MVEL

by George Gastaldi (JIRA)

Support for MVEL ---------------- Key: SEAMREPORTS-20 URL: https://issues.jboss.org/browse/SEAMREPORTS-20 Project: Seam Reports Issue Type: Feature Request Reporter: George Gastaldi Add Support for MVEL - enabled reports. The purpose is to take advantage of the same features Seam Render owns. See http://mvel.codehaus.org -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (SEAMCONFIG-49) Support fields of the class Properties: replacing and modifying (regression from seam 2)

by Geoffrey De Smet (JIRA)

Support fields of the class Properties: replacing and modifying (regression from seam 2) ---------------------------------------------------------------------------------------- Key: SEAMCONFIG-49 URL: https://issues.jboss.org/browse/SEAMCONFIG-49 Project: Seam Config Issue Type: Feature Request Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet In seam 2 you could do something like this: {code} <component name="repositoryConfiguration"> <property name="setupProperties"> <key>org.drools.repository.configurator</key><value>org.drools.repository.jackrabbit.JackrabbitRepositoryConfigurator</value>   </property> </component> {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
3
0 / 0

[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

13 years, 3 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

13 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-4841) Mail MIME Attachment IS NOT TO SPEC

by nathan dennis (JIRA)

Mail MIME Attachment IS NOT TO SPEC ----------------------------------- Key: JBSEAM-4841 URL: https://issues.jboss.org/browse/JBSEAM-4841 Project: Seam 2 Issue Type: Bug Components: Mail Affects Versions: 2.2.0.GA Environment: Centos 5.x, Centos 6.x, Jboss 5.1.0, Thunderbird 5.x, Thunderbird 6.x Reporter: nathan dennis Assignee: Pete Muir Message containing attachments not intended to be displayed inline are being formatted incorrectly. The current MIME type is not to spec RFC2387. (http://www.ietf.org/rfc/rfc2387.txt) As a result, mail clients that have chosen to strictly follow the spec will no longer correctly handle non inline attachments generated with seam mail. i believe this is related to JBSEAM-3906. However that work around listed there will create more problems than it will fix. (i actually tried that workaround on my own before i even visited the forum for help.) on closer inspection, it will attach ALL attachments using the inherited parent MIME type mixed which will cause all of your inline content to not be formatted. ei... <m:attachment value="/img.png" contentType="image/jpeg" fileName="header.jpg" status="headerPhoto" disposition="inline" /> <img src="cid:#{headerPhoto.contentId}" /> will no long work. i actually started rewriting some of UIBody.java only to realize i needed to read and study more before i wrote a patch. below is a sample message. Message-ID: <1992253538.401315329484805.JavaMail.jboss@node1> Subject: Online Credit Application MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_65_749177026.1315329484754" X-Priority: 5 Priority: Non-urgent Importance: low X-Sent-From: Node1 Date: Tue, 6 Sep 2011 13:18:04 -0400 (EDT) ------=_Part_65_749177026.1315329484754 Content-Type: multipart/related; (***********************PROBLEM IS HERE and inherited below*********************) boundary="----=_Part_66_721653621.1315329484804" ------=_Part_66_721653621.1315329484804 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------=_Part_66_721653621.1315329484804 Content-Type: application/pdf; name=XXXXXXXXXXX.pdf Content-Transfer-Encoding: base64 Content-ID: <aeamddeazitbtngdcsln> Content-Disposition: attachment; filename=XXXXXXXXXXX.pdf JVBERi0xLjQKJeLjz9MKMyAwIG9iaiA8PC9MZW5ndGggMTY0My9GaWx0ZXIvRmxhdGVEZWNvZGU+ PnN0cmVhbQp4nJVY227bNhi+91MQ2MVSoGEkijrtZkucZHWRUxsPRYfe0BITc5FFl5KbeE/TR91P yk5s+aeTIUhgh/z+85HfByfjQRjTMCUZS2gWkXE5CMhhEoaUM/vlbDz4NPjufhn5CGd/DkLyOGCM xiTNGU0TEscBiTgNUmLk4HbjOM1okrvjEDlO8oAyd5pllOf90zShYeQHhzmNQ3ccJzRh/eMgppx7 0XGa0yh1x6D17nESUz/rmOeUrY4xcATmTPxoEDzI/WgQPGBeNE8ZzbLO4oyGvH8cZzQL/egQHOJO -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
3
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

13 years, 3 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

13 years, 3 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

13 years, 3 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

13 years, 3 months

4
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2011