June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-64) Filesystem deployment scanner deployment failure removes unrelated deployments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-64?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFCORE-64: ----------------------------------------------- Radovan Netuka <rnetuka(a)redhat.com> changed the Status of [bug 1291710|https://bugzilla.redhat.com/show_bug.cgi?id=1291710] from POST to MODIFIED > Filesystem deployment scanner deployment failure removes unrelated deployments > ------------------------------------------------------------------------------ > > Key: WFCORE-64 > URL: https://issues.jboss.org/browse/WFCORE-64 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha5 > Environment: WIndows and Linux platforms both exhibit the issue > Reporter: Jess Holle > Assignee: ehsavoie Hugonnet > > If one's standalone-full.xml configuration contains something like: > <deployments> > <deployment name="MyWebApp.war" runtime-name="MyWebApp.war" enabled="true"> > <fs-exploded path="../../SomeDir/MyWebApp.war" relative-to="jboss.home.dir"/> > </deployment> > </deployments> > whether manually inserted (while the server is not running) or installed via the CLI via > /deployment=ServiceCenter.war/:add(runtime-name=ServiceCenter.war,content=[{archive=false,path="../../Windchill/ServiceCenter.war",relative-to="jboss.home.dir"}]) > and a deployment scanner like: > <subsystem xmlns="urn:jboss:domain:deployment-scanner:2.0"> > <deployment-scanner name="1" path="../../../Applications" relative-to="jboss.server.base.dir" scan-interval="5000" auto-deploy-exploded="true"/> > </subsystem> > a failure by a deployment-scanner to deploy an application (exploded in my case, though I'm not sure this makes a difference) will cause the explicitly listed <deployments> to be removed from the configuration! > This occurs irrespective of the value used for auto-deploy-exploded and to <deployment> elements that had already successfully been deployed and started. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6402) EJBs accessible too early (spec violation)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6402?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-6402: ----------------------------------------------- Radovan Netuka <rnetuka(a)redhat.com> changed the Status of [bug 1310908|https://bugzilla.redhat.com/show_bug.cgi?id=1310908] from POST to MODIFIED > EJBs accessible too early (spec violation) > ------------------------------------------ > > Key: WFLY-6402 > URL: https://issues.jboss.org/browse/WFLY-6402 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Brad Maxwell > Assignee: Fedor Gavrilov > Labels: downstream_dependency > Attachments: auto-test-reproducer.zip > > > {code} > EJB 3.1 spec, section 4.8.1: > "If the Startup annotation appears on the Singleton bean class or if the Singleton has been designated via the deployment descriptor as requiring eager initialization, the container must initialize the Singleton bean instance during the application startup sequence. The container must initialize all such startup-time Singletons before any external client requests (that is, client requests originating outside of the application) are delivered to any enterprise bean components in the application. > {code} > Wildlfy does not implement this correctly, and allows calls to other EJBs before a @Startup @Singleton finishes its @PostConstruct call. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-64) Filesystem deployment scanner deployment failure removes unrelated deployments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-64?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFCORE-64: ----------------------------------------------- Radovan Netuka <rnetuka(a)redhat.com> changed the Status of [bug 1327093|https://bugzilla.redhat.com/show_bug.cgi?id=1327093] from POST to MODIFIED > Filesystem deployment scanner deployment failure removes unrelated deployments > ------------------------------------------------------------------------------ > > Key: WFCORE-64 > URL: https://issues.jboss.org/browse/WFCORE-64 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha5 > Environment: WIndows and Linux platforms both exhibit the issue > Reporter: Jess Holle > Assignee: ehsavoie Hugonnet > > If one's standalone-full.xml configuration contains something like: > <deployments> > <deployment name="MyWebApp.war" runtime-name="MyWebApp.war" enabled="true"> > <fs-exploded path="../../SomeDir/MyWebApp.war" relative-to="jboss.home.dir"/> > </deployment> > </deployments> > whether manually inserted (while the server is not running) or installed via the CLI via > /deployment=ServiceCenter.war/:add(runtime-name=ServiceCenter.war,content=[{archive=false,path="../../Windchill/ServiceCenter.war",relative-to="jboss.home.dir"}]) > and a deployment scanner like: > <subsystem xmlns="urn:jboss:domain:deployment-scanner:2.0"> > <deployment-scanner name="1" path="../../../Applications" relative-to="jboss.server.base.dir" scan-interval="5000" auto-deploy-exploded="true"/> > </subsystem> > a failure by a deployment-scanner to deploy an application (exploded in my case, though I'm not sure this makes a difference) will cause the explicitly listed <deployments> to be removed from the configuration! > This occurs irrespective of the value used for auto-deploy-exploded and to <deployment> elements that had already successfully been deployed and started. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-281) Investigate if it's possible to modify the OTP SASL mechanism and password implementation to make use of the credential verification API

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-281?page=com.atlassian.jira.plugin.sy... ] Farah Juma resolved ELY-281. ---------------------------- Resolution: Out of Date ELY-535 removed the need for this. > Investigate if it's possible to modify the OTP SASL mechanism and password implementation to make use of the credential verification API > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-281 > URL: https://issues.jboss.org/browse/ELY-281 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Farah Juma > Assignee: Farah Juma > > The main idea here is to be able to pass the guess that's being verified to the realm and have the realm handle updating the stored credential if verification succeeds. > Relevant chat discussion: > {quote} > \[8:42 AM\] Darran Lofthouse: @KabirKhan Ok, so you are trying to test OTP and require updates to be applied to the realm > \[8:43 AM\] Darran Lofthouse: One option is to update the ServerAuthenticationContext to make an update > \[8:43 AM\] Kabir Khan: That is what I had planned > \[8:43 AM\] Darran Lofthouse: I do also wonder if a second option may be to use the credential verification API we have instead so the credential being verified is passed into the realm and the realm can handle updates internally > \[8:44 AM\] Darran Lofthouse: although have not been in the credential in detail to see if this is possible > \[8:44 AM\] Kabir Khan: Possibly, I'd need to look at the code a bit better though > \[8:44 AM\] Kabir Khan: the first option is what stood out to me > \[8:45 AM\] Darran Lofthouse: the first option may match with how the credential and mech are currently implemented - but does risk us adding more and more behaviour to ServerAuthenticationContext > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6707) WildFly Test Suite: Integration - XTS is a little bit confusing and needs small cleanup

by Daniel Simko (JIRA)

[ https://issues.jboss.org/browse/WFLY-6707?page=com.atlassian.jira.plugin.... ] Daniel Simko reassigned WFLY-6707: ---------------------------------- Assignee: Gytis Trikleris (was: Daniel Simko) > WildFly Test Suite: Integration - XTS is a little bit confusing and needs small cleanup > --------------------------------------------------------------------------------------- > > Key: WFLY-6707 > URL: https://issues.jboss.org/browse/WFLY-6707 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite, XTS > Affects Versions: 10.0.0.Final > Reporter: Daniel Simko > Assignee: Gytis Trikleris > Priority: Minor > > The line https://github.com/wildfly/wildfly/blob/master/testsuite/integration/xts/... is never reached because exception is thrown from the line before. > The Javadoc https://github.com/wildfly/wildfly/blob/master/testsuite/integration/xts/... is copied from https://github.com/wildfly/quickstart/blob/10.x/wsba-coordinator-completi... and doesn't make sense here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-273) Expose RealmIdentity.getAttributes()

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-273?page=com.atlassian.jira.plugin.sy... ] Farah Juma commented on ELY-273: -------------------------------- As mentioned in [PR #441|https://github.com/wildfly-security/wildfly-elytron/pull/441], the timeout handling will be covered by ELY-558 instead of using a {{RealmIdentity}} attribute. However, exposing the {{RealmIdentity#getAttributes}} method is still useful nonetheless. > Expose RealmIdentity.getAttributes() > ------------------------------------ > > Key: ELY-273 > URL: https://issues.jboss.org/browse/ELY-273 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Realms > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 1.1.0.Beta6 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6707) WildFly Test Suite: Integration - XTS is a little bit confusing and needs small cleanup

by Daniel Simko (JIRA)

Daniel Simko created WFLY-6707: ---------------------------------- Summary: WildFly Test Suite: Integration - XTS is a little bit confusing and needs small cleanup Key: WFLY-6707 URL: https://issues.jboss.org/browse/WFLY-6707 Project: WildFly Issue Type: Enhancement Components: Test Suite, XTS Affects Versions: 10.0.0.Final Reporter: Daniel Simko Assignee: Daniel Simko Priority: Minor The line https://github.com/wildfly/wildfly/blob/master/testsuite/integration/xts/... is never reached because exception is thrown from the line before. The Javadoc https://github.com/wildfly/wildfly/blob/master/testsuite/integration/xts/... is copied from https://github.com/wildfly/quickstart/blob/10.x/wsba-coordinator-completi... and doesn't make sense here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1290) Upgrade Marshalling to 1.4.11.Final

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1290?page=com.atlassian.jira.plugi... ] Tomaz Cerar updated WFCORE-1290: -------------------------------- Description: Change log https://issues.jboss.org/projects/JBMAR/versions/12329371 (was: Release is not out yet. Change log https://issues.jboss.org/projects/JBMAR/versions/12329371) > Upgrade Marshalling to 1.4.11.Final > ----------------------------------- > > Key: WFCORE-1290 > URL: https://issues.jboss.org/browse/WFCORE-1290 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Radoslav Husar > Assignee: David Lloyd > > Change log https://issues.jboss.org/projects/JBMAR/versions/12329371 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6697) @PreDestroy beans not called when performing disable in domain mode

by Robert Smith (JIRA)

[ https://issues.jboss.org/browse/WFLY-6697?page=com.atlassian.jira.plugin.... ] Robert Smith edited comment on WFLY-6697 at 6/14/16 9:16 AM: ------------------------------------------------------------- Disable is an option from the web console under Deployments. For Standalone, go to the Deployments tab, select the deployment drop down menu and choose 'Disable'. For Domain, go to the Deployments tab, Server Groups/<server group deployed to>/deployment and choose 'Disable'. was (Author: rsmith1): Disable is an option from the web console under Deployments. > @PreDestroy beans not called when performing disable in domain mode > ------------------------------------------------------------------- > > Key: WFLY-6697 > URL: https://issues.jboss.org/browse/WFLY-6697 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 9.0.2.Final > Reporter: Robert Smith > Assignee: Brian Stansberry > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1098) Find better place / fix @ignored tests in core suite

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1098?page=com.atlassian.jira.plugi... ] Tomaz Cerar resolved WFCORE-1098. --------------------------------- Fix Version/s: 2.2.0.CR3 Resolution: Done > Find better place / fix @ignored tests in core suite > ---------------------------------------------------- > > Key: WFCORE-1098 > URL: https://issues.jboss.org/browse/WFCORE-1098 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 2.2.0.CR3 > > > tests that need revisiting and cleanup / moving stuff around: > org.wildfly.core.test.standalone.mgmt.api.ValidateOperationOperationTestCase > org.jboss.as.test.integration.management.http.HttpPostMgmtOpsTestCase#testAddRemoveOperation -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 June 2016