October 2011 - seam-issues - Jboss List Archives

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

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

12 years, 7 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

12 years, 7 months

3
2
0 / 0

[JBoss JIRA] (SEAMMAIL-24) Sendmail example integration tests broken

by Marek Schmidt (Created) (JIRA)

Sendmail example integration tests broken ----------------------------------------- Key: SEAMMAIL-24 URL: https://issues.jboss.org/browse/SEAMMAIL-24 Project: Seam Mail Issue Type: Bug Affects Versions: 3.1.0.Beta3 Reporter: Marek Schmidt Assignee: Marek Schmidt Fix For: 3.1.0.CR1 org.jboss.seam.mail.MailMessageTest: Could not load class from archive test.war org.jboss.seam.mail.FreeMarkerMailMessageTest: Could not load class from archive test.war org.jboss.seam.mail.VelocityMailMessageTest: Could not load class from archive test.war Caused by: java.lang.ClassNotFoundException: org.jboss.seam.solder.reflection.annotated.Parameter$MethodParameter need to properly shrinkwrap correct dependencies -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

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

12 years, 7 months

4
6
0 / 0

[JBoss JIRA] (SEAMFACES-212) Query parameters are not well rebuild in requested url after login redirection

by Jérémy Bogatirsky (Created) (JIRA)

Query parameters are not well rebuild in requested url after login redirection ------------------------------------------------------------------------------ Key: SEAMFACES-212 URL: https://issues.jboss.org/browse/SEAMFACES-212 Project: Seam Faces Issue Type: Bug Components: Security Affects Versions: 3.0.2 Environment: JBoss 6 Seam 3.0.0.Final with Seam Faces 3.0.2.Final Reporter: Jérémy Bogatirsky When requesting a login protected URL containing query parameters, the preLoginEvent observer (org.jboss.seam.faces.security.LoginListener.observePreLoginEvent(@Observes PreLoginEvent event)) rebuild the requested URL using a question mark ('?') to separate all query parameters and not only to separate the first one from the URL. A boolean (initialized to true) is used to identify when the first parameter has been treated but is never set to false, leading to not use th '&' to separate the following query parameters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
1
0 / 0

[JBoss JIRA] (SOLDER-286) AnnotationInvocationHandler not Serializable

by Vinicius Carvalho (Created) (JIRA)

AnnotationInvocationHandler not Serializable -------------------------------------------- Key: SOLDER-286 URL: https://issues.jboss.org/browse/SOLDER-286 Project: Seam Solder Issue Type: Bug Components: Core Affects Versions: 3.1.0.Beta1, 3.0.0.Final Reporter: Vinicius Carvalho I was trying to put an annotation qualifier and send over the wire. Got an exception. Here's a simple test case that would reproduce the error: @Test public void solderSerialization() throws Exception{ HashMap<String, Object> values = new HashMap<String, Object>(); AnnotationInstanceProvider provider = new AnnotationInstanceProvider(); values.put("types", SerializationTest.class); ClusterAware aw = provider.get(ClusterAware.class, values); ObjectOutputStream out = new ObjectOutputStream(new ByteArrayOutputStream()); out.writeObject(aw); } And the exception: java.io.NotSerializableException: org.jboss.seam.solder.reflection.AnnotationInvocationHandler$SerializationProxy at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) at com.ericsson.one.services.one.cluster.SerializationTest.solderSerialization(SerializationTest.java:28) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
2
0 / 0

[JBoss JIRA] (SEAMVALIDATE-23) validation-helloworld works randomly on GlassFish

by Jozef Hartinger (Created) (JIRA)

validation-helloworld works randomly on GlassFish ------------------------------------------------- Key: SEAMVALIDATE-23 URL: https://issues.jboss.org/browse/SEAMVALIDATE-23 Project: Seam Validation Issue Type: Bug Affects Versions: 3.1.0.Beta3 Reporter: Jozef Hartinger Assignee: Gunnar Morling The validation works only sometimes. Redeployment of the application usually helps. This is most likely a consequence of http://java.net/jira/browse/GLASSFISH-17184 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 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 October 2011