February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3576) deployment is not accessible in runtime when deployed with runtime-name not using .war extension

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3576?page=com.atlassian.jira.plugi... ] Chao Wang moved JBEAP-13814 to WFCORE-3576: ------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3576 (was: JBEAP-13814) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Deployment Scanner Domain Management (was: Domain Management) (was: User Experience) Target Release: (was: 7.backlog.GA) Affects Version/s: 4.0.0.Alpha9 (was: 7.0.8.GA) (was: 7.1.0.CR4) > deployment is not accessible in runtime when deployed with runtime-name not using .war extension > ------------------------------------------------------------------------------------------------ > > Key: WFCORE-3576 > URL: https://issues.jboss.org/browse/WFCORE-3576 > Project: WildFly Core > Issue Type: Enhancement > Components: Deployment Scanner, Domain Management > Affects Versions: 4.0.0.Alpha9 > Reporter: Jan Stourac > Assignee: Chao Wang > > According to the folowing [blog-post|https://developer.jboss.org/thread/221251], when using custom --name or --runtime-name for deployment, the file extension (.war, .jar, .ear,...) need to be included so server can distinguish type of deployment somehow. > Currently there is no such check - when I try to deploy any .war app using either web-console or CLI with my custom '\-\-runtime-name' and/or '\-\-name' without .war suffix, server does not complain anyhow: > {code} > deploy --runtime-name=alice --name=bob /tmp/eve.war > {code} > Message in server log: > {code} > 17:30:48,469 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "bob" (runtime-name: "alice") > 17:30:48,499 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0010: Deployed "bob" (runtime-name : "alice") > {code} > Although, when I try to access content of the war app via URL, I get only {{404 Not found}} HTTP response. Also I cannot see any deployment content when browsing via CLI: > {code} > /deployment=bob/subsystem=undertow/... > {code} > Even when I raise logging level to DEBUG, I can see no suspicious messages that deployed app has not been completely deployed. > If such suffix is required, we need to inform user about it. We need to update description text for '\-\-name' and '\-\-runtime-name' atributes of deploy command in CLI (see {{deploy --help}}). Also when no such suffix is provided (and/or we fail to distinguish type of deployment in a different way) we need to print error message that deploy operation was not completely successful so customer is aware of it right-away. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2304) [DMN Designer] Add context entry from literal expression cell

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2304: ----------------------------------- Summary: [DMN Designer] Add context entry from literal expression cell Key: DROOLS-2304 URL: https://issues.jboss.org/browse/DROOLS-2304 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.6.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Priority: Minor If the context entry is specified as literal expression, then user can not add context entry while this literal expression cell is selected. It can be seen in the last row of context entry table, where last entry is pair *default : literal expression cell*. If user clicks on *default*, the table offers show button *add entry* over the table, however if user clicks to *literal expression cell* next to *default* this button is not shown. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2303) [DMN Designer] Add column to whole row outline

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2303: ----------------------------------- Summary: [DMN Designer] Add column to whole row outline Key: DROOLS-2303 URL: https://issues.jboss.org/browse/DROOLS-2303 Project: Drools Issue Type: Enhancement Components: DMN Editor Affects Versions: 7.6.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Priority: Minor Currently, if the user has outlined whole row of the decision table, and new column is added to this decision table, the new column is not added to the outline. This could be enhanced not just for decision tables but in general, if there is outlined whole row of decision table, relation etc., then adding new column in the given editor should cause new column is included in the current outline. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2302) [DMN Designer] Outline is not refreshed after new editor type selected

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2302: ----------------------------------- Summary: [DMN Designer] Outline is not refreshed after new editor type selected Key: DROOLS-2302 URL: https://issues.jboss.org/browse/DROOLS-2302 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.6.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Priority: Minor If the context entry table has at least two rows where: # first row is selected (outline is shown) and the editor type is specified (decision table for example) # second row has not the editor type specified (6 blue squares shown in that row) Then if user clicks on some of these blue squares, the outline should be refreshed to overlap the last added cell / editor. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2302) [DMN Designer] Outline is not refreshed after new editor type selected

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2302?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2302: -------------------------------- Description: If the context entry table has at least two rows where: # first row is selected (outline is shown) and the editor type is specified (decision table for example) # second row has not the editor type specified (6 blue squares shown in that row) Then if user clicks on some of these blue squares, the outline should be refreshed to overlap the last added cell / editor. was: If the context entry table has at least two rows where: # first row is selected (outline is shown) and the editor type is specified (decision table for example) # second row has not the editor type specified (6 blue squares shown in that row) Then if user clicks on some of these blue squares, the outline should be refreshed to overlap the last added cell / editor. > [DMN Designer] Outline is not refreshed after new editor type selected > ---------------------------------------------------------------------- > > Key: DROOLS-2302 > URL: https://issues.jboss.org/browse/DROOLS-2302 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > > If the context entry table has at least two rows where: > # first row is selected (outline is shown) and the editor type is specified (decision table for example) > # second row has not the editor type specified (6 blue squares shown in that row) > Then if user clicks on some of these blue squares, the outline should be refreshed to overlap the last added cell / editor. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3555) Pipe with echo command gives incorrect result

by Martin Stefanko (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3555?page=com.atlassian.jira.plugi... ] Martin Stefanko updated WFCORE-3555: ------------------------------------ Summary: Pipe with echo command gives incorrect result (was: Pipe with echo commad gives incorrect result) > Pipe with echo command gives incorrect result > --------------------------------------------- > > Key: WFCORE-3555 > URL: https://issues.jboss.org/browse/WFCORE-3555 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Katerina Novotna > Assignee: Martin Stefanko > > *Description of problem:* > When putting 'echo' into the right side of the pipe. Addional 'o' is displayed as result. > *Actual results:* > [standalone@embedded /] version | echo test > o test > *Expected results:* > [standalone@embedded /] version | echo test > test -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-482) Add log4j2 support for WildFly

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-482?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-482: ------------------------------------ Fix Version/s: 4.0.0.Beta1 (was: 4.0.0.Alpha9) > Add log4j2 support for WildFly > ------------------------------ > > Key: WFCORE-482 > URL: https://issues.jboss.org/browse/WFCORE-482 > Project: WildFly Core > Issue Type: Task > Components: Logging > Environment: Spring 3, Hibernate, Wicket, JBoss AS7 > Reporter: Amarkanth Ranganamayna > Assignee: James Perkins > Priority: Optional > Fix For: 4.0.0.Beta1 > > > I am trying to use Flume Appender which comes with Log4j2 (log4j 1.x doesn't support flume appender) (AND) inorder to acheive this, I am looking at how to configure JBoss AS7 to use log4j2. > Looks like Jboss AS7 by default use log4j 1.x > Are you guys already working on using log4j2 ? > If NOT, can you please suggest how to configure Jboss AS7 such that it picks up "log4j2.xml" file and doesn't use its own logging. > Thanks, > Amar -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-456) Add a content-stream attribute to the root deployment=* resources

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-456?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-456: ------------------------------------ Fix Version/s: 4.0.0.Beta1 (was: 4.0.0.Alpha9) > Add a content-stream attribute to the root deployment=* resources > ----------------------------------------------------------------- > > Key: WFCORE-456 > URL: https://issues.jboss.org/browse/WFCORE-456 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Fix For: 4.0.0.Beta1 > > > Add a new attribute to the deployment resource that allows the user to get a stream with the deployment content attached to the response, a la what we do with the subsystem=logging/log-file=* resource's "stream" attribute. > The attribute must be configured as runtime-only and read-only. > The read handler that handles the attribute should only attach a stream if the following conditions are met, otherwise the value for the attribute should remain as 'undefined'. > 1) The resource's "content" attribute has only a single element in the list. (This is always the case today; adding a check for this is just future proofing) > 2) The first element in the "content" attribute list has a defined value in its "hash" field. (This confirms the content is stored in the content repo. We won't support serving unmanaged content as we have insufficient control over it.) > 3) The first element in the "content" attribute list has a 'true' as value of its "archive" field. (Current this will always be the case; this is future proofing for when we add support for exploded content in the content repo. Trying to assemble a stream from exploded content is currently out of scope for this feature.) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-377) The management API should provide a command to restart only all servers that are in state 'reload-required'

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-377?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-377: ------------------------------------ Fix Version/s: 4.0.0.Beta1 (was: 4.0.0.Alpha9) > The management API should provide a command to restart only all servers that are in state 'reload-required' > ----------------------------------------------------------------------------------------------------------- > > Key: WFCORE-377 > URL: https://issues.jboss.org/browse/WFCORE-377 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Wolf-Dieter Fink > Labels: cli, domain, domain-mode, management > Fix For: 4.0.0.Beta1 > > > After configuration changes via CLI batch it might be that different processes needs to be restarted. > It is possible to iterate over all servers and check it. > But I think it would be easier to have a command that restart all controllers and servers conditional to the 'relod required' state > - at domain level > - at host level > - at server level > command example : > :restart(ifRequired=true) > :reload(ifRequired=true) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-185) Api returns internal server error instead of not found for non-existing path

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-185?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-185: ------------------------------------ Fix Version/s: 4.0.0.Beta1 (was: 4.0.0.Alpha9) > Api returns internal server error instead of not found for non-existing path > ---------------------------------------------------------------------------- > > Key: WFCORE-185 > URL: https://issues.jboss.org/browse/WFCORE-185 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Rupp > Assignee: Brian Stansberry > Labels: domain-mode, rhq > Fix For: 4.0.0.Beta1 > > > When I try to e.g. /subsystem=foo:read-resource the api returns a 500 internal server error. > In http-land, the return code for "not found" is normally 404. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 February 2018