September 2011 - jboss-jira - Jboss List Archives

[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

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1766) Jsr299BindingsInterceptor fails if TCCL not set during interceptor creation

by Stuart Douglas (JIRA)

Jsr299BindingsInterceptor fails if TCCL not set during interceptor creation --------------------------------------------------------------------------- Key: AS7-1766 URL: https://issues.jboss.org/browse/AS7-1766 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Affects Versions: 7.0.1.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.0.2.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1770) Multiple remove methods on a SFSB are causing deployment failure

by Stuart Douglas (JIRA)

Multiple remove methods on a SFSB are causing deployment failure ---------------------------------------------------------------- Key: AS7-1770 URL: https://issues.jboss.org/browse/AS7-1770 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.0.2.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.0.2.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Commented: (AS7-1702) Accept <any-address/> in Jboss AS7 configuration

by Michael Dobozy (JIRA)

[ https://issues.jboss.org/browse/AS7-1702?page=com.atlassian.jira.plugin.s... ] Michael Dobozy commented on AS7-1702: ------------------------------------- Here's a fix for this and some other issues w.r.t interface bindings in AS7's ARQ components: https://github.com/jbossas/jboss-as/pull/271 > Accept <any-address/> in Jboss AS7 configuration > ------------------------------------------------ > > Key: AS7-1702 > URL: https://issues.jboss.org/browse/AS7-1702 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.0.1.Final > Environment: JBoss AS 7.0.1.Final > Reporter: Alexandre Gattiker > > ERROR ArquillianServiceDeployer - Cannot deploy arquillian service > java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.asList(ModelValue.java:128) > at org.jboss.dmr.ModelNode.asList(ModelNode.java:1096) > at org.jboss.as.arquillian.container.ManagementClient.getInterface(ManagementClient.java:185) > at org.jboss.as.arquillian.container.ManagementClient.getBinding(ManagementClient.java:177) > at org.jboss.as.arquillian.container.ManagementClient.extractSubSystemURI(ManagementClient.java:148) > at org.jboss.as.arquillian.container.ManagementClient.getSubSystemURI(ManagementClient.java:90) > at org.jboss.as.arquillian.container.ManagementClient.getDeploymentMetaData(ManagementClient.java:96) > at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:98) > at org.jboss.as.arquillian.protocol.jmx.ArquillianServiceDeployer.doServiceDeploy(ArquillianServiceDeployer.java:58) > After changing the JBoss AS 7 configuration from: > <interface name="public"> > <inet-address value="127.0.0.1"/> > </interface> > to: > <interface name="public"> > <any-address/> > </interface> > Presumed cause: > in org.jboss.as.arquillian.container.ManagementClient in jboss-as-arquillian-common-7.0.1.Final.jar: > return rootNode.get("interface").get(name).get("criteria").asList().get(0).get("inet-address").asString(); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (AS7-1702) Accept <any-address/> in Jboss AS7 configuration

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/AS7-1702?page=com.atlassian.jira.plugin.s... ] Shelly McGowan commented on AS7-1702: ------------------------------------- With this recent commit: https://github.com/jbossas/jboss-as/commit/26cf6decdc771760837ad2f6a3f2aa... org.jboss.as.arquillian.container.ManagementClient.getBinding(socketBinding) throws an IllegalArgumentException: {code} java.lang.IllegalArgumentException at java.net.URI.create(URI.java:842) at org.jboss.as.arquillian.container.ManagementClient.getBinding(ManagementClient.java:181) at org.jboss.as.arquillian.container.ManagementClient.extractSubSystemURI(ManagementClient.java:148) at org.jboss.as.arquillian.container.ManagementClient.getSubSystemURI(ManagementClient.java:90) at org.jboss.as.arquillian.container.ManagementClient.getDeploymentMetaData(ManagementClient.java:96) at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:98) <snip> Caused by: java.net.URISyntaxException: Illegal character in authority at index 7: http://${jboss.bind.address.public:127.0.0.1}:8080 at java.net.URI$Parser.fail(URI.java:2809) at java.net.URI$Parser.parseAuthority(URI.java:3147) at java.net.URI$Parser.parseHierarchical(URI.java:3058) at java.net.URI$Parser.parse(URI.java:3014) at java.net.URI.<init>(URI.java:578) at java.net.URI.create(URI.java:840) {code} related to determining the IP address using the getInterface(intf) method: {code} private String getInterface(String name) { ModelNode node = rootNode.get("interface").get(name).get("criteria").asList().get(0).get("inet-address"); return node.resolve().asString(); } {code} > Accept <any-address/> in Jboss AS7 configuration > ------------------------------------------------ > > Key: AS7-1702 > URL: https://issues.jboss.org/browse/AS7-1702 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.0.1.Final > Environment: JBoss AS 7.0.1.Final > Reporter: Alexandre Gattiker > > ERROR ArquillianServiceDeployer - Cannot deploy arquillian service > java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.asList(ModelValue.java:128) > at org.jboss.dmr.ModelNode.asList(ModelNode.java:1096) > at org.jboss.as.arquillian.container.ManagementClient.getInterface(ManagementClient.java:185) > at org.jboss.as.arquillian.container.ManagementClient.getBinding(ManagementClient.java:177) > at org.jboss.as.arquillian.container.ManagementClient.extractSubSystemURI(ManagementClient.java:148) > at org.jboss.as.arquillian.container.ManagementClient.getSubSystemURI(ManagementClient.java:90) > at org.jboss.as.arquillian.container.ManagementClient.getDeploymentMetaData(ManagementClient.java:96) > at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:98) > at org.jboss.as.arquillian.protocol.jmx.ArquillianServiceDeployer.doServiceDeploy(ArquillianServiceDeployer.java:58) > After changing the JBoss AS 7 configuration from: > <interface name="public"> > <inet-address value="127.0.0.1"/> > </interface> > to: > <interface name="public"> > <any-address/> > </interface> > Presumed cause: > in org.jboss.as.arquillian.container.ManagementClient in jboss-as-arquillian-common-7.0.1.Final.jar: > return rootNode.get("interface").get(name).get("criteria").asList().get(0).get("inet-address").asString(); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
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

14 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (JBBUILD-697) Add plugin version for maven-bundle-plugin

by Thomas Diesler (JIRA)

Add plugin version for maven-bundle-plugin ------------------------------------------ Key: JBBUILD-697 URL: https://issues.jboss.org/browse/JBBUILD-697 Project: JBoss Build System Issue Type: Feature Request Components: JBoss Parent POM Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBoss Parent POM - 7 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1683) Connection factory connector-ref element not properly handled

by Brian Stansberry (JIRA)

Connection factory connector-ref element not properly handled ------------------------------------------------------------- Key: AS7-1683 URL: https://issues.jboss.org/browse/AS7-1683 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JMS Affects Versions: 7.0.1.Final, 7.0.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.0.Beta1 The backup-connector-name attribute in a JMS connection factory's connector-ref element isn't being parsed or stored in the model. In the model, the "connector" attribute in a connection factory resource should be a simple Map<String, String> (i.e. ModelType.OBJECT with value type ModelType.STRING) with undefined values allowed. The value is the optional backup-connector-name. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1466) Use socket binding for messaging subsystem broadcast group and discovery group

by Brian Stansberry (JIRA)

Use socket binding for messaging subsystem broadcast group and discovery group ------------------------------------------------------------------------------ Key: AS7-1466 URL: https://issues.jboss.org/browse/AS7-1466 Project: Application Server 7 Issue Type: Task Components: Domain Management, JMS Reporter: Brian Stansberry Fix For: 7.1.0.Alpha1 The messaging subsystem broadcast-group and discovery-group configs are using IP addresses and ports. They should use a "socket-binding" attribute which results in the injection of a SocketBinding service into some service. This will require a change to the xsd. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1405) Provide jms-topic DMR descriptions

by Heiko Braun (JIRA)

Provide jms-topic DMR descriptions ---------------------------------- Key: AS7-1405 URL: https://issues.jboss.org/browse/AS7-1405 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JMS Affects Versions: 7.0.0.Final Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.0.1.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
2
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 September 2011