June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-840) Common test suite

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-840: ------------------------------------- Summary: Common test suite Key: JBJCA-840 URL: https://issues.jboss.org/browse/JBJCA-840 Project: IronJacamar Issue Type: Task Components: Common Reporter: Jesper Pedersen Assignee: Vladimir Rastseluev Fix For: 1.1.0.Beta2 * Clean up common/ test suite for duplicated tests * Improve code coverage, especially for resource adapter v1.0 * Remove incorrect DTD tests for v1.5 and v1.6 * Give descriptive names for test classes and resources -- 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

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] (AS7-4249) Inhereted start/stop methods are not invoked on a POJO

by Ivo Studensky (JIRA)

Ivo Studensky created AS7-4249: ---------------------------------- Summary: Inhereted start/stop methods are not invoked on a POJO Key: AS7-4249 URL: https://issues.jboss.org/browse/AS7-4249 Project: Application Server 7 Issue Type: Bug Components: POJO Affects Versions: 7.1.1.Final Reporter: Ivo Studensky Assignee: Ales Justin Fix For: 7.1.2.Final Let's say we have a POJO A which extends a class B. The start/stop methods are defined in the class B. In the jboss-beans.xml file is something like this: <bean name="A" class="blah.blah.A"/> Then, only the constructor of A is invoked by AS7, but no invocation of start/stop methods occur. The start/stop methods are invoked only if they are directly defined in A. -- 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

13 years, 7 months

3
4
0 / 0

[JBoss JIRA] (AS7-4167) Admin console: cannot set attribute max-attempts of modcluster subsystem

by Jan Martiska (JIRA)

Jan Martiska created AS7-4167: --------------------------------- Summary: Admin console: cannot set attribute max-attempts of modcluster subsystem Key: AS7-4167 URL: https://issues.jboss.org/browse/AS7-4167 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.1.Final Reporter: Jan Martiska Assignee: Heiko Braun Priority: Minor Under Networking tab of modcluster configuration - property "Max Attempts" cannot be set- console references it as "max-attemps" instead of the correct "max-attempts" {noformat} { "outcome" => "failed", "result" => {"step-1" => { "outcome" => "failed", "failure-description" => "JBAS014792: Unknown attribute max-attemps", "rolled-back" => true }}, "failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014792: Unknown attribute max-attemps"}}, "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} } {noformat} -- 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

13 years, 7 months

1
5
0 / 0

[JBoss JIRA] (AS7-4166) Admin console: cannot set attribute auto-enable-contexts of modcluster subsystem

by Jan Martiska (JIRA)

Jan Martiska created AS7-4166: --------------------------------- Summary: Admin console: cannot set attribute auto-enable-contexts of modcluster subsystem Key: AS7-4166 URL: https://issues.jboss.org/browse/AS7-4166 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.1.Final Reporter: Jan Martiska Assignee: Heiko Braun Priority: Minor Under Web Contexts tab of modcluster configuration - property "Auto Enable Contexts" cannot be set- console references it as "auto-enableContexts" instead of the correct "auto-enable-contexts" {noformat} { "outcome" => "failed", "result" => {"step-1" => { "outcome" => "failed", "failure-description" => "JBAS014792: Unknown attribute auto-enableContexts", "rolled-back" => true }}, "failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014792: Unknown attribute auto-enableContexts"}}, "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} {noformat} -- 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

13 years, 7 months

1
5
0 / 0

[JBoss JIRA] Created: (AS7-1263) Publish deployment descriptor schemas and dtd in the dist

by Brian Stansberry (JIRA)

Publish deployment descriptor schemas and dtd in the dist --------------------------------------------------------- Key: AS7-1263 URL: https://issues.jboss.org/browse/AS7-1263 Project: Application Server 7 Issue Type: Task Affects Versions: 7.0.0.Final Reporter: Brian Stansberry Fix For: 7.0.1.Final AS 7.0 has the domain/host/standalone config schemas in docs/schema, but not the deployment descriptor schemas and DTDs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

7
14
0 / 0

[JBoss JIRA] (AS7-4057) Create logging profiles for deployments

by James Perkins (JIRA)

James Perkins created AS7-4057: ---------------------------------- Summary: Create logging profiles for deployments Key: AS7-4057 URL: https://issues.jboss.org/browse/AS7-4057 Project: Application Server 7 Issue Type: Feature Request Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 7.2.0.Alpha1 Create logging profiles to be assignable to deployments. The precedence would be deployment configuration -> profile configuration -> default configuration. This would allow profiles to be configured with the management interface. Each profile would have it's own LogContext and the context could be secured. -- 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

13 years, 7 months

2
3
0 / 0

[JBoss JIRA] (AS7-2385) Management - readding file handler logger fails

by Dominik Pospisil (Created) (JIRA)

Management - readding file handler logger fails ----------------------------------------------- Key: AS7-2385 URL: https://issues.jboss.org/browse/AS7-2385 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Logging Affects Versions: 7.1.0.Beta1 Reporter: Dominik Pospisil Assignee: Brian Stansberry Removing and adding file handler fails. Perhaps remove operation does not clean up all resources properlly. Steps to reproduce: [standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:add(name="test-fh", level="WARN", file={"path" => "/home/dpospisi/testfh.log"}) {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:remove {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:add(name="test-fh", level="WARN", file={"path" => "/home/dpospisi/testfh.log"}) { "outcome" => "failed", "failure-description" => "Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.logging.handler-file.test-fh is already registered", "rolled-back" => true } [standalone@localhost:9999 /] -- 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

13 years, 7 months

6
5
0 / 0

[JBoss JIRA] (AS7-2873) EJB not defining an EJB 2 view method should not deploy

by Carlo de Wolf (Created) (JIRA)

EJB not defining an EJB 2 view method should not deploy ------------------------------------------------------- Key: AS7-2873 URL: https://issues.jboss.org/browse/AS7-2873 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: Carlo de Wolf Assignee: Stuart Douglas A bean which does not implement the sayHello method of the following EJB 2 remote view: {code:title=HelloRemote.java} public interface HelloRemote extends EJBObject { String sayHello(String name) throws RemoteException; } {code} gets the following exception during invocation: {noformat} Caused by: javax.ejb.EJBException: org.jboss.invocation.CannotProceedException: INV-00002:Invocation cannot proceed (end of interceptor chain has been hit) at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:241) at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:316) at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:201) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropogatingInterceptor.processInvocation(EJBRemoteTransactionPropogatingInterceptor.java:86) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:70) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:56) ... 126 more {noformat} Instead the EJB should not have deployed properly and throw a DeploymentException. -- 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

13 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (LOGTOOL-22) Add additional support for message validation.

by James Perkins (JIRA)

Add additional support for message validation. ---------------------------------------------- Key: LOGTOOL-22 URL: https://issues.jboss.org/browse/LOGTOOL-22 Project: Log Tool Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: David Lloyd Fix For: 1.0.0.Beta8 Add validation to see if the method parameters match the parameters required for the message. For example, an integer should be passed to String.format("%d"). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
9
0 / 0

[JBoss JIRA] (LOGTOOL-52) Remove string concatenation during message construction

by David Lloyd (JIRA)

David Lloyd created LOGTOOL-52: ---------------------------------- Summary: Remove string concatenation during message construction Key: LOGTOOL-52 URL: https://issues.jboss.org/browse/LOGTOOL-52 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Bill Burke Assignee: David Lloyd Fix For: 1.0.3.Final, 1.1.0.Beta1 I have noticed a small deficiency in your otherwise completely excellent software! As it turns out, the source code generation produces superfluous string concatenations. It would be more efficient if the string concatenation were to happen either during processing, or within the right-hand side of the static field assignment expression in the generated classes. Keep up the top-notch work on the definitely not over-engineered project! Excelsior!! -- 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

13 years, 7 months

3
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2012