December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-46) Fix intermittent failures in DeploymentOverlayCLITestCase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-46?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFCORE-46: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1055229|https://bugzilla.redhat.com/show_bug.cgi?id=1055229] from MODIFIED to ON_QA > Fix intermittent failures in DeploymentOverlayCLITestCase > --------------------------------------------------------- > > Key: WFCORE-46 > URL: https://issues.jboss.org/browse/WFCORE-46 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha4 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 1.0.0.Alpha9 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-83) EAR deployment overlay did not work if there is no related resource included in the ear

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-83?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFCORE-83: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1055229|https://bugzilla.redhat.com/show_bug.cgi?id=1055229] from MODIFIED to ON_QA > EAR deployment overlay did not work if there is no related resource included in the ear > --------------------------------------------------------------------------------------- > > Key: WFCORE-83 > URL: https://issues.jboss.org/browse/WFCORE-83 > Project: WildFly Core > Issue Type: Bug > Reporter: Wolf-Dieter Fink > Assignee: Stuart Douglas > Fix For: 1.0.0.Alpha6 > > Attachments: reproducer.zip > > > It is possible to overlay WEB-inf/lib/xy.jar without having xy.jar included in the war file. > If an EAR file is used a module in the lib directory can not be added in the same way. But overlay is working if the lib/xy.jar is available. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-444) JAVA_OPTS environment variable not used for domain mode on Windows

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-444?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-444: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1170051|https://bugzilla.redhat.com/show_bug.cgi?id=1170051] from POST to MODIFIED > JAVA_OPTS environment variable not used for domain mode on Windows > ------------------------------------------------------------------ > > Key: WFCORE-444 > URL: https://issues.jboss.org/browse/WFCORE-444 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Josef Cacek > Assignee: Josef Cacek > > When I use JAVA_OPTS as an environment variable (i.e. configured before starting the AS) it's not propagated when used in domain mode on windows (domain.bat). > For standalone mode (standalone.bat) it works. > For Linux/Unix it works in both cases (standalone.sh, domain.sh). > Steps to reproduce: > {code} > SET "JAVA_OPTS=...MyOwnJavaOptsConfig..." > domain.bat > {code} > Actual result: > The configured JAVA_OPTS are not used. > Expected result: > Provided JAVA_OPTS are used for the process controller and host controller processes. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-267) CLI prints output twice if using cli client jar

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-267?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-267: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1149526|https://bugzilla.redhat.com/show_bug.cgi?id=1149526] from POST to MODIFIED > CLI prints output twice if using cli client jar > ----------------------------------------------- > > Key: WFCORE-267 > URL: https://issues.jboss.org/browse/WFCORE-267 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 1.0.0.Alpha13 > Reporter: Stan Silvert > Assignee: James Perkins > Fix For: 1.0.0.Alpha14 > > > If you are using the [CLI client jar|https://developer.jboss.org/wiki/UsingTheCLIRemoteClientJar], all output is printed twice. This is because JBoss logging is not set up and by default CommandContextImpl is printing log messages to standard out. The output will look something like this: > {code} > [standalone@localhost:9999 /] :read-children-types > Nov 19, 2014 8:57:19 AM org.jboss.as.cli.impl.CommandContextImpl printLine > INFO: { > "outcome" => "success", > "result" => [ > "core-service", > "deployment", > "deployment-overlay", > "extension", > "interface", > "path", > "socket-binding-group", > "subsystem", > "system-property" > ] > } > { > "outcome" => "success", > "result" => [ > "core-service", > "deployment", > "deployment-overlay", > "extension", > "interface", > "path", > "socket-binding-group", > "subsystem", > "system-property" > ] > } > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-776) Inject POJO to MBean by using <inject bean="XXX"> in jboss-service.xml does not work in SAR

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/WFLY-776?page=com.atlassian.jira.plugin.s... ] Romain Pelisse commented on WFLY-776: ------------------------------------- Regarding the two technical issues raised by Tomasz (and I've discussed with him over IRC): 1) dependency between the mbean service and the pojo service seems to be OK - it's not far fetch to think that MBean would need to access POJO just for this purpose (looking up dependency) 2) rather than chaning the XML syntax, we could change the content of the bean attribute, by adding a prefix: {code:xml} <mbean code="com.redhat.jboss.support.HelloService" name="example:type=HelloService,service=Hello"> <attribute name="Message">Hello!!</attribute> <attribute name="Task"><inject bean="pojo:myTask"/></attribute> </mbean> {code} Which leads to no prefix, default behavior, prefix load some factories/resolver based on the prefix. On top of not arming the current syntax, it also reuse an usual practice (like URL) to specifiy other mechanism to inject dependency. > Inject POJO to MBean by using <inject bean="XXX"> in jboss-service.xml does not work in SAR > ------------------------------------------------------------------------------------------- > > Key: WFLY-776 > URL: https://issues.jboss.org/browse/WFLY-776 > Project: WildFly > Issue Type: Bug > Components: JMX, POJO > Reporter: Masafumi Miura > Attachments: HelloService-AS7-inject-reproducer.tar.gz > > > When injecting POJO to MBean by using {{<inject bean="myTask"/>}} in {{jboss-service.xml}} of SAR like the following: > * META-INF/jboss-service.xml: > {code:xml} > <server> > <mbean code="com.redhat.jboss.support.HelloService" > name="example:type=HelloService,service=Hello"> > <attribute name="Message">Hello!!</attribute> > <attribute name="Task"><inject bean="myTask"/></attribute> > </mbean> > </server> > {code} > * META-INF/jboss-beans.xml: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <deployment ... > > <bean name="myTask" class="com.redhat.jboss.support.SimpleTask"> > </bean> > </deployment> > {code} > Then the following ERROR is happened at deployment of SAR: > {noformat:title=7.1.4.Final} > ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.mbean.service.example:type=HelloService,service=Hello.start Missing[jboss.mbean.service.myTask.start]","jboss.mbean.registration.example:type=HelloService,service=Hello Missing[JBAS014861: <one or more transitive dependencies>]","jboss.mbean.service.example:type=HelloService,service=Hello.create Missing[jboss.mbean.service.myTask.create]"]}}} > {noformat} > {noformat:title=7.2.0.Alpha1} > ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "HelloService.sar" was rolled back with the following failure message: > {"JBAS014771: Services with missing/unavailable dependencies" => [ > "jboss.mbean.service.example:type=HelloService,service=Hello.start is missing [jboss.mbean.service.myTask.start]", > "jboss.mbean.service.example:type=HelloService,service=Hello.create is missing [jboss.mbean.service.myTask.create]" > ]} > {noformat} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-354) Support EJB 2.0 dtd descriptors

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBMETA-354?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBMETA-354: ------------------------------------------------ Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1171105|https://bugzilla.redhat.com/show_bug.cgi?id=1171105] from NEW to ASSIGNED > Support EJB 2.0 dtd descriptors > ------------------------------- > > Key: JBMETA-354 > URL: https://issues.jboss.org/browse/JBMETA-354 > Project: JBoss Metadata > Issue Type: Bug > Components: ejb > Affects Versions: 7.0.0.Final > Reporter: Carlo de Wolf > Assignee: Ivo Studensky > Fix For: 8.1.2.Final, 7.2.1.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-354) Support EJB 2.0 dtd descriptors

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBMETA-354?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated JBMETA-354: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1057835, https://bugzilla.redhat.com/show_bug.cgi?id=1171105 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1057835) > Support EJB 2.0 dtd descriptors > ------------------------------- > > Key: JBMETA-354 > URL: https://issues.jboss.org/browse/JBMETA-354 > Project: JBoss Metadata > Issue Type: Bug > Components: ejb > Affects Versions: 7.0.0.Final > Reporter: Carlo de Wolf > Assignee: Ivo Studensky > Fix For: 8.1.2.Final, 7.2.1.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-448) CLI unable to load JAAS configuration on IBM JDK due to ClassNotFoundException

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-448: --------------------------------------- Summary: CLI unable to load JAAS configuration on IBM JDK due to ClassNotFoundException Key: WFCORE-448 URL: https://issues.jboss.org/browse/WFCORE-448 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 1.0.0.Alpha13 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Alpha14 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-447) Add jboss-metadata-common 8.1.2.Final

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-447?page=com.atlassian.jira.plugin... ] Jeff Mesnil reassigned WFCORE-447: ---------------------------------- Assignee: Jeff Mesnil (was: Tomaz Cerar) > Add jboss-metadata-common 8.1.2.Final > ------------------------------------- > > Key: WFCORE-447 > URL: https://issues.jboss.org/browse/WFCORE-447 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Test Suite > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > To be able to validate the subsystem's XML (in the tests and provided by the templates), we need to replace any expression in the XML (e.g. to replace an expression that resolve to a boolean or an int). > We need to add jboss-metadata-commons to the wildly-core project that will be used in the subsystem-test/framework/ module. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-447) Add jboss-metadata-common 8.1.2.Final

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFCORE-447: ---------------------------------- Summary: Add jboss-metadata-common 8.1.2.Final Key: WFCORE-447 URL: https://issues.jboss.org/browse/WFCORE-447 Project: WildFly Core Issue Type: Component Upgrade Components: Test Suite Reporter: Jeff Mesnil Assignee: Tomaz Cerar To be able to validate the subsystem's XML (in the tests and provided by the templates), we need to replace any expression in the XML (e.g. to replace an expression that resolve to a boolean or an int). We need to add jboss-metadata-commons to the wildly-core project that will be used in the subsystem-test/framework/ module. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 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 December 2014