April 2011 - seam-issues - Jboss List Archives

[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, 2 months

4
9
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

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

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

13 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-20) Update code formatting to community formatting rules

by Jason Porter (JIRA)

Update code formatting to community formatting rules ---------------------------------------------------- Key: SEAMMAIL-20 URL: https://issues.jboss.org/browse/SEAMMAIL-20 Project: Seam Mail Issue Type: Task Reporter: Jason Porter There are some classes (or perhaps all classes) which need to be updated to the new code formatting guidelines, please see https://github.com/seam/build/blob/master/formatting.README for more information -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-11) root pom.xml is not correct regarding distribution profile

by Martin Gencur (JIRA)

root pom.xml is not correct regarding distribution profile ---------------------------------------------------------- Key: SEAMMAIL-11 URL: https://issues.jboss.org/browse/SEAMMAIL-11 Project: Seam Mail Issue Type: Bug Reporter: Martin Gencur Fix For: 3.0.0.Beta1 The root pom.xml should contain corrent submodule definition in "distribution" profile. There is a <module>examples/sendmail</module> but should be <module>examples/seam-mail-examples-sendmail</module> instead. Thus, the distribution build is failing. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-6) Ensure exception handling is well tested

by Pete Muir (JIRA)

Ensure exception handling is well tested ---------------------------------------- Key: SEAMMAIL-6 URL: https://jira.jboss.org/browse/SEAMMAIL-6 Project: Seam Mail Issue Type: Feature Request Reporter: Pete Muir -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1279) use ExceptionFilter in Remoting

by Keith Naas (JIRA)

use ExceptionFilter in Remoting ------------------------------- Key: JBSEAM-1279 URL: http://jira.jboss.com/jira/browse/JBSEAM-1279 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Affects Versions: 1.2.1.GA Reporter: Keith Naas Assigned To: Shane Bryzak Currently, the Remoting resource class swallows all exceptions. Because of this, it is not possible to gracefully handle security restrictions in WebRemote methods from the client. Two ideas: # Simply bubble the Exception all the way up through the ResourceServlet. If the ResourceServlet throws the exception, the ExceptionFilter should pick up on it. The XHR would then receive the proper error code as defined in the pages.xml and could properly redirect the user to the correct login page. # Have the ResourceServlet trap for NotLoggedInException's or NotAuthorizedException's and return the respective HTTP status code. The XHR would then receive the error code and be able to redirect the user to the correct login page. -- 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

13 years, 2 months

5
12
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-17) Separate core and client sub-modules within remoting project

by Shane Bryzak (JIRA)

Separate core and client sub-modules within remoting project ------------------------------------------------------------ Key: SEAMREMOTING-17 URL: https://issues.jboss.org/browse/SEAMREMOTING-17 Project: Seam Remoting Issue Type: Task Reporter: Shane Bryzak Assignee: Shane Bryzak Fix For: 3.0.0.CR1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3188) ConcurrentModificationException on flush of ServerConversationContext

by Sanne Grinovero (JIRA)

ConcurrentModificationException on flush of ServerConversationContext --------------------------------------------------------------------- Key: JBSEAM-3188 URL: https://jira.jboss.org/jira/browse/JBSEAM-3188 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.3.CR1 Environment: 2.0.3.CR1, JBoss 4.2.2, JDK 5 Reporter: Sanne Grinovero As confirmed by other people on the forum at http://seamframework.org/Community/ConcurrentModificationExceptionAfterPr... It is possible for ServerConversationContext to iterate on an EntrySet which is modified in the iteration block. I couldn't understand exactly in which scenarios it happens, but it's easy to patch the code to iterate on a copy instead (I'll attach the patch). I can't say if it's correct to make a copy, or if you should actually avoid the changes. -- 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
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2011