February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9788) EJB over HTTP fails with Arrays in Request

by Heiko Lettmann (JIRA)

[ https://issues.jboss.org/browse/WFLY-9788?page=com.atlassian.jira.plugin.... ] Heiko Lettmann updated WFLY-9788: --------------------------------- Summary: EJB over HTTP fails with Arrays in Request (was: EJB over HTTP fails...) > EJB over HTTP fails with Arrays in Request > ------------------------------------------ > > Key: WFLY-9788 > URL: https://issues.jboss.org/browse/WFLY-9788 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Final > Reporter: Heiko Lettmann > Priority: Blocker > Attachments: Test.zip > > > I stumbled over the issue WFLY-9573. Then I updated to wildfly-http-client-1.0.9.Final which made a few invocations work. There I discovered another issue. I attached a modified Quickstart version to demonstrate it! > Exception is on the client side: > Exception in thread "main" javax.ejb.EJBException: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String > at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:128) > at org.wildfly.httpclient.ejb.HttpInvocationHandler.lambda$handleInternal$0(HttpInvocationHandler.java:130) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.io.IOException: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String > at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:204) > at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:126) > ... 4 more > Caused by: java.lang.ClassCastException: java.lang.Class cannot be cast to java.lang.String > at org.wildfly.httpclient.ejb.HttpInvocationHandler$1.getRequestContent(HttpInvocationHandler.java:178) > ... 5 more -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3273) sharedState is passed null by PluginAuthenticationCallbackHandler

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3273?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-3273: ------------------------------------------------- Sandro Bonazzola <sbonazzo(a)redhat.com> changed the Status of [bug 1490383|https://bugzilla.redhat.com/show_bug.cgi?id=1490383] from VERIFIED to CLOSED > sharedState is passed null by PluginAuthenticationCallbackHandler > ----------------------------------------------------------------- > > Key: WFCORE-3273 > URL: https://issues.jboss.org/browse/WFCORE-3273 > Project: WildFly Core > Issue Type: Bug > Components: Security > Environment: Fedora 26, using ovirt-engine-wildfly package > Reporter: Roy Golan > Assignee: Darran Lofthouse > Fix For: 3.0.2.Final, 4.0.0.Alpha1 > > > oVirt's ovirt-engine uses an authentication plugin [1] for management interface that recently after upgrading to Wildfly 11 stopped working. The reason is the sharedState passed to the plugin's init method is now null. > A current workaround this would be to avoid adding the plugin into the shareState, but that means any delegating plugin would fail to find this plugin and possibly other bad stuff I'm not aware of. > [1] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=backend/manag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-34) Use the same groupId:artifactId[:type[:classifier[:version]]] format everywhere

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-34?page=com.atlassian.jira.plugin... ] Peter Palaga commented on WFBUILD-34: ------------------------------------- These two locations in Maven codebase seem to be the most prominent and they use the {{groupId:artifactId\[:type\[:classifier\[:version]]]}} order: https://github.com/apache/maven-resolver/blob/master/maven-resolver-api/s... https://github.com/apache/maven/blob/master/maven-artifact/src/main/java/... > Use the same groupId:artifactId[:type[:classifier[:version]]] format everywhere > ------------------------------------------------------------------------------- > > Key: WFBUILD-34 > URL: https://issues.jboss.org/browse/WFBUILD-34 > Project: WildFly Build Tools > Issue Type: Enhancement > Reporter: Peter Palaga > Assignee: Stuart Douglas > Fix For: 1.2.8.Final > > > This both a usability issue and a feature request. > On the usability side, the artifact formats in module.xml files vs. in feature-pack-build.xml files are not the same: > * `{{groupId:artifactId\[:version\[:classifier]]}}` in module.xml files > * `{{groupId:artifactId\[:type\[:classifier]]}}` in feature-pack-build.xml files > The missing feature is the impossibility to define type/extension in module.xml files and the impossibility to had code version in feature-pack-build.xml files > The current proposal is to use the same {{groupId:artifactId\[:type\[:classifier\[:version]]]}} format in both kinds of files. > The proposal is backwards incompatible for module.xml files. But given that the support for hardcoded versions in module.xml files was added just 11 days ago, this will probably impact just a few users. > I am not sure what artifact format is used by JBoss modules. Maybe `{{groupId:artifactId\[:version\[:classifier]]}}` is taken from there? > WDYT [~swd847]? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9128) Upgrade to JAXB 2.3 / JBossWS 5.2 / CXF 3.2

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-9128?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated WFLY-9128: ---------------------------------- Description: Upgrade to JAXB 2.3 / JBossWS 5.2 / CXF 3.2 (was: Upgrade Apache CXF to 3.1.13. ) > Upgrade to JAXB 2.3 / JBossWS 5.2 / CXF 3.2 > ------------------------------------------- > > Key: WFLY-9128 > URL: https://issues.jboss.org/browse/WFLY-9128 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Ivo Studensky > Assignee: Alessio Soldano > Labels: downstream_dependency > Fix For: 12.0.0.Alpha1 > > > Upgrade to JAXB 2.3 / JBossWS 5.2 / CXF 3.2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9128) Upgrade to JAXB 2.3 / JBossWS 5.2 / CXF 3.2

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-9128?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated WFLY-9128: ---------------------------------- Comment: was deleted (was: A comment with security level 'Red Hat Employee' was removed.) > Upgrade to JAXB 2.3 / JBossWS 5.2 / CXF 3.2 > ------------------------------------------- > > Key: WFLY-9128 > URL: https://issues.jboss.org/browse/WFLY-9128 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Ivo Studensky > Assignee: Alessio Soldano > Labels: downstream_dependency > Fix For: 12.0.0.Alpha1 > > > Upgrade Apache CXF to 3.1.13. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6460) JSON-P 1.1 Support

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-6460?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on WFLY-6460: ----------------------------------------- {quote} I don't really know anything about the Automatic-Module-Name stuff. I just renamed what Tomaz Cerar had there. Maybe he can explain that part a bit. {quote} My comment is just reference for the future to keep EE8 and Java 9 stuff in separate commits if possible. > JSON-P 1.1 Support > ------------------ > > Key: WFLY-6460 > URL: https://issues.jboss.org/browse/WFLY-6460 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: David Lloyd > Assignee: James Perkins > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2318) Create a generative test suite to test ItemDefinition dependency sorting algorithm

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-2318: -------------------------------------- Summary: Create a generative test suite to test ItemDefinition dependency sorting algorithm Key: DROOLS-2318 URL: https://issues.jboss.org/browse/DROOLS-2318 Project: Drools Issue Type: Enhancement Components: dmn engine Reporter: Matteo Mortari Assignee: Tibor Zimányi ref https://github.com/kiegroup/drools/pull/1762#issuecomment-364916665 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-34) Use the same groupId:artifactId[:type[:classifier[:version]]] format everywhere

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-34?page=com.atlassian.jira.plugin... ] David Lloyd commented on WFBUILD-34: ------------------------------------ We _could_ enhance version 1.7 of the schema to expect g:a:t:c:v if that's the Maven standard. Then the build tools could examine the namespace to decide what format to use. But we should only use the format that is standardized in Maven if possible. > Use the same groupId:artifactId[:type[:classifier[:version]]] format everywhere > ------------------------------------------------------------------------------- > > Key: WFBUILD-34 > URL: https://issues.jboss.org/browse/WFBUILD-34 > Project: WildFly Build Tools > Issue Type: Enhancement > Reporter: Peter Palaga > Assignee: Stuart Douglas > Fix For: 1.2.8.Final > > > This both a usability issue and a feature request. > On the usability side, the artifact formats in module.xml files vs. in feature-pack-build.xml files are not the same: > * `{{groupId:artifactId\[:version\[:classifier]]}}` in module.xml files > * `{{groupId:artifactId\[:type\[:classifier]]}}` in feature-pack-build.xml files > The missing feature is the impossibility to define type/extension in module.xml files and the impossibility to had code version in feature-pack-build.xml files > The current proposal is to use the same {{groupId:artifactId\[:type\[:classifier\[:version]]]}} format in both kinds of files. > The proposal is backwards incompatible for module.xml files. But given that the support for hardcoded versions in module.xml files was added just 11 days ago, this will probably impact just a few users. > I am not sure what artifact format is used by JBoss modules. Maybe `{{groupId:artifactId\[:version\[:classifier]]}}` is taken from there? > WDYT [~swd847]? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9796) Update Eclipselink and OpenJPA module to public

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9796?page=com.atlassian.jira.plugin.... ] Scott Marlow closed WFLY-9796. ------------------------------ > Update Eclipselink and OpenJPA module to public > ----------------------------------------------- > > Key: WFLY-9796 > URL: https://issues.jboss.org/browse/WFLY-9796 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2317) FEEL Syntax error on function(bkm) containing `for` keyword

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-2317: -------------------------------------- Summary: FEEL Syntax error on function(bkm) containing `for` keyword Key: DROOLS-2317 URL: https://issues.jboss.org/browse/DROOLS-2317 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari Attachments: Dynamic composition.dmn Attached model {code:java} Error compiling FEEL expression 'for item in Order.items return Federal Tax for Item( item )' for name 'Calculate Federal Taxes' on node 'Calculate Federal Taxes': syntax error near 'for' {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2018