[JBoss JIRA] (WFLY-8874) jmx: java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
by Bartosz Baranowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-8874?page=com.atlassian.jira.plugin.... ]
Bartosz Baranowski reassigned WFLY-8874:
----------------------------------------
Assignee: Bartosz Baranowski (was: Kabir Khan)
> jmx: java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
> ---------------------------------------------------------------
>
> Key: WFLY-8874
> URL: https://issues.jboss.org/browse/WFLY-8874
> Project: WildFly
> Issue Type: Bug
> Components: JMX
> Affects Versions: 10.1.0.Final
> Environment: java version "1.8.0_131"
> Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
> Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)
> ubuntu 17.04
> Reporter: Gaétan QUENTIN
> Assignee: Bartosz Baranowski
>
> Launching wildfly with these options:
> JAVA_OPTS='-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9010 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Xbootclasspath/p:/opt/wildfly-10.1.0.Final/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-1.4.0.Final.jar -Djboss.modules.system.pkgs=org.jboss.logmanager -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl '
> will result in this error:
> [Loaded org.jboss.as.server.Main from jar:file:/opt/wildfly-10.1.0.Final/modules/system/layers/base/org/jboss/as/server/main/wildfly-server-2.2.0.Final.jar!/]
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:505)
> Caused by: java.lang.ClassNotFoundException: org.jboss.logmanager.Level
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9303) Remove unused ServiceRefWithoutExplicitWsdlServletTestCase
by Jan Blizňák (JIRA)
[ https://issues.jboss.org/browse/WFLY-9303?page=com.atlassian.jira.plugin.... ]
Jan Blizňák moved JBEAP-13015 to WFLY-9303:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9303 (was: JBEAP-13015)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Test Suite
(was: Test Suite)
Affects Version/s: 11.0.0.CR1
(was: 7.1.0.CR1)
> Remove unused ServiceRefWithoutExplicitWsdlServletTestCase
> ----------------------------------------------------------
>
> Key: WFLY-9303
> URL: https://issues.jboss.org/browse/WFLY-9303
> Project: WildFly
> Issue Type: Task
> Components: Test Suite
> Affects Versions: 11.0.0.CR1
> Reporter: Jan Blizňák
> Assignee: Tomaz Cerar
> Priority: Minor
>
> As part of the check for ignored tests in our testsuite, ServiceRefWithoutExplicitWsdlServletTestCase was identified as an adept for removal. It was initially introduced for feature requested in WFLY-3262/WFLY-4026 but there is currently no plan for developing this feature thus it is safe remove it at this time. This jira will be linked to original feature request to be able to recover the test in case the feature is delivered.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9042) Missing spaces after EL expressions in JSP
by Bartosz Baranowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-9042?page=com.atlassian.jira.plugin.... ]
Bartosz Baranowski resolved WFLY-9042.
--------------------------------------
Resolution: Cannot Reproduce
Output in current WFLY master: "x y z"
> Missing spaces after EL expressions in JSP
> ------------------------------------------
>
> Key: WFLY-9042
> URL: https://issues.jboss.org/browse/WFLY-9042
> Project: WildFly
> Issue Type: Bug
> Environment: CentOS Linux 7.3.1611
> Reporter: Martin Švorc
> Assignee: Bartosz Baranowski
> Labels: el, el-expresion, jsp
> Attachments: example.zip
>
>
> Spaces are missing after EL expression in the output. For example the following
> {{${x} ${y} ${z}}} comes out as "xyz" (assuming the values bound to the variables are "x", "y", "z", respectively) or {{${x} text}} comes out as "xtext".
> The behaviour is the same on WF 10 and 11. Does not occur on Tomcat 7,8.
> The space is not present in the generated java class on WF and is present on Tomcat, so I assume the problem must be in the JSP parsing.
> My only lead so far is [this stackoverflow question|https://stackoverflow.com/questions/26988262/best-way-to-find-os...] back from '08.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9042) Missing spaces after EL expressions in JSP
by Bartosz Baranowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-9042?page=com.atlassian.jira.plugin.... ]
Bartosz Baranowski reassigned WFLY-9042:
----------------------------------------
Assignee: Bartosz Baranowski (was: Jason Greene)
> Missing spaces after EL expressions in JSP
> ------------------------------------------
>
> Key: WFLY-9042
> URL: https://issues.jboss.org/browse/WFLY-9042
> Project: WildFly
> Issue Type: Bug
> Environment: CentOS Linux 7.3.1611
> Reporter: Martin Švorc
> Assignee: Bartosz Baranowski
> Labels: el, el-expresion, jsp
> Attachments: example.zip
>
>
> Spaces are missing after EL expression in the output. For example the following
> {{${x} ${y} ${z}}} comes out as "xyz" (assuming the values bound to the variables are "x", "y", "z", respectively) or {{${x} text}} comes out as "xtext".
> The behaviour is the same on WF 10 and 11. Does not occur on Tomcat 7,8.
> The space is not present in the generated java class on WF and is present on Tomcat, so I assume the problem must be in the JSP parsing.
> My only lead so far is [this stackoverflow question|https://stackoverflow.com/questions/26988262/best-way-to-find-os...] back from '08.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ELY-1354) Increment WildFly Elytron schema version
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1354?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse commented on ELY-1354:
---------------------------------------
FYI this issue is for the authentication client schema within the Elytron project - bumping the subsystem schema and model is tracked under WFCORE-3234.
> Increment WildFly Elytron schema version
> ----------------------------------------
>
> Key: ELY-1354
> URL: https://issues.jboss.org/browse/ELY-1354
> Project: WildFly Elytron
> Issue Type: Task
> Components: Authentication Client
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.2.0.Beta3
>
>
> At the same time we need to review how we handle supporting multiple versions.
> On one hand we can look at making our parser fairly permissive so if we are just adding it can support both old and new, the biggest advantage here is we can minimise code duplication.
> The down side however is in the future it becomes very difficult to reverse and remove support for older schema.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ELY-1354) Increment WildFly Elytron schema version
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/ELY-1354?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar commented on ELY-1354:
----------------------------------
Completing the move to defined parsers would help with that.
most of that work is tracked under WFCORE-2882
> Increment WildFly Elytron schema version
> ----------------------------------------
>
> Key: ELY-1354
> URL: https://issues.jboss.org/browse/ELY-1354
> Project: WildFly Elytron
> Issue Type: Task
> Components: Authentication Client
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.2.0.Beta3
>
>
> At the same time we need to review how we handle supporting multiple versions.
> On one hand we can look at making our parser fairly permissive so if we are just adding it can support both old and new, the biggest advantage here is we can minimise code duplication.
> The down side however is in the future it becomes very difficult to reverse and remove support for older schema.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months