July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-966) admin console randomly show defined datasources

by Marek Novotny (JIRA)

admin console randomly show defined datasources ----------------------------------------------- Key: AS7-966 URL: https://issues.jboss.org/browse/AS7-966 Project: Application Server 7 Issue Type: Bug Components: Console Environment: JBoss AS 7 Beta4-SNAPSHOT - Build #1158 (Jun 7, 2011 11:25:21 AM) Revision: a004da8272d7717225bfa1bc65534bb4b599bc1b Firefox 4.0.1, Ubuntu 11.04 Reporter: Marek Novotny Loading admin console at http://localhost.localdomain:9990/console/App.html#server/datasources shows empty datasource list. After creating new datasource it shows 2 datasources - one created myself and default H2DS. When I go to Deployments and back to Datasources it again shows only empty list. When I open standalone/configuration/standalone.xml both datasources are there. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMETA-335) Implement message-driven parsing

by Carlo de Wolf (JIRA)

Implement message-driven parsing -------------------------------- Key: JBMETA-335 URL: https://issues.jboss.org/browse/JBMETA-335 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Components: ejb Affects Versions: 7.0.0.Beta6 Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1342) :test-connection-in-pool fails in a strange way

by Heiko Rupp (JIRA)

:test-connection-in-pool fails in a strange way ----------------------------------------------- Key: AS7-1342 URL: https://issues.jboss.org/browse/AS7-1342 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.0.0.Final Reporter: Heiko Rupp Assignee: Stefano Maestri [11:54:03] <+pilhuhn> maeste hi [11:54:06] <+pilhuhn> what does this mean: [11:54:07] <+pilhuhn> [domain@localhost:9999 data-source=lalaDS] :test-connection-in-pool [11:54:07] <+pilhuhn> { [11:54:07] <+pilhuhn> "outcome" => "failed", [11:54:07] <+pilhuhn> "failure-description" => "failed to invoke operation: failed to match pool. Check JndiName: lalaJNDI", [11:54:57] <+maeste> that jndiName is not matched [11:55:19] <+pilhuhn> matched by? [11:55:34] <+maeste> by the runtime connection invoker [11:55:35] <+pilhuhn> If it is invalid, creation of the datasource should have failed ? [11:56:01] <+maeste> BTW maybe it'0s a bug when ds name and jndiName are not the same I'll check [11:56:14] <+pilhuhn> [domain@localhost:9999 data-source=lalaDS] :read-resource [11:56:14] <+pilhuhn> { [11:56:14] <+pilhuhn> "outcome" => "success", [11:56:14] <+pilhuhn> "result" => { [11:56:14] <+pilhuhn> "background-validation" => undefined, [11:56:14] <+pilhuhn> "background-validation-minutes" => undefined, [11:56:14] <+pilhuhn> "blocking-timeout-wait-millis" => undefined, [11:56:14] <+pilhuhn> "connection-url" => "jdbc:lala", [11:56:14] <+pilhuhn> "driver-name" => "postgresql-9.0-801.jdbc4.jar", [11:56:14] <+pilhuhn> "idle-timeout-minutes" => undefined, [11:56:14] <+pilhuhn> "jndi-name" => "lalaJNDI", [11:56:38] <+pilhuhn> I did define an invalid connection URL (on purpose) [11:56:39] <+maeste> yup probably the problem is mine [11:56:49] <+maeste> I'll have a look this afternoon [11:57:53] ChanServ sets mode +v Jaikiran [11:57:54] <+pilhuhn> ok -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1379) Provide the ability to update RA attributes

by Heiko Braun (JIRA)

Provide the ability to update RA attributes ------------------------------------------- Key: AS7-1379 URL: https://issues.jboss.org/browse/AS7-1379 Project: Application Server 7 Issue Type: Feature Request Components: JCA Reporter: Heiko Braun Assignee: Jeff Zhang Fix For: 7.1.0.Beta1 most of the attributes seem to be read only. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
9
0 / 0

[JBoss JIRA] Created: (AS7-873) Subsystem "datasources": attributes not writable

by Heiko Braun (JIRA)

Subsystem "datasources": attributes not writable ------------------------------------------------ Key: AS7-873 URL: https://issues.jboss.org/browse/AS7-873 Project: Application Server 7 Issue Type: Enhancement Components: Domain Management, JCA Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.1.0.Beta1 like this, modifications to datasource configurations are not possible -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1378) Make module directory configurable using .sh/.bat run scripts

by Rostislav Svoboda (JIRA)

Make module directory configurable using .sh/.bat run scripts ------------------------------------------------------------- Key: AS7-1378 URL: https://issues.jboss.org/browse/AS7-1378 Project: Application Server 7 Issue Type: Feature Request Reporter: Rostislav Svoboda Fix For: 7.1.0.Alpha1 Make module directory configurable using .sh/.bat run scripts, currently you can specify configuration location using '--server-config' or '--domain-config' + '--host-config' , location of modules directory should be configurable too. It's necessary to make changes on .bat/.sh files level to make module directory configurable. Currently it's hard-coded to use module directory under JBOSS_HOME directory {code} -mp \"$JBOSS_HOME/modules\" \ {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2262) When throwing an application exception in a method that is annotated with NOT_SUPPORTED it should not wrap the application Exception.

by Shaun Appleton (JIRA)

When throwing an application exception in a method that is annotated with NOT_SUPPORTED it should not wrap the application Exception. ------------------------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-2262 URL: https://issues.jboss.org/browse/EJBTHREE-2262 Project: EJB 3.0 Issue Type: Bug Reporter: Shaun Appleton When throwing an application exception in a method that is annotated with NOT_SUPPORTED it should not wrap the application Exception. What currently happen is that it is wrapped in an EJBException instead of being thrown un-wrapped. See Table 14 p361. of jsr-220 spec This has been tested on EAP 5.1.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-9231) Expose platform mxbeans via the domain model

by Brian Stansberry (JIRA)

Expose platform mxbeans via the domain model -------------------------------------------- Key: JBAS-9231 URL: https://issues.jboss.org/browse/JBAS-9231 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.CR1 Expose the java.lang.managment MXBeans. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (AS7-1317) Allow application exceptions to be defined when using the throws clause

by Carlo de Wolf (JIRA)

Allow application exceptions to be defined when using the throws clause ----------------------------------------------------------------------- Key: AS7-1317 URL: https://issues.jboss.org/browse/AS7-1317 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.0.0.Final Reporter: Carlo de Wolf Assignee: Carlo de Wolf Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-798) JMSTopicService and JMSQueueService made public for use outside of jboss-as-messaging

by Bob McWhirter (JIRA)

JMSTopicService and JMSQueueService made public for use outside of jboss-as-messaging ------------------------------------------------------------------------------------- Key: AS7-798 URL: https://issues.jboss.org/browse/AS7-798 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.0.0.Beta3 Reporter: Bob McWhirter Assignee: Jason Greene In TorqueBox, we allow applications to deploy queues with their application. JMSQueueService is perfect for it. But isn't public enough to consume. Likewise, JMSTopicService is slightly more public, but does involve some package-protected methods I might be interested in using. I'd love to have these services exposed enough to be externally useable. I understand the caveat of any queues/topics created this way being "unmanaged". I'm okay with that. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011