September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-90) don't require escaping special characters where they are not expected in argument values

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFCORE-90: --------------------------------------- Summary: don't require escaping special characters where they are not expected in argument values Key: WFCORE-90 URL: https://issues.jboss.org/browse/WFCORE-90 Project: WildFly Core Issue Type: Feature Request Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Besides having this feature in place being nice in general, it will help avoid confusions in some cases and will make determining the problem with the parsed command line easier. Examples of special characters in argument values are: {, [, =. Each of these is a legal character in a value by itself. But the CLI reacts to them differently: { is a beginning of a DMR OBJECT value; [ is beginning of a DMR LIST value; = is a name value separator. The same for the corresponding closing } and ]. At the moment the CLI parsing is not smart enough and requires escaping {, }, [, ] and = if they have to be a part of the value. This feature request is to make the parsing a bit smarter by taking into account the context where these characters appear and require escaping them in places where they obviously don't have the special meaning. E.g. { and [ are significant from the parsing point of few if they appear at the very beginning, i.e. before the parameter value, not in the middle. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3827) Update Subsystem for PicketLink Console

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFLY-3827?page=com.atlassian.jira.plugin.... ] Pedro Igor updated WFLY-3827: ----------------------------- Affects Version/s: 9.0.0.Beta1 (was: 8.1.0.Final) > Update Subsystem for PicketLink Console > --------------------------------------- > > Key: WFLY-3827 > URL: https://issues.jboss.org/browse/WFLY-3827 > Project: WildFly > Issue Type: Enhancement > Components: Security > Affects Versions: 9.0.0.Beta1 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3534) Transaction is not being shared by different operations within the same thread

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFLY-3534?page=com.atlassian.jira.plugin.... ] Pedro Igor resolved WFLY-3534. ------------------------------ Fix Version/s: 9.0.0.Beta1 Resolution: Done > Transaction is not being shared by different operations within the same thread > ------------------------------------------------------------------------------ > > Key: WFLY-3534 > URL: https://issues.jboss.org/browse/WFLY-3534 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 9.0.0.Beta1 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 9.0.0.Beta1 > > > When injecting a JPA-based PartitionManager configuration in a EJB as follows: > {code} > @Resource(mappedName = "picketlink/JPADSBasedPartitionManager") > private PartitionManager jpaDSBasedPartitionManager; > {code} > The IDM operations are executed without share the same EntityManager instance. This causes some strange behaviors such as not being able to retrieve data stored from a previous operation during a method execution. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3827) Update Subsystem for PicketLink Console

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFLY-3827?page=com.atlassian.jira.plugin.... ] Pedro Igor updated WFLY-3827: ----------------------------- Fix Version/s: 9.0.0.Beta1 > Update Subsystem for PicketLink Console > --------------------------------------- > > Key: WFLY-3827 > URL: https://issues.jboss.org/browse/WFLY-3827 > Project: WildFly > Issue Type: Enhancement > Components: Security > Affects Versions: 8.1.0.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3827) Update Subsystem for PicketLink Console

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFLY-3827?page=com.atlassian.jira.plugin.... ] Pedro Igor updated WFLY-3827: ----------------------------- Affects Version/s: 8.1.0.Final > Update Subsystem for PicketLink Console > --------------------------------------- > > Key: WFLY-3827 > URL: https://issues.jboss.org/browse/WFLY-3827 > Project: WildFly > Issue Type: Enhancement > Components: Security > Affects Versions: 8.1.0.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3534) Transaction is not being shared by different operations within the same thread

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFLY-3534?page=com.atlassian.jira.plugin.... ] Pedro Igor reassigned WFLY-3534: -------------------------------- Assignee: Pedro Igor (was: Darran Lofthouse) > Transaction is not being shared by different operations within the same thread > ------------------------------------------------------------------------------ > > Key: WFLY-3534 > URL: https://issues.jboss.org/browse/WFLY-3534 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 9.0.0.Beta1 > Reporter: Pedro Igor > Assignee: Pedro Igor > > When injecting a JPA-based PartitionManager configuration in a EJB as follows: > {code} > @Resource(mappedName = "picketlink/JPADSBasedPartitionManager") > private PartitionManager jpaDSBasedPartitionManager; > {code} > The IDM operations are executed without share the same EntityManager instance. This causes some strange behaviors such as not being able to retrieve data stored from a previous operation during a method execution. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-122) Clean unreferenced items from the content repository

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-122?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on WFLY-122: --------------------------------------- Yes, the solution will be something like that, although I don't want it as blocking part of boot (we highly value boot time) but rather a side task kicked off during boot. Emmanuel Hugonnet is working on this; he's working on a related Bugzilla and I just saw now he wasn't assigned to this JIRA. I just updated the title and description a bit to highlight the fact that this isn't just about deployments. > Clean unreferenced items from the content repository > ---------------------------------------------------- > > Key: WFLY-122 > URL: https://issues.jboss.org/browse/WFLY-122 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Fix For: 9.0.0.CR1 > > > The algorithm for removing unused deployments from the content repository is based on doing this as part of undeploy operation execution. This doesn't cover cases where the content is never explicitly undeployed. For example: > 1) Scanner content that is updated when the server is offline; the old content will not have been "undeployed" during shutdown, and on startup the new content will be installed. > 2) Similar issues with deployments generated from module resources (see "A Mixed Approach on https://community.jboss.org/wiki/ExtendingAS7). When the server shuts down, there is no "subsystem remove" as part of shutdown, so the content added during start will not be removed. > Note that the content repository can include things other than deployments. Currently it also includes management-client-content (specifically rollout plans) and can potentially include anything. This is why it's a "content repository" and not a "deployment repository." The solution for this needs to deal with all cases. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-122) Clean unreferenced items from the content repository

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-122?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-122: ---------------------------------- Assignee: Emmanuel Hugonnet > Clean unreferenced items from the content repository > ---------------------------------------------------- > > Key: WFLY-122 > URL: https://issues.jboss.org/browse/WFLY-122 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Fix For: 9.0.0.CR1 > > > The algorithm for removing unused deployments from the content repository is based on doing this as part of undeploy operation execution. This doesn't cover cases where the content is never explicitly undeployed. For example: > 1) Scanner content that is updated when the server is offline; the old content will not have been "undeployed" during shutdown, and on startup the new content will be installed. > 2) Similar issues with deployments generated from module resources (see "A Mixed Approach on https://community.jboss.org/wiki/ExtendingAS7). When the server shuts down, there is no "subsystem remove" as part of shutdown, so the content added during start will not be removed. > Note that the content repository can include things other than deployments. Currently it also includes management-client-content (specifically rollout plans) and can potentially include anything. This is why it's a "content repository" and not a "deployment repository." The solution for this needs to deal with all cases. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-122) Clean unreferenced items from the content repository

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-122?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-122: ---------------------------------- Description: The algorithm for removing unused deployments from the content repository is based on doing this as part of undeploy operation execution. This doesn't cover cases where the content is never explicitly undeployed. For example: 1) Scanner content that is updated when the server is offline; the old content will not have been "undeployed" during shutdown, and on startup the new content will be installed. 2) Similar issues with deployments generated from module resources (see "A Mixed Approach on https://community.jboss.org/wiki/ExtendingAS7). When the server shuts down, there is no "subsystem remove" as part of shutdown, so the content added during start will not be removed. Note that the content repository can include things other than deployments. Currently it also includes management-client-content (specifically rollout plans) and can potentially include anything. This is why it's a "content repository" and not a "deployment repository." The solution for this needs to deal with all cases. was: The algorithm for removing unused deployments from the content repository is based on doing this as part of undeploy operation execution. This doesn't cover cases where the content is never explicitly undeployed. For example: 1) Scanner content that is updated when the server is offline; the old content will not have been "undeployed" during shutdown, and on startup the new content will be installed. 2) Similar issues with deployments generated from module resources (see "A Mixed Approach on https://community.jboss.org/wiki/ExtendingAS7). When the server shuts down, there is no "subsystem remove" as part of shutdown, so the content added during start will not be removed. > Clean unreferenced items from the content repository > ---------------------------------------------------- > > Key: WFLY-122 > URL: https://issues.jboss.org/browse/WFLY-122 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 9.0.0.CR1 > > > The algorithm for removing unused deployments from the content repository is based on doing this as part of undeploy operation execution. This doesn't cover cases where the content is never explicitly undeployed. For example: > 1) Scanner content that is updated when the server is offline; the old content will not have been "undeployed" during shutdown, and on startup the new content will be installed. > 2) Similar issues with deployments generated from module resources (see "A Mixed Approach on https://community.jboss.org/wiki/ExtendingAS7). When the server shuts down, there is no "subsystem remove" as part of shutdown, so the content added during start will not be removed. > Note that the content repository can include things other than deployments. Currently it also includes management-client-content (specifically rollout plans) and can potentially include anything. This is why it's a "content repository" and not a "deployment repository." The solution for this needs to deal with all cases. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-122) Clean unreferenced items from the content repository

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-122?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-122: ---------------------------------- Summary: Clean unreferenced items from the content repository (was: Clean unreferenced deployments from the content repository) > Clean unreferenced items from the content repository > ---------------------------------------------------- > > Key: WFLY-122 > URL: https://issues.jboss.org/browse/WFLY-122 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 9.0.0.CR1 > > > The algorithm for removing unused deployments from the content repository is based on doing this as part of undeploy operation execution. This doesn't cover cases where the content is never explicitly undeployed. For example: > 1) Scanner content that is updated when the server is offline; the old content will not have been "undeployed" during shutdown, and on startup the new content will be installed. > 2) Similar issues with deployments generated from module resources (see "A Mixed Approach on https://community.jboss.org/wiki/ExtendingAS7). When the server shuts down, there is no "subsystem remove" as part of shutdown, so the content added during start will not be removed. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

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 September 2014