March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-216) Include Infinispan CDI as a JBoss module

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-216?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar commented on WFLY-216: ---------------------------------- any news here? > Include Infinispan CDI as a JBoss module > ---------------------------------------- > > Key: WFLY-216 > URL: https://issues.jboss.org/browse/WFLY-216 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Avelino Martins > Assignee: Radoslav Husar > Fix For: 9.0.0.Beta1 > > > CDI has become an invaluable technology on any JavaEE project. I find hard to justify having to include infinispan-cdi as a compile dependency on every project that uses ISPN. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-570) Check ModelTypes in jacorb subsystem

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-570?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar closed WFLY-570. ---------------------------- Resolution: Out of Date Closing as we replaced jacorb subsystem with jdkorb one > Check ModelTypes in jacorb subsystem > ------------------------------------ > > Key: WFLY-570 > URL: https://issues.jboss.org/browse/WFLY-570 > Project: WildFly > Issue Type: Task > Components: Domain Management, IIOP > Affects Versions: 8.0.0.Alpha1 > Reporter: Brian Stansberry > Fix For: 9.0.0.Beta1 > > > There are a number of attributes in the Jacorb subsystem that use ModelType.STRING for things that look like booleans. Check through the attributes and change to ModelType.BOOLEAN where appropriate. > This shouldn't raise a compatibility issue, since ModelType.BOOLEAN is freely convertible to ModelType.STRING, and vice-versa so long as the string represents as boolean (which it would have to do for the attribute to work anyway.) If anything is changed though, a Console subtask should be created to look into any UI implications. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2824) Remove https://issues.apache.org/jira/browse/DIRAPI-125 workaround

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2824?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-2824: --------------------------------- Assignee: Tomaz Cerar (was: Brian Stansberry) > Remove https://issues.apache.org/jira/browse/DIRAPI-125 workaround > ------------------------------------------------------------------- > > Key: WFLY-2824 > URL: https://issues.jboss.org/browse/WFLY-2824 > Project: WildFly > Issue Type: Task > Components: Test Suite > Affects Versions: 8.0.0.CR1 > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: 9.0.0.Beta1 > > > As a workaround for an Apache DS bug (https://issues.apache.org/jira/browse/DIRAPI-125) we forked their LdapUrl class in the testsuite/integration/basic module. This JIRA is a reminder to check if the upstream bug is fixed and the fix is in the release WF uses; if so remove the workaround. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1129) Add VisualVm launch scripts to the AS7 distribution

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1129?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1129: ----------------------------------- Priority: Optional (was: Trivial) > Add VisualVm launch scripts to the AS7 distribution > --------------------------------------------------- > > Key: WFLY-1129 > URL: https://issues.jboss.org/browse/WFLY-1129 > Project: WildFly > Issue Type: Feature Request > Components: Scripts > Environment: All > Reporter: John O'Hara > Priority: Optional > > Launching VisualVM with remoting-jmx requires additional jars to be on the classpath, in the same way that launching jconsole does. > Can we provice a .sh and a .bat with the correct classpath in the AS7 distribution to launch visualvm -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-578) Better warning message in add-user.sh

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-578?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-3781 to WFCORE-578: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-578 (was: WFLY-3781) Affects Version/s: (was: 8.1.0.Final) Component/s: Scripts (was: Scripts) Fix Version/s: 1.0.0.Alpha11 (was: Awaiting Volunteers) > Better warning message in add-user.sh > ------------------------------------- > > Key: WFCORE-578 > URL: https://issues.jboss.org/browse/WFCORE-578 > Project: WildFly Core > Issue Type: Feature Request > Components: Scripts > Environment: Linux > Reporter: David Tonhofer > Assignee: David Salter > Priority: Minor > Fix For: 1.0.0.Alpha11 > > > If (shell or environment) variable JBOSS_HOME is set to something unexpected, then add-user.sh complains: > "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur." > This can be made clearer, e.g.: > "WARNING: The JBOSS_HOME (/usr/java/jboss7) that this script will use may indicate a different installation than the one this script resides in (/usr/local/java/wildfly) - unpredictable results may occur." > Change of line 35 in "bin/add-user.sh": > echo "WARNING: The JBOSS_HOME ($SANITIZED_JBOSS_HOME) that this script will use may indicate a different installation than the one this script resides in ($RESOLVED_JBOSS_HOME) - unpredictable results may occur." -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4231) Update Hibernate Search to version 5.0.0.Final and depending HQL Parser to version 1.1.0.Final

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4231?page=com.atlassian.jira.plugin.... ] Tomaz Cerar resolved WFLY-4231. ------------------------------- Resolution: Done PR was merged some time ago > Update Hibernate Search to version 5.0.0.Final and depending HQL Parser to version 1.1.0.Final > ---------------------------------------------------------------------------------------------- > > Key: WFLY-4231 > URL: https://issues.jboss.org/browse/WFLY-4231 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.0.0.Beta1 > > > The Hibernate HQL Parser depends on this specific version of Hibernate Search, so the two components need to be updated atomically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3781) Better warning message in add-user.sh

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3781?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-3781: -------------------------------------- Assignee: David Salter > Better warning message in add-user.sh > ------------------------------------- > > Key: WFLY-3781 > URL: https://issues.jboss.org/browse/WFLY-3781 > Project: WildFly > Issue Type: Feature Request > Components: Scripts > Affects Versions: 8.1.0.Final > Environment: Linux > Reporter: David Tonhofer > Assignee: David Salter > Priority: Minor > Fix For: Awaiting Volunteers > > > If (shell or environment) variable JBOSS_HOME is set to something unexpected, then add-user.sh complains: > "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur." > This can be made clearer, e.g.: > "WARNING: The JBOSS_HOME (/usr/java/jboss7) that this script will use may indicate a different installation than the one this script resides in (/usr/local/java/wildfly) - unpredictable results may occur." > Change of line 35 in "bin/add-user.sh": > echo "WARNING: The JBOSS_HOME ($SANITIZED_JBOSS_HOME) that this script will use may indicate a different installation than the one this script resides in ($RESOLVED_JBOSS_HOME) - unpredictable results may occur." -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4309) hibernate-configuration-3.0.dtd should be loaded from ORM jar but opens http://hibernate.org instead

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4309?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-4309: --------------------------------- Assignee: Tomaz Cerar (was: Scott Marlow) Resolution: Partially Completed worked around by not including xsd schema in our hibernate 3 xmls > hibernate-configuration-3.0.dtd should be loaded from ORM jar but opens http://hibernate.org instead > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-4309 > URL: https://issues.jboss.org/browse/WFLY-4309 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Tomaz Cerar > Fix For: 9.0.0.Beta1 > > > The WildFly testsuite is seeing testsuite failures when a connection to org.hibernate cannot be obtained. See HHH-9511 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-244) Undertow Integration Tracker

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-244?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar resolved WFLY-244. ------------------------------ Resolution: Done > Undertow Integration Tracker > ---------------------------- > > Key: WFLY-244 > URL: https://issues.jboss.org/browse/WFLY-244 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Tomaz Cerar > Priority: Critical > Fix For: 9.0.0.Beta1 > > > Tracking issue for all issues related to undertow integration. > as part of https://github.com/wildfly/wildfly/pull/4810 there tests removed that need to be re-added as part of this tracking issue -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-838) Can't get implementing classname for JSR77 MBean

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-838?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reassigned WFLY-838: ------------------------------------- Assignee: Kabir Khan > Can't get implementing classname for JSR77 MBean > ------------------------------------------------ > > Key: WFLY-838 > URL: https://issues.jboss.org/browse/WFLY-838 > Project: WildFly > Issue Type: Bug > Components: JMX > Reporter: Anders Welen > Assignee: Kabir Khan > Priority: Minor > Fix For: Awaiting Volunteers > > > The following exception are thrown when asking the MBean server for the classname implementing "jboss.jsr77:j2eeType=WebModule,name=MyWar.war,J2EEServer=default". > It should be a legal call. Why are the code clearly states it's illegal? > > java.lang.IllegalStateException: JBAS019905: Should not get called > at org.jboss.as.jsr77.managedobject.J2EEDeployedObjectHandlers$J2EEModuleHandler.queryObjectNames(J2EEDeployedObjectHandlers.java:245) > at org.jboss.as.jsr77.managedobject.BaseHandler.getMBeanInfo(BaseHandler.java:64) > at org.jboss.as.jsr77.managedobject.J2EEDeployedObjectHandlers.getMBeanInfo(J2EEDeployedObjectHandlers.java:147) > at org.jboss.as.jsr77.managedobject.ManagedObjectHandlerRegistry.getMBeanInfo(ManagedObjectHandlerRegistry.java:112) > at org.jboss.as.jsr77.subsystem.JSR77ManagementMBeanServer.getMBeanInfo(JSR77ManagementMBeanServer.java:179) > at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanInfo(PluggableMBeanServerImpl.java:212) > > The error can easily be triggered by using JConsole to browse the same MBean. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2015