[JBoss JIRA] (WFLY-9310) Class loading hierarchie
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-9310?page=com.atlassian.jira.plugin.... ]
David Lloyd updated WFLY-9310:
------------------------------
Attachment: (was: image-2017-09-07-12-57-59-849.png)
> Class loading hierarchie
> -------------------------
>
> Key: WFLY-9310
> URL: https://issues.jboss.org/browse/WFLY-9310
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading, JPA / Hibernate
> Affects Versions: 10.1.0.Final
> Environment: windows 7
> oracle jdk hotspot 8
> wildfly 10 final
> Reporter: stefano canu
> Assignee: David Lloyd
>
> Deployng an EAR application with hibernate 4.x jars in lib folders but is ignored and workning with AS module (hibernate 5.0.10) . i tried to do module exclusion by using jboss-deployment- structure but whitout any luck.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3264) add i18n to the CLI
by Kabir Khan (JIRA)
Kabir Khan created WFCORE-3264:
----------------------------------
Summary: add i18n to the CLI
Key: WFCORE-3264
URL: https://issues.jboss.org/browse/WFCORE-3264
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Affects Versions: 3.0.1.Final
Reporter: Martin Stefanko
Assignee: Jean-Francois Denise
Priority: Optional
Introduce i18n in the CLI subsystem. This could possibly include messages printed by the console and help description.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3263) add i18n to the CLI
by Martin Stefanko (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3263?page=com.atlassian.jira.plugi... ]
Martin Stefanko updated WFCORE-3263:
------------------------------------
Description: Introduce i18n in the CLI subsystem. This could possibly include messages printed by the console and help description. (was: Introduce i18n in the CLI subsystem. This could possibly include only messages printed by the console or full i18n including user commands (if possible).)
> add i18n to the CLI
> -------------------
>
> Key: WFCORE-3263
> URL: https://issues.jboss.org/browse/WFCORE-3263
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI
> Affects Versions: 3.0.1.Final
> Reporter: Martin Stefanko
> Assignee: Jean-Francois Denise
> Priority: Optional
>
> Introduce i18n in the CLI subsystem. This could possibly include messages printed by the console and help description.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-2408) Description of Elytron oauth2-introspection resource is copy/pasted from jwt
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2408?page=com.atlassian.jira.plugi... ]
Ilia Vassilev closed WFCORE-2408.
---------------------------------
Fix Version/s: 3.0.0.Beta8
Resolution: Out of Date
> Description of Elytron oauth2-introspection resource is copy/pasted from jwt
> ----------------------------------------------------------------------------
>
> Key: WFCORE-2408
> URL: https://issues.jboss.org/browse/WFCORE-2408
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta7
> Reporter: Ondrej Lukas
> Assignee: Ilia Vassilev
> Labels: user_experience
> Fix For: 3.0.0.Beta8
>
>
> Description of {{oauth2-introspection}} resource from Elytron {{token-realm}} is copy/pasted from description of {{jwt}}.
> It is similar as WFLY-7573, but its description (and also its linked fix) talks only about description of attributes. This Jira is related to description of whole resource which currently says:
> "A token validator to be used in conjunction with a token-based realm that handles security tokens based on the JWT/JWS standard."
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3263) add i18n to the CLI
by Martin Stefanko (JIRA)
Martin Stefanko created WFCORE-3263:
---------------------------------------
Summary: add i18n to the CLI
Key: WFCORE-3263
URL: https://issues.jboss.org/browse/WFCORE-3263
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Affects Versions: 3.0.1.Final
Reporter: Martin Stefanko
Priority: Optional
Introduce i18n in the CLI subsystem. This could possibly include only messages printed by the console or full i18n including user commands (if possible).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9314) Upgrade JBeret to 1.2.5.Final
by Cheng Fang (JIRA)
[ https://issues.jboss.org/browse/WFLY-9314?page=com.atlassian.jira.plugin.... ]
Cheng Fang edited comment on WFLY-9314 at 9/8/17 7:44 AM:
----------------------------------------------------------
the best way to stay current is to use latest WildFly releases, which includes the latest stable jberet-core module. If you want to drop in a more recent version of jberet-core into your WildFly installation, you are doing it at your own risk, and it may or may not work as expected, depending on the versions of WildFly and JBeret. There are some structural or spi changes in various versions of WildFly and JBeret that are incompatible with previous versions.
For developers, you can look at the commits between 2 JBeret versions and decide if a newer jberet-core may work.
https://github.com/jberet/jsr352/commits/1.2.x?before=53335ea19993adf220f...
For instance, JBeret 1.2.2 work spans from 6/26/2016 to 12/13/2016, and includes some api changes, so I don't think 1.2.2 will work with WildFly 10.1.
WildFly 11 currently contains jberet-core 1.2.4.Final, and replacing it with jberet-core 1.2.5.Final should just work as well.
Currently there is no plan to upgrade jberet-core in WildFly 11.
was (Author: cfang):
the best way to stay current is to use latest WildFly releases, which includes the latest stable jberet-core module. If you want to drop in a more recent version of jberet-core into your WildFly installation, you are doing it at your own risk, and it may or may not work as expected, depending on the versions of WildFly and JBeret. There are some structural or spi changes in various versions of WildFly and JBeret that are incompatible with previous versions.
For developers, you can look at the commits between 2 JBeret versions and decide if a newer jberet-core may work.
https://github.com/jberet/jsr352/commits/1.2.x?before=53335ea19993adf220f...
For instance, JBeret 1.2.2 work spans from 6/26/2016 to 12/13/2016, and includes some api changes, so I don't think 1.2.2 will work with WildFly 10.1.
> Upgrade JBeret to 1.2.5.Final
> -----------------------------
>
> Key: WFLY-9314
> URL: https://issues.jboss.org/browse/WFLY-9314
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Batch
> Reporter: Leandro Kersting de Freitas
> Assignee: Cheng Fang
> Fix For: 11.0.0.Final
>
>
> https://issues.jboss.org/projects/JBERET/versions/12335093
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months