October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2123) Fix or remove ignored tests in Messaging test cases

by Thomas Diesler (Created) (JIRA)

Fix or remove ignored tests in Messaging test cases --------------------------------------------------- Key: AS7-2123 URL: https://issues.jboss.org/browse/AS7-2123 Project: Application Server 7 Issue Type: Sub-task Reporter: Thomas Diesler Assignee: Richard Opalka Fix For: 7.0.0.CR1, 7.1.0.Beta1 We are in the process of a major test infrastructure update. For this I migrated all smoke tests the the managed container. The arquillian subsystem has been replaced by a on-demand deployment. Your test might be @Ignored because I could not fix it easily or it has already been ignored for some time. Please have a look if you can fix it, otherwise I'd like to know why it should be ignored. -- 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

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] (AS7-2125) Weld SPI TransactionServices implementation incorrectly evaluates transaction activity

by Martin Kouba (Created) (JIRA)

Weld SPI TransactionServices implementation incorrectly evaluates transaction activity -------------------------------------------------------------------------------------- Key: AS7-2125 URL: https://issues.jboss.org/browse/AS7-2125 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Affects Versions: 7.0.2.Final Reporter: Martin Kouba Assignee: Stuart Douglas *org.jboss.as.weld.services.bootstrap.WeldTransactionServices#isTransactionActive()* impl is not valid. -- 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

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] (JGRP-1373) MERGE2: findAllViews assumes the list returned by the discovery protocol is modifiable

by Dan Berindei (Created) (JIRA)

MERGE2: findAllViews assumes the list returned by the discovery protocol is modifiable -------------------------------------------------------------------------------------- Key: JGRP-1373 URL: https://issues.jboss.org/browse/JGRP-1373 Project: JGroups Issue Type: Bug Affects Versions: 3.0 Reporter: Dan Berindei Assignee: Bela Ban In the Infinispan test suite we use a custom TEST_PING protocol to speed up discovery and it sometimes returns Collections.emptyList(). This triggers an UnsupportedOperationException in MERGE2: 2011-10-09 10:34:30,381 ERROR (Timer-5,Infinispan-Cluster,RehashAfterPartitionMergeTest-NodeA-56050) [org.jgroups.util.T imeScheduler2] failed executing task org.jgroups.protocols.MERGE2$1@4dbce33 java.lang.UnsupportedOperationException at java.util.AbstractList.add(AbstractList.java:148) at java.util.AbstractList.add(AbstractList.java:108) at org.jgroups.protocols.MERGE2$FindSubgroupsTask.findAllViews(MERGE2.java:325) at org.jgroups.protocols.MERGE2$FindSubgroupsTask._findAndNotify(MERGE2.java:255) at org.jgroups.protocols.MERGE2$FindSubgroupsTask.findAndNotify(MERGE2.java:246) at org.jgroups.protocols.MERGE2$1.run(MERGE2.java:202) at org.jgroups.util.TimeScheduler2$MyTask.run(TimeScheduler2.java:523) at org.jgroups.util.TimeScheduler2$Entry.execute(TimeScheduler2.java:428) at org.jgroups.util.TimeScheduler2$1.run(TimeScheduler2.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) -- 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

14 years, 9 months

5
4
0 / 0

[JBoss JIRA] (JBMETA-339) Fix QName parsing

by Richard Opalka (Created) (JIRA)

Fix QName parsing ----------------- Key: JBMETA-339 URL: https://issues.jboss.org/browse/JBMETA-339 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: common Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 7.0.0.Beta14 -- 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

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1907) Provide suppor for expression across all form elements

by Heiko Braun (JIRA)

Provide suppor for expression across all form elements ------------------------------------------------------ Key: AS7-1907 URL: https://issues.jboss.org/browse/AS7-1907 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Priority: Blocker Fix For: 7.1.0.Alpha1 bstansberry: <inet-address value="${jboss.bind.address:127.0.0.1}"/> [3:11pm] hbraun: the first part is resolved from system properties? [3:11pm] hbraun: the later is the default? [3:11pm] bstansberry: yes [3:11pm] hbraun: wicked [3:12pm] bstansberry: but what's stored in the model is a ModelNode of type ModelType.EXPRESSION [3:12pm] bstansberry: and the metadata for the attribute includes "expression-allowed" => true [3:12pm] hbraun: ok [3:13pm] hbraun: did you just want to raise my attention? [3:13pm] bstansberry: those really should appearing all over the place [3:13pm] bstansberry: yeah [3:14pm] bstansberry: really a very heavy % of attributes should allow expressions [3:14pm] hbraun: damn [3:14pm] hbraun: i need to think about the implications [3:14pm] hbraun: for the UI [3:15pm] hbraun: so attributes actually allow multiple types? [3:15pm] hbraun: i.e. string or expression [3:15pm] bstansberry: yes, X or expression [3:15pm] bstansberry: where X is the "type" = X in the metadata [3:16pm] hbraun: do we have proper setters for expression values? [3:16pm] hbraun: in the DMR lib I mean? [3:16pm] hbraun: or how does it currently work [3:16pm] hbraun: ? [3:16pm] bstansberry: ModeNode.setExpression(String s) [3:16pm] hbraun: i.e. how do you create an add operation that contains an expression? [3:16pm] hbraun: ah, guess we didn't port that to the GWT lib yet -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1995) Re-entrant call into SFSB invalidly blocks

by Carlo de Wolf (JIRA)

Re-entrant call into SFSB invalidly blocks ------------------------------------------ Key: AS7-1995 URL: https://issues.jboss.org/browse/AS7-1995 Project: Application Server 7 Issue Type: Bug Components: EJB Environment: https://github.com/wolfc/jboss-as/tree/reentrant Reporter: Carlo de Wolf Assignee: Stuart Douglas Fix For: 7.1.0.CR1 Calling a method on the proxy returned by SessionContext.getBusinessObject(Class) can lead to incorrect ConcurrentAccess(Timeout)Exceptions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
8
0 / 0

[JBoss JIRA] (AS7-2121) Add J2EE-DeploymentFactory-Implementation-Class to JSR-88 manifest

by Thomas Diesler (Created) (JIRA)

Add J2EE-DeploymentFactory-Implementation-Class to JSR-88 manifest ------------------------------------------------------------------ Key: AS7-2121 URL: https://issues.jboss.org/browse/AS7-2121 Project: Application Server 7 Issue Type: Bug Reporter: Thomas Diesler Assignee: Thomas Diesler -- 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

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1608) Deployment is not copied to host added to domain after deployment.

by Matej Lazar (JIRA)

Deployment is not copied to host added to domain after deployment. ------------------------------------------------------------------ Key: AS7-1608 URL: https://issues.jboss.org/browse/AS7-1608 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Alpha1 Reporter: Matej Lazar Assignee: Brian Stansberry -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
4
0 / 0

[JBoss JIRA] (JGRP-188) JGroups should not use System properties, because it's too restrictive

by Bela Ban (Commented) (JIRA)

[ https://issues.jboss.org/browse/JGRP-188?page=com.atlassian.jira.plugin.s... ] Bela Ban commented on JGRP-188: ------------------------------- Julien, what do you suggest we change ? > JGroups should not use System properties, because it's too restrictive > ---------------------------------------------------------------------- > > Key: JGRP-188 > URL: https://issues.jboss.org/browse/JGRP-188 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 2.2.8, 2.2.9, 2.2.9.1 > Environment: all > Reporter: Robert Stevenson > Assignee: Bela Ban > Priority: Minor > Fix For: 2.4 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > JGroups should not use System properties for configuration, it should instead use a Global Configurator class (singleton), similar to log4j; which just contains a Properties object. This would allow JGroups to be much easier to move around to different environments. For example : (Applet), which does not have access to easily change System properties, on a per applet basis. > This new class could have a mapping/conversion method to make the current -D command line options be put into this new Properties Configurator for backward compatibility -- 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

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-2119) Portable war: Weld deployment on JBoss AS 7 should not require to remove the WeldListener line from the web.xml

by Stuart Douglas (Resolved) (JIRA)

[ https://issues.jboss.org/browse/AS7-2119?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-2119. --------------------------------- Assignee: Stuart Douglas Fix Version/s: 7.1.0.Beta1 Resolution: Done > Portable war: Weld deployment on JBoss AS 7 should not require to remove the WeldListener line from the web.xml > --------------------------------------------------------------------------------------------------------------- > > Key: AS7-2119 > URL: https://issues.jboss.org/browse/AS7-2119 > Project: Application Server 7 > Issue Type: Feature Request > Affects Versions: 7.1.0.Alpha1 > Reporter: Geoffrey De Smet > Assignee: Stuart Douglas > Priority: Critical > Fix For: 7.1.0.Beta1 > > > When deploying on JBoss AS 7, the web.xml can't contain this: > {code} > <listener> > <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class> > </listener> > {code} > When deploying on any other app servers (JBoss AS 5.1 EAP, Tomcat 6, Jetty 6, ...) that code needs to be there. > This makes for an unportable wars. > Maven profiles cannot fix this in many cases: > - You don't want to run your build 5 times to build 5 different wars. You run it once, build a generic war and use assembly descriptors to build 5 appserver specific wars from that. > - When you're using GWT, you want run in GWT-hosted mode (which uses jetty 6) a lot. So the default web.xml needs to contain it. > - When you're using arquillian-jboss7 (in maven and straight for your IDE), the default web.xml should not have it. > - When you're deploying a generic war to nexus, the web.xml should contain it? -- 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

14 years, 9 months

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