[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
13 years, 2 months
[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
13 years, 2 months
[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
13 years, 2 months
[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
13 years, 2 months
[JBoss JIRA] Created: (SEAMMAIL-17) Test cases fails and errors
by Marek Smigielski (JIRA)
Test cases fails and errors
---------------------------
Key: SEAMMAIL-17
URL: https://issues.jboss.org/browse/SEAMMAIL-17
Project: Seam Mail
Issue Type: Bug
Reporter: Marek Smigielski
1.testTextMailMessage
junit.framework.AssertionFailedError: Didn't receive the expected amount of messages. Expected 1 got 0
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at org.jboss.seam.mail.MailMessageTest.testTextMailMessage(MailMessageTest.java:131)
2. template.html.vm resource not mapped correctly
3. testVelocityTextMailMessage
junit.framework.AssertionFailedError: Didn't receive the expected amount of messages. Expected 1 got 0
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at org.jboss.seam.mail.VelocityMailMessageTest.testVelocityTextMailMessage(VelocityMailMessageTest.java:133)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months