[jboss-jira] [JBoss JIRA] (WFLY-4520) Multi-JSF archive deploy fails with JBAS014746: steps may not be null

[Farah Juma (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060296#comment-13060296 ] 

Farah Juma commented on WFLY-4520:
----------------------------------

This error only seems to occur when using the CLI GUI. However, note that the new JSF implementation still gets installed successfully even though this error message occurs. To verify this, after seeing the error message, restart the server and execute the following CLI command:

{code}
/subsystem=jsf:list-active-jsf-impls()
{code}

You should see mojarra-1.2_15 in the output.

When the CLI GUI isn't used, the CLI archive deploys successfully, without any error messages, i.e., the following commands do work (verified this on Windows as well):

{code}
./bin/jboss-cli.sh --connect (for Windows, use .\bin\jboss-cli.bat --connect)
deploy install-mojarra-1.2_15.cli
{code}

I'm going to update this JIRA's title and description accordingly.

> Multi-JSF archive deploy fails with JBAS014746: steps may not be null
> ---------------------------------------------------------------------
>
>                 Key: WFLY-4520
>                 URL: https://issues.jboss.org/browse/WFLY-4520
>             Project: WildFly
>          Issue Type: Bug
>          Components: JSF
>    Affects Versions: 8.2.0.Final, 9.0.0.Beta2
>            Reporter: Paul Newport
>            Assignee: Farah Juma
>         Attachments: install-mojarra-1.2_15.cli
>
>
> Deploying a multi-jsf archive fails with a steps may not be null error
> deploy install-mojarra-1.2_15.cli
> {
>     "outcome" => "failed",
>     "failure-description" => "JBAS014746: steps may not be null",
>     "rolled-back" => true
> }



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)