March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2950) jboss-cli using https-remoting: command not executed if certificate is unrecognised

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2950?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2950: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1026418|https://bugzilla.redhat.com/show_bug.cgi?id=1026418] from ON_QA to VERIFIED > jboss-cli using https-remoting: command not executed if certificate is unrecognised > ----------------------------------------------------------------------------------- > > Key: WFLY-2950 > URL: https://issues.jboss.org/browse/WFLY-2950 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CLI, Domain Management > Affects Versions: 8.0.0.Final > Environment: Windows 7 Pro > Reporter: Darren Jones > Assignee: Darran Lofthouse > Labels: cli, shutdown > Fix For: 8.0.1.Final > > > When using the https management interface from jboss-cli, commands passed with a command line option (such as --command=:shutdown) are not executed if the server certificate is unrecognised - even if accepting the certificate [T]emporarily or [P]ermenantly. > It appears to be due to the CommandContextImpl.handleSSLFailure() method, which calls error("Unable to connect..."). The error() method sets the exitCode to 1. So, when CliLauncher.processCommands() subsequently runs, it sees that the cmdCtx.exitCode is 1 and ignores any commands. > I guess the handleSSLFailure needs to reset the exitCode to 0 if the user chooses [T] or [P]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2538) Certificate acceptance causing command entered on starting the CLI to be skipped.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2538?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2538: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1026418|https://bugzilla.redhat.com/show_bug.cgi?id=1026418] from ON_QA to VERIFIED > Certificate acceptance causing command entered on starting the CLI to be skipped. > --------------------------------------------------------------------------------- > > Key: WFLY-2538 > URL: https://issues.jboss.org/browse/WFLY-2538 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CLI > Affects Versions: 8.0.0.Beta1 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > e.g. > {noformat} > ./jboss-cli.sh -c shutdown > Accept certificate? [N]o, [T]emporarily, [P]ermenantly : T > {noformat} > The shutdown command is not executed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3125) Update help text for add-user to reflect that password is checked against the configured policy.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3125?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3125: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1063888|https://bugzilla.redhat.com/show_bug.cgi?id=1063888] from ON_QA to VERIFIED > Update help text for add-user to reflect that password is checked against the configured policy. > ------------------------------------------------------------------------------------------------ > > Key: WFLY-3125 > URL: https://issues.jboss.org/browse/WFLY-3125 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3133) Misleading error message for add-user username requirements.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3133?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3133: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1062611|https://bugzilla.redhat.com/show_bug.cgi?id=1062611] from ON_QA to VERIFIED > Misleading error message for add-user username requirements. > ------------------------------------------------------------ > > Key: WFLY-3133 > URL: https://issues.jboss.org/browse/WFLY-3133 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > > The current error message is: - > {code} > JBAS015239: Only alpha/numeric usernames accepted. > {code} > However a small set of symbols are allowed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3130) Add a custom RuntimeException to add-user utility.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3130?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3130: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1062595|https://bugzilla.redhat.com/show_bug.cgi?id=1062595] from ON_QA to VERIFIED > Add a custom RuntimeException to add-user utility. > -------------------------------------------------- > > Key: WFLY-3130 > URL: https://issues.jboss.org/browse/WFLY-3130 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > > The add-user utility uses a RuntimeException to indicate failure in non-interactive mode, this does not look good so should switch it to a custom exception of our own. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-834) org.jboss.as.cmp dependency added only to EJB subdeployments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-834?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-834: ---------------------------------------------- James Livingston <jlivings(a)redhat.com> changed the Status of [bug 924548|https://bugzilla.redhat.com/show_bug.cgi?id=924548] from NEW to POST > org.jboss.as.cmp dependency added only to EJB subdeployments > ------------------------------------------------------------ > > Key: WFLY-834 > URL: https://issues.jboss.org/browse/WFLY-834 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Reporter: James Livingston > Assignee: jaikiran pai > > The CMP code adds a module dependency on org.jboss.as.cmp if there are any CMP beans in it (via the CMP marker). > If the <ejb-class> refers to a class not in the EJB jar itself, such as in a library jar, this will result in the proxy being created in the EAR classloader and not being able to find JBoss' CmpProxy class. > The solution is to add the dependency to the top-level deployment so it is available in all sub-deployments, rather than the such the ejb subdeployment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3189) Error validating jboss-ejb3.xml.

by shinzey shinzey (JIRA)

shinzey shinzey created WFLY-3189: ------------------------------------- Summary: Error validating jboss-ejb3.xml. Key: WFLY-3189 URL: https://issues.jboss.org/browse/WFLY-3189 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB Affects Versions: 8.0.0.Final Environment: WildFly 8.0.0.Final Reporter: shinzey shinzey Assignee: David Lloyd I'm trying to configure code completion for jboss-ejb3.xml with schema, but fail to do that due to the following validation error: {noformat} src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' to a(n) 'type definition' component. [33] src-resolve: Cannot resolve the name 'javaee:jboss-ejb-jarType' to a(n) 'type definition' component. [35] src-resolve: Cannot resolve the name 'javaee:jboss-enterprise-beansType' to a(n) 'type definition' component. [37] src-resolve: Cannot resolve the name 'javaee:assembly-descriptor-entry' to a(n) 'element declaration' component. [35] src-resolve: Cannot resolve the name 'javaee:jboss-assembly-descriptor-bean-entryType' to a(n) 'type definition' component. [39] {noformat} The jboss-ejb3.xml is quite simple: {code:xml} <?xml version="1.0" encoding="UTF-8"?> <jboss:ejb-jar version="3.1" impl-version="2.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns:s="urn:security:1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd"> <assembly-descriptor> <s:security> <ejb-name>*</ejb-name> <s:security-domain>testsd</s:security-domain> </s:security> </assembly-descriptor> </jboss:ejb-jar> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-424) drools-camel support for session-scoped knowledge session

by Damon Horrell (JIRA)

[ https://issues.jboss.org/browse/DROOLS-424?page=com.atlassian.jira.plugin... ] Damon Horrell commented on DROOLS-424: -------------------------------------- If anyone is looking for a server for drools with a session-scoped knowledge session then you can use: http://anonsvn.jboss.org/repos/tohu/trunk/tohu/tohu-xml/src/main/java/org... This is part of the Tohu project but there is nothing Tohu-specific about it so it could be easily adapted for other purposes. It uses the CommandExecutor but currently only supports request/responses in XML format. > drools-camel support for session-scoped knowledge session > --------------------------------------------------------- > > Key: DROOLS-424 > URL: https://issues.jboss.org/browse/DROOLS-424 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 5.6.0.Final > Reporter: Damon Horrell > Assignee: Mark Proctor > > The Spring configuration for drools-camel allows creation of either a stateless knowledge session (i.e. effectively request-scoped), or a single stateful knowledge session which is shared by all requests (i.e. effectively application-scoped). There is no session-scoped option. > This differs from the earlier drools-execution-server module (version 0.0.4) which was replaced by drools-camel. drools-execution-server maintained a separate StatefulKnowledgeSession instance per HTTP session. > Can you please add support for a session-scoped StatefulKnowledgeSession? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3118) <vault> does not have module option

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3118?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-3118. ---------------------------- Resolution: Done > <vault> does not have module option > ----------------------------------- > > Key: WFLY-3118 > URL: https://issues.jboss.org/browse/WFLY-3118 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Security > Reporter: Derek Horton > Assignee: Kabir Khan > > The <vault> element in standalone/domain.xml takes a 'code' attribute specifying the class to use as the implementation. It does not let you specify a 'module' option like most similar elements have, and instead always loads the class from the org.picketbox module. > The <vault> element should take a module option too. > The current workaround is to add the custom vault module as a dependency in the org.picketbox module. > Additionally, hanging any module.xml can also result in patching conflicts when customers apply future updates. > Since we have a quite a few customers writing custom vault implementations for various pieces of functionality that it doesn't provide out of the box, we should consider making this type of customer-initiated change patch safe for customers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3158) @Model does not work

by Stefan Dilk (JIRA)

[ https://issues.jboss.org/browse/WFLY-3158?page=com.atlassian.jira.plugin.... ] Stefan Dilk commented on WFLY-3158: ----------------------------------- but in glassfish 4 this works. i mean glassfish uses weld too, so i think it is a bug in wildfly. please correct me if i go wrong. > @Model does not work > -------------------- > > Key: WFLY-3158 > URL: https://issues.jboss.org/browse/WFLY-3158 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: CDI / Weld, JSF > Affects Versions: 8.0.0.Final > Reporter: Stefan Dilk > Assignee: Jozef Hartinger > > hi, > wildfly not work with @Model annotated beans in JSF. > @RequestScoped and @Named work. > in this ticket it is already reported, but closed: > https://issues.jboss.org/browse/WFLY-2372 > in the related CDI ticket the change is made, so please implement this in the next wildfly update. in glassfish4 the @Model annotation works fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2014