July 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMPERSIST-44) remove annotation @Remove from o.j.st.TransactionManagerSynchronizations

by Denis Forveille (JIRA)

remove annotation @Remove from o.j.st.TransactionManagerSynchronizations ------------------------------------------------------------------------ Key: SEAMPERSIST-44 URL: https://issues.jboss.org/browse/SEAMPERSIST-44 Project: Seam Persistence Issue Type: Bug Affects Versions: 3.0.0.CR3 Environment: WebSphere v8 beta Reporter: Denis Forveille org.jboss.seam.transaction.TransactionManagerSynchronizations contains an annotaion @Remove but this class in not a SFSB.. This causes the following exception in WebShere v8 beta {noformat}An exception occurred while validating an annotation: com.ibm.wsspi.amm.validate.ValidationException: CWWAM2102E: The @Remove annotation is defined for bean org.jboss.seam.transaction.TransactionManagerSynchronizations; however, it is only applicable to a stateful session bean class. {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-4822) MultipartRequestImpl incorrect parse filename with semicolon

by Krzysztof Borgul (JIRA)

MultipartRequestImpl incorrect parse filename with semicolon ------------------------------------------------------------ Key: JBSEAM-4822 URL: https://issues.jboss.org/browse/JBSEAM-4822 Project: Seam 2 Issue Type: Bug Affects Versions: 2.2.0.GA Environment: Windows XP Reporter: Krzysztof Borgul Priority: Minor When I uploaded file with semicolon in name, org.jboss.seam.web.MultipartRequestImpl.parseParams incorrect parse header line: Content-Disposition: form-data; name="form:fileUpload"; filename="x;a.txt" It was split on four parts: Content-Disposition: form-data name="form:fileUpload" filename="x a.txt" ,but should be Content-Disposition: form-data name="form:fileUpload" filename="x;a.txt" The problem is in the regular expression used as split method parameter. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFACES-47) UIInputContainer keeps invalid state too long

by Nicklas Karlsson (JIRA)

UIInputContainer keeps invalid state too long --------------------------------------------- Key: SEAMFACES-47 URL: https://jira.jboss.org/browse/SEAMFACES-47 Project: Seam Faces Issue Type: Bug Components: UI Components Affects Versions: 3.0.0.Alpha3 Reporter: Nicklas Karlsson Given a <p:input> <h:inputText value="#{credentials.username}" /> </p:input> <p:input> <h:inputText value="#{credentials.password}" /> </p:input> <h:commandButton value="Login" action="#{credentials.login}" /> and a @Model public class Credentials { @NotNull private String username; public String getUsername() { return username; } public void setUsername(String username) { this.username = username; } @NotNull public String getPassword() { return password; } public void setPassword(String password) { this.password = password; } private String password; public void login() { System.out.println(username); System.out.println(password); } } with <context-param> <param-name>javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL</param-name> <param-value>true</param-value> </context-param> and a modified input.xhtml that outputs #{cc.attrs.invalid} you submit a blank form and get "true" and correct message for both fields, then you enter a value in the second field and re-submit and the messages are correct but both fields still show true for the invalid attribute output (making it impossible to use the attr for rendered attributes if e.g. an error image) -- 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, 6 months

5
4
0 / 0

[JBoss JIRA] Created: (SEAMJCR-12) API for injecting Credentials

by John Ament (JIRA)

API for injecting Credentials ----------------------------- Key: SEAMJCR-12 URL: https://issues.jboss.org/browse/SEAMJCR-12 Project: Seam JCR Issue Type: Feature Request Components: CDI & Injection API Reporter: John Ament Assignee: John Ament Fix For: 3.0.0.Alpha2 We should support injecting credentials to the backend frameworks when producing sessions. The requirement should be conditional and should end up scoped to the same context as is being injected into. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMJMS-33) Documentation issues

by Jozef Hartinger (JIRA)

Documentation issues -------------------- Key: SEAMJMS-33 URL: https://issues.jboss.org/browse/SEAMJMS-33 Project: Seam JMS Issue Type: Bug Components: Documentation Affects Versions: 3.0.0.Beta2 Reporter: Jozef Hartinger Priority: Minor Fix For: 3.0.0.CR1 * Java syntax highlighting is not enabled in code samples (affects the entire document) * Code formating (indentation) is broken in some of the code samples * Section 1.2 ** s/Message Received/Message Receiver ** s/Further,/Furthermore, * Section 3.1 ** "now" is not necessary in the very first sentence * Section 3.1.1 ** "The injection of resources that {color:red}are{color} themselves {color:red}a{color} javax.jms.Destination or require one needs a hint:" This sentence is gramatically incorrect ** s/annotatation/annotation * Section 4 ** The sections of this chapter will describe how to achieve both. - use present tense * Section 4.1 ** Let's let a little configuration do the work for us. - this is gramatically incorrect -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (SEAMJMS-36) jms-statuswatcher example broken

by Jozef Hartinger (JIRA)

jms-statuswatcher example broken -------------------------------- Key: SEAMJMS-36 URL: https://issues.jboss.org/browse/SEAMJMS-36 Project: Seam JMS Issue Type: Bug Affects Versions: 3.0.0.Beta2 Reporter: Jozef Hartinger Priority: Blocker Fix For: 3.0.0.CR1 Firstly, the ReceivingClient class needs to be updated to follow recent API changes: @Durable qualifier needs to be added to the following injection point definition: @Inject @Durable private DurableMessageManager dmm; Without this change, the example fails to deploy with UnsatisfiedResolutionException. Even with this change, the example does not work as expected: 1.) Deploy the application 2.) Open http://localhost:8080/jms-statuswatcher/watchstatus.jsf 3.) Check "Follow all" 4.) Open http://localhost:8080/jms-statuswatcher/sendstatus.jsf and send a status The status is never displayed on the watchstatus page. Using the "history" link does not help and clicking "receive" causes an exception since the ReceivingClient.receive() method is commented out for some reason -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMJMS-44) MessageManagers should support configurable JMS Sessions

by John Ament (JIRA)

MessageManagers should support configurable JMS Sessions -------------------------------------------------------- Key: SEAMJMS-44 URL: https://issues.jboss.org/browse/SEAMJMS-44 Project: Seam JMS Issue Type: Feature Request Affects Versions: 3.0.0.Beta2 Reporter: John Ament Assignee: John Ament Fix For: 3.0.0.CR1 The current implementation of MessageManager does not support configurable JMS sessions, it uses a hardcoded transacted = false and auto acknowledge. If we convert it to use a standalone producer, then it becomes more user oriented. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMJMS-46) Allow for a default session configuration

by John Ament (JIRA)

Allow for a default session configuration ----------------------------------------- Key: SEAMJMS-46 URL: https://issues.jboss.org/browse/SEAMJMS-46 Project: Seam JMS Issue Type: Feature Request Reporter: John Ament Assignee: John Ament Fix For: 3.0.0.CR1 Create a default configuration option - e.g. @JmsDefault(type="session") SessionConfiguration that includes the transacted and acknowledge mode of a session. This will be the default used when working with sessions, specifically the message manager interface. If none found, will continue to use false/auto. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMJMS-45) Support a message payload type that can support all properties in a JMS message, but not depend on a JMS session.

by John Ament (JIRA)

Support a message payload type that can support all properties in a JMS message, but not depend on a JMS session. ----------------------------------------------------------------------------------------------------------------- Key: SEAMJMS-45 URL: https://issues.jboss.org/browse/SEAMJMS-45 Project: Seam JMS Issue Type: Feature Request Reporter: John Ament Assignee: John Ament Fix For: 3.0.0.CR1 JMS relies on a JMS session to create messages. However, a session may not be available in the client caller in a fired event, and it may be a different session that sends it. Therefore, we will provide a custom message type that encapsulated necessary extra functionality, as well as an observer method that forwards the fired message to a destination. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-44) security-openid-op - ambiguous bean names

by Jozef Hartinger (JIRA)

security-openid-op - ambiguous bean names ----------------------------------------- Key: SEAMSECURITY-44 URL: https://issues.jboss.org/browse/SEAMSECURITY-44 Project: Seam Security Issue Type: Bug Environment: GlassFish 3.1 + Weld SNAPSHOT Reporter: Jozef Hartinger [#|2011-03-24T10:57:47.967+0100|SEVERE|glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=67;_ThreadName=Thread-1;|Exception while loading the app : WELD-001414 Bean name is ambiguous. Name identity resolves to beans [Managed Bean [class org.jboss.seam.security.examples.openid.Identity] with qualifiers [@Any @Default @Named], Managed Bean [class org.jboss.seam.security.IdentityImpl] with qualifiers [@Any @Default @Named]] org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name is ambiguous. Name identity resolves to beans [Managed Bean [class org.jboss.seam.security.examples.openid.Identity] with qualifiers [@Any @Default @Named], Managed Bean [class org.jboss.seam.security.IdentityImpl] with qualifiers [@Any @Default @Named]] at org.jboss.weld.bootstrap.Validator.validateBeanNames(Validator.java:480) at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:376) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:396) at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:190) at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:128) at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:298) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:370) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:355) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:370) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1067) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:96) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1247) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235) at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:465) at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:222) at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:168) at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:234) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59) at com.sun.grizzly.ContextTask.run(ContextTask.java:71) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513) at java.lang.Thread.run(Thread.java:662) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2011