June 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4632) Seam Reference Guide - 18.1.5. Lists - two properties called "alignment" in p:list

by Misty Stanley-Jones (JIRA)

Seam Reference Guide - 18.1.5. Lists - two properties called "alignment" in p:list ---------------------------------------------------------------------------------- Key: JBSEAM-4632 URL: https://jira.jboss.org/jira/browse/JBSEAM-4632 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.0.0.GA Reporter: Misty Stanley-Jones Fix For: 2.0.0.GA Notice "alignment" used twice for two different attributes. Attributes * alignment — The alignment of the header/footer box section. (See Section 18.1.7.2, "Alignment Values" for alignment values.) * alignment — The alignment of the list item. (See Section 18.1.7.2, "Alignment Values" for possible values.) * indentationLeft — The left indentation amount. * indentationRight — The right indentation amount. * listSymbol — Overrides the default list symbol for this list item. -- 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, 10 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4461) small typo/mistake in reference manual

by Wolfgang Schwendt (JIRA)

small typo/mistake in reference manual -------------------------------------- Key: JBSEAM-4461 URL: https://jira.jboss.org/jira/browse/JBSEAM-4461 Project: Seam Issue Type: Patch Affects Versions: 2.2.0.GA Reporter: Wolfgang Schwendt Priority: Trivial just for the sake of correctness. In the reference manual, chapter 30 (configuring seam), it must read "public interface Authenticator", not "public class Authenticator" -- 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, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-4638) In Seam mail do not recommend replacing the mail-ra.rar in JBoss 5.x

by Samuel Mendenhall (JIRA)

In Seam mail do not recommend replacing the mail-ra.rar in JBoss 5.x -------------------------------------------------------------------- Key: JBSEAM-4638 URL: https://jira.jboss.org/jira/browse/JBSEAM-4638 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.2.1.CR1 Reporter: Samuel Mendenhall Priority: Minor Fix For: 2.2.1.CR2 In http://docs.jboss.org/seam/2.2.1.CR1/reference/en-US/html_single/#d0e20986 modify "If you are using EJB then you can use a MDB (Message Driven Bean) to receive email. JBoss provides a JCA adaptor — mail-ra.rar — but the version distributed with JBoss AS has a number of limitations (and isn't bundled in some versions) therefore we recommend using the mail-ra.rar distributed with Seam (it's in the extras/ directory in the Seam bundle). mail-ra.rar should be placed in $JBOSS_HOME/server/default/deploy; if the version of JBoss AS you use already has this file, replace it." To say if using JBoss AS 5.x and above the mail-ra.rar changes are merged into JBoss AS already. On AS 4.x it is still tech preview. The changes being fixes to the limitations that the docs originally noted, there should no longer be these limitations in JBoss AS 5.x but they are still in AS 4.x Pete has said that his patches for the mail-ra.rar were all accepted into JBAS so these changes should be in the JBAS 5.x, thus the mail-ra.rar is up to par. -- 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, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-4590) Multiple war in ear - resources not isolated between wars

by Susanne Jarl (JIRA)

Multiple war in ear - resources not isolated between wars ---------------------------------------------------------- Key: JBSEAM-4590 URL: https://jira.jboss.org/jira/browse/JBSEAM-4590 Project: Seam Issue Type: Bug Affects Versions: 2.2.0.GA Environment: JBoss 5.1.0.GA, Hot deployment. JDK 1.6 Reporter: Susanne Jarl If you have a.war and b.war in an ear and try to send an email using org.jboss.seam.faces.Renderer this will only work for b.war and in a.war you will get an exception saying that the resource in b.war could not be found. So the renderer called from a.war looks for resources in b.war. Kind of the same problem with s.graphicImage, only working in b.war, and when used in a.war the exception says it is looking for resources in b.war. I use hot deployment. If I start my application with only one of the war files at the time everything works perfectly fine. These issues did not exist in version 2.0.X, they appeared in 2.1. and has been around since then although changed a little between versions. I have also tried 2.2.1. nightly build #164, since I thought that JBSEAM-4316 might solve this, but unfortunatally it did not. I have in each war a jboss-web.xml looking like this example (with of course different unique names): <jboss-web> <class-loading java2ClassLoadingCompliance="false"> <loader-repository> org.jboss.seam:archive=uniquename <loader-repository-config>java2ParentDelegation=false</loader-repository-config> </loader-repository> </class-loading> </jboss-web> jboss-app.xml looks like this: <jboss-app> <loader-repository> org.jboss.seam:archive=myapp <loader-repository-config> java2ParentDelegation=false </loader-repository-config> </loader-repository> </jboss-app> Please solve this bug until next release. Thank you! -- 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, 10 months

3
11
0 / 0

[JBoss JIRA] Created: (JBSEAM-4630) File Attachment not Visible in certain versions of AppleMail

by Cody Lerum (JIRA)

File Attachment not Visible in certain versions of AppleMail ------------------------------------------------------------ Key: JBSEAM-4630 URL: https://jira.jboss.org/jira/browse/JBSEAM-4630 Project: Seam Issue Type: Patch Components: Mail Affects Versions: 2.2.1.CR1 Reporter: Cody Lerum Assignee: Pete Muir I ran across an issue in production where a couple end users running AppleMail versions (2.1077) and (2.936) are unable to see PDF attachments to a seam mail. Upon further investigation I've created a patch that fixes the message layout of messages which have attachments. The issue is where all attachment inline and other are added to a new multipart/related attached to the root multipart/mixed. This appears to cause issues if attachments are not inline. Basically all messages start with a root multipart/mixed at the top level. >From there, if there are no inline attachments then the message body is added to the root multipart/mixed and any attachments (non-inline) are also added to the root multipart/mixed. If there are inline attachments then a multipart/related is created and added to the root multipart/mixed. The message body is added to the related as well as any inline attachments. Non inline attachments are added to the root multipart/mixed if there is a text alternative to a html body then a multipart/alternative is created and added added either to the root multipart/mixed or to the multipart/related depending on if inline attachments exist. I've tested with this current versions of Outlook, with Gmail and with current versions of AppleMail. The inline attachment shows as broken in Thunderbird, but it also shows that way in the current 2.2.0GA and 2.2.1CR1 and appears to be a bug in thunderbird. I'm going to attach a patch and a graphic so you can visualize the layout under different scenarios. -- 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, 10 months

2
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2512) Default configuration option for begins to use flushmode=MANUAL

by Jacob Orshalick (JIRA)

Default configuration option for begins to use flushmode=MANUAL --------------------------------------------------------------- Key: JBSEAM-2512 URL: http://jira.jboss.com/jira/browse/JBSEAM-2512 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.1.CR1 Reporter: Jacob Orshalick It would be nice to provide a way to globally configure the flushmode setting. Say, a way to configure begins to use flushmode=MANUAL by default. Maybe this could be configured in components.xml. This would save a lot of what is generally boilerplate configuration since this is common usage. Perhaps, I could specify: <core:manager conversation-flushmode="MANUAL" /> -- 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, 11 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3975) Load jBPM Process Def from the DB/Repo

by Burr Sutter (JIRA)

Load jBPM Process Def from the DB/Repo -------------------------------------- Key: JBSEAM-3975 URL: https://jira.jboss.org/jira/browse/JBSEAM-3975 Project: Seam Issue Type: Feature Request Components: BPM Reporter: Burr Sutter What about loading up process defs from their "normal" location, the database? jBPM has a "repository" that stores process instance state for long running processes as well as it versions the definitions, Seam should be able to load the process def not only from the .ear/classpath but also from the repo. -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-4624) Tasks example doesn't work correctly on Windows

by Jozef Hartinger (JIRA)

Tasks example doesn't work correctly on Windows ----------------------------------------------- Key: JBSEAM-4624 URL: https://jira.jboss.org/jira/browse/JBSEAM-4624 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.2.1.CR1 Environment: Microsoft Windows Server 2003 R2 Service Pack 2, Internet Explorer 8, Sun jdk1.6 Reporter: Jozef Hartinger Priority: Minor Fix For: 2.2.1.CR2 Steps to reproduce the bug: - log in, click "Resolved Tasks" link, click "Undo this Task" (green arrow), click "Tasks" link - now you should see (as it is with Linux and Firefox) "Buy a turtle" in a "Buy" section - when you click "Resolved Tasks" again, you can see that the task is still there (didn't disappear) A jbossas log doesn't show anything specific - no exception or warning message. -- 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, 11 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4039) Seam component cannot serve as a JAX-RS subresource

by Jozef Hartinger (JIRA)

Seam component cannot serve as a JAX-RS subresource --------------------------------------------------- Key: JBSEAM-4039 URL: https://jira.jboss.org/jira/browse/JBSEAM-4039 Project: Seam Issue Type: Bug Components: WS Reporter: Jozef Hartinger Assignee: Christian Bauer When Seam component is returned as a subresource, RESTEasy scans it's javassist proxy for JAX-RS annotations. It should however scan the actual component's class instead. Following snippet: @Path("/{username}/{context}") public ContextResource getContextResource(@PathParam("username")String username) { ... return (ContextResource) Component.getInstance("contextResource"); } causes LoggableException with message: Subresource for target class has no jax-rs annotations.: org.jboss.seam.example.rest.resource.ContextResource_$$_javassist_seam_9 -- 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, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JBSEAM-4642) Contextual instance are not available via ResteasyProviderFactory.getContextData()

by Jozef Hartinger (JIRA)

Contextual instance are not available via ResteasyProviderFactory.getContextData() ---------------------------------------------------------------------------------- Key: JBSEAM-4642 URL: https://jira.jboss.org/jira/browse/JBSEAM-4642 Project: Seam Issue Type: Bug Components: WS Affects Versions: 2.2.1.CR1 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 2.2.1.CR2 Make Providers, Registry, Dispatcher available via ResteasyProviderFactory.getContextData() calls. This is set up in ResteasyDeployment.start() in plain RESTEasy. -- 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, 11 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2010