August 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMREMOTING-1) Use JSF2 and Servlet 3 features where applicable

by Nicklas Karlsson (JIRA)

Use JSF2 and Servlet 3 features where applicable ------------------------------------------------ Key: SEAMREMOTING-1 URL: https://jira.jboss.org/jira/browse/SEAMREMOTING-1 Project: Seam Remoting Issue Type: Feature Request Reporter: Nicklas Karlsson Assignee: Shane Bryzak Priority: Minor annotation based servlet registration etc. -- 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

15 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBSEAM-4685) Unexpected web service response on JBoss 6.0.0 M4

by Jozef Hartinger (JIRA)

Unexpected web service response on JBoss 6.0.0 M4 ------------------------------------------------- Key: JBSEAM-4685 URL: https://jira.jboss.org/browse/JBSEAM-4685 Project: Seam Issue Type: Bug Components: WS Affects Versions: 2.2.1.CR2 Reporter: Jozef Hartinger While the login service should return the following response: <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header><seam:conversationId xmlns:seam='http://www.jboss.org/seam/webservice'>3</seam:conversationId></env:Header><env:Body><ns2:loginResponse xmlns:ns2="http://seambay.example.seam.jboss.org/"><return>true</return></ns2:loginResponse></env:Body></env:Envelope> on JBoss 6.0.0 M4, the service returns: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns1:loginResponse xmlns:ns1="http://seambay.example.seam.jboss.org/"><return>true</return></ns1:loginResponse></soap:Body></soap:Envelope> Note the missing conversationId value. -- 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

15 years, 2 months

2
10
0 / 0

[JBoss JIRA] Created: (JBSEAM-4661) Chatroom example doesn't work as expected on JBossAS 6 M3

by Martin Gencur (JIRA)

Chatroom example doesn't work as expected on JBossAS 6 M3 --------------------------------------------------------- Key: JBSEAM-4661 URL: https://jira.jboss.org/browse/JBSEAM-4661 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.2.1.CR1 Environment: JBossAS M3 (jboss-as-distribution-6.0.0.20100429-M3) Reporter: Martin Gencur Nothing happens after entering name and clicking on "Connect" button in chatroom example. JBossAS log shows the following error: 16:39:19,143 ERROR [org.jboss.seam.remoting.messaging.SubscriptionRegistry] java.lang.NullPointerException 16:39:19,151 ERROR [org.jboss.seam.remoting.Remoting] Error: java.lang.NullPointerException at org.jboss.seam.remoting.messaging.SubscriptionRequest.marshal(SubscriptionRequest.java:31) [:2.2.1-SNAPSHOT] at org.jboss.seam.remoting.SubscriptionHandler.marshalResponse(SubscriptionHandler.java:107) [:2.2.1-SNAPSHOT] at org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:96) [:2.2.1-SNAPSHOT] at org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111) [:2.2.1-SNAPSHOT] at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) [:2.2.1-SNAPSHOT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Beta2] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:336) [:6.0.0.20100429-M3] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.20100429-M3] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) [:2.2.1-SNAPSHOT] at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [:2.2.1-SNAPSHOT] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.1-SNAPSHOT] at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) [:2.2.1-SNAPSHOT] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.1-SNAPSHOT] at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) [:2.2.1-SNAPSHOT] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.1-SNAPSHOT] at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) [:2.2.1-SNAPSHOT] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.1-SNAPSHOT] at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) [:2.2.1-SNAPSHOT] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [:2.2.1-SNAPSHOT] at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [:2.2.1-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.0.0.20100429-M3] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.20100429-M3] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:293) [:6.0.0.20100429-M3] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.20100429-M3] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183) [:6.0.0.20100429-M3] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95) [:6.0.0.20100429-M3] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) [:6.0.0.20100429-M3] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) [:6.0.0.20100429-M3] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.20100429-M3] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.20100429-M3] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.20100429-M3] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.20100429-M3] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [:6.0.0.20100429-M3] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:872) [:6.0.0.20100429-M3] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [:6.0.0.20100429-M3] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.20100429-M3] at java.lang.Thread.run(Thread.java:619) [:1.6.0_16] -- 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

15 years, 2 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3917) NPE in Image.getImage() for images with unsupported content type

by Daniel Wiell (JIRA)

NPE in Image.getImage() for images with unsupported content type ---------------------------------------------------------------- Key: JBSEAM-3917 URL: https://jira.jboss.org/jira/browse/JBSEAM-3917 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Reporter: Daniel Wiell Image.readImage(InputStream) sets contentType to null if the type of the image is unknown (say a bmp). When invoking Image.getImage(), a NPE is thrown: java.lang.NullPointerException at org.jboss.seam.ui.graphicImage.Image.getImage(Image.java:154) ImageIO.write(bufferedImage, getContentType().getImageFormatName(), outputStream); getContentType() returns null. -- 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

15 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-4) Render/Send mail from non-web requests (e.g. MDB, EJB async, JMS queue, EJB remote invocation)

by Pete Muir (JIRA)

Render/Send mail from non-web requests (e.g. MDB, EJB async, JMS queue, EJB remote invocation) ---------------------------------------------------------------------------------------------- Key: SEAMMAIL-4 URL: https://jira.jboss.org/browse/SEAMMAIL-4 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

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBSEAM-4643) Add built-in primefaces option to seam-gen

by sertac anadollu (JIRA)

Add built-in primefaces option to seam-gen ------------------------------------------ Key: JBSEAM-4643 URL: https://jira.jboss.org/jira/browse/JBSEAM-4643 Project: Seam Issue Type: Feature Request Components: JSF Integration Affects Versions: 2.2.1.CR2 Reporter: sertac anadollu Fix For: 2.2.1.CR2 Primefaces is the one of most popular open source jsf component libraries and day by day it is widely used in seam based projects. Some advantages of this library are its simplicity, natural compatibility with other libraries, high performance, having interesting components, simple setup, good documentation, development team behind it and licensed under Apache License V2. I used it many seam based projects and I am very happy for being with it. It is very nice to see primefaces option in the seam-gen setup. -- 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

15 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-1) Handle errors from sending mail

by Pete Muir (JIRA)

Handle errors from sending mail ------------------------------- Key: SEAMMAIL-1 URL: https://jira.jboss.org/browse/SEAMMAIL-1 Project: Seam Mail Issue Type: Feature Request Reporter: Pete Muir > Another thing the current implementation does is render and send at the same > time. This is a bad idea as well. You'd generally want to save the rendered? > email, and retry on send errors. Email has two types of errors, those that the MTA will automatically retry for, and those that cause bounces. If you are referring to bounces, how do you process the bounces? -- 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

15 years, 3 months

3
10
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-5) Save rendered Mail message to JPA

by Pete Muir (JIRA)

Save rendered Mail message to JPA --------------------------------- Key: SEAMMAIL-5 URL: https://jira.jboss.org/browse/SEAMMAIL-5 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

15 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-7) Consider how users can edit mail templates

by Pete Muir (JIRA)

Consider how users can edit mail templates ------------------------------------------ Key: SEAMMAIL-7 URL: https://jira.jboss.org/browse/SEAMMAIL-7 Project: Seam Mail Issue Type: Feature Request Reporter: Pete Muir Apparently XML templates are too complex. -- 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

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMMAIL-2) Testing infrastructure

by Pete Muir (JIRA)

Testing infrastructure ---------------------- Key: SEAMMAIL-2 URL: https://jira.jboss.org/browse/SEAMMAIL-2 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

15 years, 3 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2010