July 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMSECURITY-30) Create example to demonstrate rule-based permissions

by Shane Bryzak (JIRA)

Create example to demonstrate rule-based permissions ---------------------------------------------------- Key: SEAMSECURITY-30 URL: https://issues.jboss.org/browse/SEAMSECURITY-30 Project: Seam Security Issue Type: Task Reporter: Shane Bryzak Assignee: Shane Bryzak Fix For: 3.0.0.Beta2 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-78) Typos in documentation

by Jozef Hartinger (JIRA)

Typos in documentation ---------------------- Key: SEAMSECURITY-78 URL: https://issues.jboss.org/browse/SEAMSECURITY-78 Project: Seam Security Issue Type: Bug Affects Versions: 3.0.0.Final Reporter: Jozef Hartinger Priority: Minor Fix For: 3.1.0.Final Section 5.2.3 * CustomeOpenIdProvider * Coogle -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
3
0 / 0

[JBoss JIRA] Created: (SEAMXML-34) Create an example(s) demonstrating config features

by Ondrej Skutka (JIRA)

Create an example(s) demonstrating config features -------------------------------------------------- Key: SEAMXML-34 URL: https://issues.jboss.org/browse/SEAMXML-34 Project: Seam Config Issue Type: Feature Request Reporter: Ondrej Skutka Fix For: 3.0.0.Final Create an example(s) demonstrating config features or modify existing one(s): - Inline bean declarations - Configuring methods - Configuring bean constructor - Overriding type of injection point -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

6
9
0 / 0

[JBoss JIRA] Created: (SEAMSERVLET-28) Integrate Catch with *EventBridge* classes

by Jason Porter (JIRA)

Integrate Catch with *EventBridge* classes ------------------------------------------ Key: SEAMSERVLET-28 URL: https://issues.jboss.org/browse/SEAMSERVLET-28 Project: Seam Servlet Issue Type: Enhancement Components: Catch Integration Affects Versions: 3.0.0.Beta1 Reporter: Jason Porter None of the EventBridge classes catch exceptions to pass to Seam Catch, thus the following code does not invoke any exception handlers: {code} public void initial(@Observes @Path("NullPointer") @Initialized final HttpServletRequestContext ctx) { throw new NullPointerException(); } {code} I would expect the NPE to be passed to Catch for exception handling. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

5
9
0 / 0

[JBoss JIRA] Created: (SOLDER-98) Documentation issues

by Martin Gencur (JIRA)

Documentation issues -------------------- Key: SOLDER-98 URL: https://issues.jboss.org/browse/SOLDER-98 Project: Seam Solder Issue Type: Bug Components: Documentation Affects Versions: 3.0.0.Final Reporter: Martin Gencur Priority: Minor Fix For: Future 1) Introduction - question marks links ("???") pointing nowhere [only in Seam 3 distribution bundle] 2) Chapter 6. Getting Started -> Tip -> "Maven user-defined property" link pointing nowhere 3) 7.1.2. @Requires -> "Note" contains "The ProcessAnnotatedType container lifecycle event will be called for vetoed types." where the word "vetoed" should be "required", in fact 4) TYPO -> 7.5. @FullyQualified bean names -> "This behavior aligns is with the needs of"... (the "is" word shouldn't be there IMHO) 5) TYPO -> 11.1. JBoss Logging: The foundation -> "JBoss Logging has is parallel support" (the "is" should be "its" IMHO) 6) TYPO -> 11.3. Typed loggers -> "If injecting a typed logger seems to "enterprisy" to you" ("to" should be "too") 7) TYPO -> 1.6.2. Including the implementation classes in Arquillian tests -> "Otherwise, you may can an exception like:" 8) section "Chapter 17. Default Beans" has probably wrong formatting of the last code snippet of this subchapter (the one containing @DefaultBean(Cache.class)) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

5
7
0 / 0

[JBoss JIRA] Created: (SEAMSERVLET-40) Typos in documentation

by Jozef Hartinger (JIRA)

Typos in documentation ---------------------- Key: SEAMSERVLET-40 URL: https://issues.jboss.org/browse/SEAMSERVLET-40 Project: Seam Servlet Issue Type: Bug Components: Documentation Affects Versions: 3.0.0.Final Reporter: Jozef Hartinger Priority: Minor Fix For: 3.0.1.Beta1 * qualifers * qualifer * safetly * intances * inadvertantly -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (SEAMREST-44) Deployment fails on JBoss AS 7

by Jozef Hartinger (JIRA)

Deployment fails on JBoss AS 7 ------------------------------ Key: SEAMREST-44 URL: https://issues.jboss.org/browse/SEAMREST-44 Project: Seam REST Issue Type: Bug Components: Client Affects Versions: 3.0.0.Final Environment: JBoss AS 7.0.0.Beta4-SNAPSHOT Reporter: Jozef Hartinger Assignee: Jozef Hartinger Priority: Blocker Fix For: 3.1.0.Alpha1 08:16:49,123 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."rest-exceptions.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."rest-exceptions.war".WeldService: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [ClientExecutor] with qualifiers [@Default] at injection point [[parameter 2] of [method] @Produces @RestClient public org.jboss.seam.rest.client.RestClientProducer.produceClientRequest(InjectionPoint, ClientExecutor)] at org.jboss.as.weld.services.WeldService.start(WeldService.java:96) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [ClientExecutor] with qualifiers [@Default] at injection point [[parameter 2] of [method] @Produces @RestClient public org.jboss.seam.rest.client.RestClientProducer.produceClientRequest(InjectionPoint, ClientExecutor)] at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:270) at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:106) at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:129) at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:351) at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:336) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:396) at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82) at org.jboss.as.weld.services.WeldService.start(WeldService.java:89) ... 4 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-40) Model example broken on AS7: Could not find TransactionManager in JNDI

by Marek Schmidt (JIRA)

Model example broken on AS7: Could not find TransactionManager in JNDI ---------------------------------------------------------------------- Key: SEAMREMOTING-40 URL: https://issues.jboss.org/browse/SEAMREMOTING-40 Project: Seam Remoting Issue Type: Bug Environment: Seam Remoting 3.0.1-SNAPSHOT JBoss AS 7.1.0-Alpha Firefox 3.6.18 Reporter: Marek Schmidt Assignee: Shane Bryzak Fix For: 3.1.0.Final Seam Remoting Model example is broken on AS7, cannot modify any values nor create new persons: The following log from attempting to create a new person, notice the "RuntimeException: Could not find TransactionManager in JNDI" {quote} Fri Jul 15 2011 15:37:37 GMT+0200 (CET): Request packet: <envelope><header><context><callId>1</callId></context></header><body><model operation="fetch"><action><target>org.jboss.seam.remoting.examples.model.PersonAction</target><method>createPerson</method></action><bean alias="person"><name>org.jboss.seam.remoting.examples.model.PersonAction</name><property>person</property></bean></model></body></envelope> Fri Jul 15 2011 15:37:37 GMT+0200 (CET): Response packet: <envelope><header><context><conversationId>1</conversationId><callId>1</callId></context></header><body><model id="3fbca98e-a040-48c4-8d21-74caef019093"><value alias="person"><ref id="0"/></value><refs><ref id="0"><bean type="org.jboss.seam.remoting.examples.model.Person"><member name="dateOfBirth"><null/></member><member name="lastName"><null/></member><member name="personId"><null/></member><member name="addresses"><bag></bag></member><member name="firstName"><null/></member></bean></ref></refs></model></body></envelope> Fri Jul 15 2011 15:37:46 GMT+0200 (CET): Request packet: <envelope><header><context><callId>2</callId><conversationId>1</conversationId></context></header><body><model id="3fbca98e-a040-48c4-8d21-74caef019093" operation="apply"><action><target>org.jboss.seam.remoting.examples.model.PersonAction</target><method>savePerson</method></action><delta><changeset refid="0"><member name="dateOfBirth"><date>19840101000000000</date></member><member name="lastName"><str>Doe</str></member><member name="firstName"><str>John</str></member></changeset></delta></model></body></envelope> Fri Jul 15 2011 15:37:46 GMT+0200 (CET): Response packet: <envelope><body><exception><message><str>java.lang.RuntimeException%3A%20java.lang.RuntimeException%3A%20Could%20not%20find%20TransactionManager%20in%20JNDI</str></message></exception></body></envelope> {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-23) Support global exception handler

by Jozef Hartinger (JIRA)

Support global exception handler -------------------------------- Key: SEAMREMOTING-23 URL: https://issues.jboss.org/browse/SEAMREMOTING-23 Project: Seam Remoting Issue Type: Feature Request Affects Versions: 3.0.0.Beta2 Reporter: Jozef Hartinger Fix For: 3.0.0.CR1 Besides allowing a specific exception handler to be associated with every method invocation, it would be nice to provide a way of registering a global exception handler i.e. Seam.globalExceptionHandler = function() { ... } This would most often be used to inform an end user that an unexpected exception occured. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-5) Add messages support for Remoting

by Shane Bryzak (JIRA)

Add messages support for Remoting --------------------------------- Key: SEAMREMOTING-5 URL: https://jira.jboss.org/browse/SEAMREMOTING-5 Project: Seam Remoting Issue Type: Feature Request Reporter: Shane Bryzak We need to add support for adding status messages. Any messages generated during a request will need to go into the context of the response packet, where they can then be accessed by the client. -- 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

14 years, 5 months

5
9
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 July 2011