[jbosstools-issues] [JBoss JIRA] (JBIDE-25095) WildFly 11 runtime should add "wildfly-elytron-1.1.1.Final.jar" to build path

[Martin Malina (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-25095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina closed JBIDE-25095.
---------------------------------


Both modules are now added to the default classpath for both wf11 and eap 7.1. Verified in devstudio 11.1.0.AM3 B1225. Closing.

> WildFly 11 runtime should add "wildfly-elytron-1.1.1.Final.jar" to build path
> -----------------------------------------------------------------------------
>
>                 Key: JBIDE-25095
>                 URL: https://issues.jboss.org/browse/JBIDE-25095
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: server
>    Affects Versions: 4.5.0.Final
>            Reporter: Wolfgang Knauf
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: 4.5.1.AM3
>
>
> When a client app (e.g. a JavaEE application client) wants to perform a login to a WildFly 11 server, it has to either use a "wildfly-config.xml" file or add some code to setup security (see e.g. [Client authentication with Elytron client|https://docs.jboss.org/author/display/WFLY/Client+Authentication+with+Elytron+Client#ClientAuthenticationwithElytronClient-TheProgrammaticApproach] for a code snippet).
> To make this code compile, two jar files are required:
> %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\security\elytron-private\main\wildfly-elytron-1.1.1.Final.jar
> %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\common\main\wildfly-common-1.2.0.Final.jar
> I think the runtime should add them by default.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)