[JBoss JIRA] (WFCORE-4873) Upgrade JGit to 5.8.0.202006091008-r
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFCORE-4873?page=com.atlassian.jira.plug... ]
Emmanuel Hugonnet updated WFCORE-4873:
--------------------------------------
Description: In order to be able to switch the ssh implementation we need to upgrade JGit to 5.8.0.202006091008-r and update javaewah to 1.1.7 on the way. (was: In order to be able to switch the ssh implementation we need to upgrade JGit to 5.8.0.202006091008-r)
> Upgrade JGit to 5.8.0.202006091008-r
> ------------------------------------
>
> Key: WFCORE-4873
> URL: https://issues.redhat.com/browse/WFCORE-4873
> Project: WildFly Core
> Issue Type: Component Upgrade
> Components: Management
> Affects Versions: 11.0.0.Final
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> In order to be able to switch the ssh implementation we need to upgrade JGit to 5.8.0.202006091008-r and update javaewah to 1.1.7 on the way.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13641) WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml
by Jens Viebig (Jira)
[ https://issues.redhat.com/browse/WFLY-13641?page=com.atlassian.jira.plugi... ]
Jens Viebig commented on WFLY-13641:
------------------------------------
Here is the sample project.
Source: [https://github.com/JSurf/WFLY-13641]
Binaries: [https://github.com/JSurf/WFLY-13641/releases]
Issue can be reproduced with a fresh download of wildfly by just deploying the ear and war
You can skip step 1 and 2 when using the binaries
# Build ear
{{cd ear}}
{{mvn install}}
{{cd ..}}
# Build war
{{cd war}}
{{mvn install}}
# Download wildfly zip, unpack
# copy ear/ear/target/myear.ear to wildfly standalone/deployments
# copy war/target/mywar.war to wildfly standalone/deployments
# Start wildfly with standalone.bat or standalone.sh
> WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13641
> URL: https://issues.redhat.com/browse/WFLY-13641
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 20.0.0.Final
> Reporter: Jens Viebig
> Assignee: Matěj Novotný
> Priority: Major
>
> When referencing a jar with CDI scan mode "annotaded" inside an ear from an external war via jboss-deployment-structure.xml a warning will be printed for every class:
> WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml
> Seems VFS cannot get hold of the classes.
> The warning is logged in ExternalBeanArchiveProcessor which catches an EOFException from the inputstream loading the class. (Line 284). Seems the input stream is not able to load a single byte from the class
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5498) Avoid using import star in executable model classes and always use FQN
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5498?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5498:
---------------------------------
Tester: Daniel Rosa
Story Points: 3
> Avoid using import star in executable model classes and always use FQN
> ----------------------------------------------------------------------
>
> Key: DROOLS-5498
> URL: https://issues.redhat.com/browse/DROOLS-5498
> Project: Drools
> Issue Type: Enhancement
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
>
> to avoid problem such as
>
> ```[ERROR] /home/lmolteni/git/reproducer20200430/target/generated-sources/drools-model-compiler/main/java/org/kie/dmn/validation/DMNv1_1/Rules86f277caf99949898df882cceeb356edRuleMethods0.java:[42,260] reference to Binding is ambiguous
> [ERROR] both interface org.kie.dmn.model.api.Binding in org.kie.dmn.model.api and interface org.drools.model.Binding in org.drools.model match
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5498) Avoid using import star in executable model classes and always use FQN
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5498?page=com.atlassian.jira.plug... ]
Luca Molteni reassigned DROOLS-5498:
------------------------------------
Assignee: Luca Molteni (was: Mario Fusco)
> Avoid using import star in executable model classes and always use FQN
> ----------------------------------------------------------------------
>
> Key: DROOLS-5498
> URL: https://issues.redhat.com/browse/DROOLS-5498
> Project: Drools
> Issue Type: Enhancement
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
>
> to avoid problem such as
>
> ```[ERROR] /home/lmolteni/git/reproducer20200430/target/generated-sources/drools-model-compiler/main/java/org/kie/dmn/validation/DMNv1_1/Rules86f277caf99949898df882cceeb356edRuleMethods0.java:[42,260] reference to Binding is ambiguous
> [ERROR] both interface org.kie.dmn.model.api.Binding in org.kie.dmn.model.api and interface org.drools.model.Binding in org.drools.model match
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5498) Avoid using import star in executable model classes and always use FQN
by Luca Molteni (Jira)
Luca Molteni created DROOLS-5498:
------------------------------------
Summary: Avoid using import star in executable model classes and always use FQN
Key: DROOLS-5498
URL: https://issues.redhat.com/browse/DROOLS-5498
Project: Drools
Issue Type: Enhancement
Reporter: Luca Molteni
Assignee: Mario Fusco
to avoid problem such as
```[ERROR] /home/lmolteni/git/reproducer20200430/target/generated-sources/drools-model-compiler/main/java/org/kie/dmn/validation/DMNv1_1/Rules86f277caf99949898df882cceeb356edRuleMethods0.java:[42,260] reference to Binding is ambiguous
[ERROR] both interface org.kie.dmn.model.api.Binding in org.kie.dmn.model.api and interface org.drools.model.Binding in org.drools.model match
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13619) Elytron: org.wildfly.security.auth.server.SecurityIdentity not Serializable
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-13619?page=com.atlassian.jira.plugi... ]
Darran Lofthouse reassigned WFLY-13619:
---------------------------------------
Assignee: (was: Darran Lofthouse)
> Elytron: org.wildfly.security.auth.server.SecurityIdentity not Serializable
> ---------------------------------------------------------------------------
>
> Key: WFLY-13619
> URL: https://issues.redhat.com/browse/WFLY-13619
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 20.0.0.Final
> Reporter: Andrej Kolontai
> Priority: Minor
>
> Since the old security subsystem has been deprecated for a while I decided to move my applications to elytron which worked just fine up to the point where I tried to migrate an application that is:
> * distributed
> * uses Jaspic in form of a JSR375 HttpAuthenticationMechanism which has@AutoApplySession
> In the logs I see stacktraces like this:
>
> {noformat}
> 09:37:22,045 WARN [org.infinispan.PERSISTENCE] (default task-1) ISPN000559: Cannot marshall 'class org.infinispan.marshall.protostream.impl.MarshallableUserObject': java.io.NotSerializableException: org.wildfly.security.auth.server.SecurityIdentity
> at org.jboss.marshalling.river@2.0.9.Final//org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:272)}}
> at org.jboss.marshalling.river@2.0.9.Final//org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1141)}}
> at org.jboss.marshalling.river@2.0.9.Final//org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1099)}}
> at org.jboss.marshalling.river@2.0.9.Final//org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:266)}}
> at org.jboss.marshalling@2.0.9.Final//org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:58)}}
> at org.jboss.marshalling@2.0.9.Final//org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:111)}}
> .....
> Caused by: an exception which occurred:
> in field org.wildfly.elytron.web.undertow.server.servlet.ServletSecurityContextImpl$IdentityContainer.securityIdentity
> in object org.wildfly.elytron.web.undertow.server.servlet.ServletSecurityContextImpl$IdentityContainer@7bf2af9a
> in object org.wildfly.elytron.web.undertow.server.servlet.ServletSecurityContextImpl$IdentityContainer@7bf2af9a
> in object java.util.concurrent.ConcurrentHashMap@d02a9ca2
> in object org.wildfly.clustering.marshalling.jboss.SimpleMarshalledValue@d02a9ca2
> {noformat}
>
>
> Looks to me like it's trying to serialize the session to replicate it to the other nodes in the cluster and fails because the user identity, which is part of the session because of AutoApplySession, is not serializable. I have checked the source and it is really not serializable.
>
> I had no problems with the old security subsystem (i.e. jaspitest).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFCORE-5020) Although elytron has module for JACC factory it is not used for JACC
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-5020?page=com.atlassian.jira.plug... ]
Darran Lofthouse updated WFCORE-5020:
-------------------------------------
Fix Version/s: 13.0.0.Beta2
> Although elytron has module for JACC factory it is not used for JACC
> --------------------------------------------------------------------
>
> Key: WFCORE-5020
> URL: https://issues.redhat.com/browse/WFCORE-5020
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 12.0.1.Final
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 13.0.0.Beta2
>
>
> A module can be specified and this is used to load the specified provider class and instantiate it, however this is separate to the one instantiated by PolicyConfigurationFactory.
> Elytron does set a system property to ensure the configured class name is used but does not actually ensure the module is used for class loading.
> At the same time it should be ensuring there is only a single instance of the class.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years