May 2012 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMSECURITY-86) Scheme setting for pages in @ViewConfig

by Bill Elliot (JIRA)

Scheme setting for pages in @ViewConfig --------------------------------------- Key: SEAMSECURITY-86 URL: https://issues.jboss.org/browse/SEAMSECURITY-86 Project: Seam Security Issue Type: Feature Request Affects Versions: 3.0.0.Final Reporter: Bill Elliot Is there a way in Seam 3 to do like in the Page definitions of Seam 2 to specify the Scheme (HTTP/HTTPS) to use for a specific page? I need to be able to place the login and password changing screens into HTTPS for increased security and best practices. This could likely be done in the Pages definition under a @ViewConfig. Possibly adding a new annotation @Scheme("HTTPS"). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

4
5
0 / 0

[JBoss JIRA] (SEAMINTL-70) Document usage of BundleTemplateMessage/TemplateMessage

by Gerald Turner (Created) (JIRA)

Document usage of BundleTemplateMessage/TemplateMessage ------------------------------------------------------- Key: SEAMINTL-70 URL: https://issues.jboss.org/browse/SEAMINTL-70 Project: Seam International Issue Type: Feature Request Components: Messages Affects Versions: 3.1.0.Beta3 Reporter: Gerald Turner Assignee: Ken Finnigan Priority: Optional As a user, the current documentation is sufficient for severity+text messages, however on closer inspection of the Message class, I see that detail and targets properties are available, much like FacesMessage. I dug around the seam-international source and experimented with a bean having fields/method like the following: @Inject private Messages messages; @Inject private transient TemplateMessage message; public void doSometing() { messages.add(message.level(Level.WARN).text("Text {0}, {1}, {2}").textParams('a', 'b', 'c').detail("Detail {0}, {1}, {2}").detailParams(1, 2, 3).targets("message").build()); messages.add(message.level(Level.FATAL).text("Fatality!").targets("message").build()); } This works. A few caveats: * TemplateMessage field has to be marked transient, otherwise get WELD error during deployment about Serializable bean having non-Serializable field. * Make sure to call add(Message) signature (invoke build()) instead of add(MessageBuilder), otherwise only the most recent message is added. * doSomething method is not reentrant/thread-safe because of the builder. I'd prefer to use Messages instead of the builders, perhaps have a methods like info(String text, String details, String targets, Object... args), however that gets ugly with the varargs, having to cast Object[], etc. Perhaps I should stick with FacesMessages. -- 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

11 years, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (SEAMINTL-58) XML Config of Supported Locales

by Ken Finnigan (JIRA)

XML Config of Supported Locales ------------------------------- Key: SEAMINTL-58 URL: https://issues.jboss.org/browse/SEAMINTL-58 Project: Seam International Issue Type: Task Components: Locales Affects Versions: 3.0.0.Final Reporter: Ken Finnigan Assignee: Ken Finnigan Priority: Minor Go through forum post -> http://seamframework.org/Community/DefaultLocaleWithSeamIntenational#comm... to see if the supported locales can be configured easier and cleaner -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMINTL-41) Messages cannot be used in TransactionPhase.AFTER_SUCCESS

by Jozef Hartinger (JIRA)

Messages cannot be used in TransactionPhase.AFTER_SUCCESS --------------------------------------------------------- Key: SEAMINTL-41 URL: https://issues.jboss.org/browse/SEAMINTL-41 Project: Seam International Issue Type: Bug Components: Messages Affects Versions: 3.0.0.Final Reporter: Jozef Hartinger Assignee: Ken Finnigan Fix For: 3.1.0.Alpha1 I am using the Seam Booking example (https://github.com/seam/examples/tree/3.0.0.Final) After a booking is made successfully, a message similar to "You're booked to stay at the Marriott Courtyard 5 days from now. " is supposed to be displayed on the web page. The message is set in an observer method. https://github.com/seam/examples/blob/3.0.0.Final/booking/src/main/java/o... Unfortunatelly, the message is never displayed. When the event is observed during TransactionPhase.IN_PROGRESS (i.e. public void onBookingComplete(@Observes @Confirmed final Booking booking)) , the message is displayed as expected. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

10
22
0 / 0

[JBoss JIRA] Created: (SEAMINTL-7) Rewrite Messages API along the lines of JBoss Logging 3

by Ken Finnigan (JIRA)

Rewrite Messages API along the lines of JBoss Logging 3 ------------------------------------------------------- Key: SEAMINTL-7 URL: https://jira.jboss.org/browse/SEAMINTL-7 Project: Seam i18n Issue Type: Feature Request Components: Messages Affects Versions: 3.0.0.Alpha1 Reporter: Ken Finnigan Fix For: 3.0.0.Alpha2 Rewrite messages API along the lines of JBoss Logging 3 to be consistent with the logging approach once the switch from slf4j is made to JBoss Logging 3. -- 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

11 years, 11 months

7
37
0 / 0

[JBoss JIRA] Created: (SEAMINTL-59) Type Safe Message specific to a Client

by Ken Finnigan (JIRA)

Type Safe Message specific to a Client -------------------------------------- Key: SEAMINTL-59 URL: https://issues.jboss.org/browse/SEAMINTL-59 Project: Seam International Issue Type: Enhancement Components: Messages Reporter: Ken Finnigan Assignee: Ken Finnigan Support @Client on message interface injection or definition of interface method. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
3
0 / 0

[JBoss JIRA] (SEAMINTL-75) Messages#clear doesn't clear builder messages

by Lucas Ventura Carro (JIRA)

Lucas Ventura Carro created SEAMINTL-75: ------------------------------------------- Summary: Messages#clear doesn't clear builder messages Key: SEAMINTL-75 URL: https://issues.jboss.org/browse/SEAMINTL-75 Project: Seam International Issue Type: Bug Components: Messages Affects Versions: 3.1.0.Final Environment: Windows 7, 64bits, Tomcat 6 Reporter: Lucas Ventura Carro Assignee: Ken Finnigan Adding messages to {{org.jboss.seam.international.status.Messages}} (so by default {{org.jboss.seam.international.status.MessagesImpl}}) using the function with MessageBuilder argument, doesn't get cleared when calling to [Messages#clear()|http://docs.jboss.org/seam/3/international/latest/api/or...] function. -- 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

11 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMINTL-65) Update Seam Config usage

by Ken Finnigan (JIRA)

Update Seam Config usage ------------------------ Key: SEAMINTL-65 URL: https://issues.jboss.org/browse/SEAMINTL-65 Project: Seam International Issue Type: Task Affects Versions: 3.0.0.Final Reporter: Ken Finnigan Assignee: Ken Finnigan Update the integration tests and documentation on how to use Seam Config for the module. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMINTL-61) Default Type Safe Messages to use App Locale

by Ken Finnigan (JIRA)

Default Type Safe Messages to use App Locale -------------------------------------------- Key: SEAMINTL-61 URL: https://issues.jboss.org/browse/SEAMINTL-61 Project: Seam International Issue Type: Enhancement Components: Locales, Messages Reporter: Ken Finnigan Assignee: Ken Finnigan Figure out way to auto set locale on messages to default to app locale to ensure correct message bundle is retrieved. Can't set jdk locale as that would impact other apps on server -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMINTL-57) Select Message Interface by Locale

by Ken Finnigan (JIRA)

Select Message Interface by Locale ---------------------------------- Key: SEAMINTL-57 URL: https://issues.jboss.org/browse/SEAMINTL-57 Project: Seam International Issue Type: Enhancement Components: Locales, Messages Reporter: Ken Finnigan Assignee: Ken Finnigan If a developer Injects a message interface and then does BlahMessages.helloWorld("Brian"); how does that become localized to either the App locale or the Client locale? For App locale, could specify developer adds @Locale('fr') to message interface injection point For Client locale, above approach doesn't work. Need to have a wrapper class around the various locale specific message interfaces that the developer would inject to use, and then when called would call the appropriate locale specific version. Something like: class MessagesWrapper<BlahMessage> {} with a way to specify which locales are supported in that wrapper, so it knows possible locale specific interfaces it would require, and then it uses the @Client @Locale to retrieve the correct localized message -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2012