[JBoss JIRA] (WFLY-11316) Remove unused dependencies from org.jberet.jberet-core
by Ranabir Chakraborty (Jira)
[ https://issues.redhat.com/browse/WFLY-11316?page=com.atlassian.jira.plugi... ]
Ranabir Chakraborty commented on WFLY-11316:
--------------------------------------------
[~yersan] are you working on this issue?
> Remove unused dependencies from org.jberet.jberet-core
> ------------------------------------------------------
>
> Key: WFLY-11316
> URL: https://issues.redhat.com/browse/WFLY-11316
> Project: WildFly
> Issue Type: Bug
> Components: Batch
> Reporter: Yeray Borges Santana
> Assignee: Yeray Borges Santana
> Priority: Optional
>
> Analysis of org.jberet.jberet-core shows:
> * org.jboss.jts is unused
> * jberet only uses javax.enterprise.api, javax.inject.api, javax.annotation.api and javax.batch.api from javaee.api, maybe we could reduce the final size removing javaee.api and add only the required modules.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFLY-10612) Include EJB's IIOP Binding when EJB is deployed logging
by Brad Maxwell (Jira)
[ https://issues.redhat.com/browse/WFLY-10612?page=com.atlassian.jira.plugi... ]
Brad Maxwell updated WFLY-10612:
--------------------------------
Attachment: WFLY-10612.jar
> Include EJB's IIOP Binding when EJB is deployed logging
> -------------------------------------------------------
>
> Key: WFLY-10612
> URL: https://issues.redhat.com/browse/WFLY-10612
> Project: WildFly
> Issue Type: Enhancement
> Components: IIOP
> Affects Versions: 12.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Tomasz Adamski
> Priority: Major
> Attachments: WFLY-10612.jar
>
>
> It would be useful when EJBs configured with IIOP enabled or when enabled by default for all, that it log the binding for the IIOP interface as it is different from the JNDI bindings.
> <iiop enable-by-default="true" use-qualified-name="true"/>
> {code}
> INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
> java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean
> java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean
> java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloSessionBean
> java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemoteHome
> java:global/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> java:app/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> java:module/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> java:jboss/exported/iiop-eap7/HelloSessionBean!com.jboss.examples.ejb3.iiop.HelloRemote
> {code}
> Something like this when use-qualified-name="true"
> {code}
> IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
> iiop-eap7/HelloSessionBean
> {code}
> or use-qualified-name="false"
> {code}
> IIOP bindings for for session bean named 'HelloSessionBean' in deployment unit 'deployment "iiop-eap7.jar"' are as follows:
> HelloSessionBean
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFLY-13256) Upgrade bouncycastle to 1.65.0
by Ashley Abdel-Sayed (Jira)
[ https://issues.redhat.com/browse/WFLY-13256?page=com.atlassian.jira.plugi... ]
Ashley Abdel-Sayed commented on WFLY-13256:
-------------------------------------------
[~brian.stansberry] I'm still trying to determine if the issue is PicketLink related. I'm working on finishing up another task then I'll return to investigating this.
> Upgrade bouncycastle to 1.65.0
> ------------------------------
>
> Key: WFLY-13256
> URL: https://issues.redhat.com/browse/WFLY-13256
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Build System, Server
> Reporter: Bartosz Spyrko
> Assignee: Brian Stansberry
> Priority: Blocker
> Labels: downstream_dependency
> Fix For: 20.0.0.Beta1
>
> Attachments: handshake-error.log, handshake-success.log
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (ELY-1952) SSLConfigurator ignores some of the SSLParameters passed in via setSSLParameters method
by Diana Vilkolakova (Jira)
Diana Vilkolakova created ELY-1952:
--------------------------------------
Summary: SSLConfigurator ignores some of the SSLParameters passed in via setSSLParameters method
Key: ELY-1952
URL: https://issues.redhat.com/browse/ELY-1952
Project: WildFly Elytron
Issue Type: Bug
Reporter: Diana Vilkolakova
Assignee: Diana Vilkolakova
Method redefine in SSLConfiguratorImpl ignores some of the SSLParameters passed in, eg. cipher suites, protocols, needClientAuth, and others. Because of this, the assert in the code snippet below fails:
```
SSLParameters sslParameters = clientSslSocket.getSSLParameters();
sslParameters.setNeedClientAuth(true);
clientSslSocket.setSSLParameters(sslParameters);
Assert.assertTrue(clientSslSocket.getSSLParameters().getNeedClientAuth());
```
This issue is to address that.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFLY-13360) Log WARN when EJB does not implement Business interface and is not compliant with EJB 3.2 spec
by Panagiotis Sotiropoulos (Jira)
[ https://issues.redhat.com/browse/WFLY-13360?page=com.atlassian.jira.plugi... ]
Panagiotis Sotiropoulos updated WFLY-13360:
-------------------------------------------
Component/s: EJB
> Log WARN when EJB does not implement Business interface and is not compliant with EJB 3.2 spec
> ----------------------------------------------------------------------------------------------
>
> Key: WFLY-13360
> URL: https://issues.redhat.com/browse/WFLY-13360
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Panagiotis Sotiropoulos
> Assignee: Panagiotis Sotiropoulos
> Priority: Major
>
> From the specification every business interface need to be declared explicitly as a business interface by @Remote or @Local annotation or deployment descriptor.
> EJB 3.2 specification
> 4.9.7 Session Bean’s Business Interface
> - The bean class must implement the interface or the interface must be designated as a local or remote business interface of the bean by means of the Local or Remote annotation or in the deployment descriptor.
> - All business interfaces must be explicitly designated as such if any of the following is true:
> - the bean exposes a no-interface view
> - any interface of the bean class is explicitly designated as a business interface of the bean by either of the following means:
> - using the Local or Remote annotation with a non-empty value on the bean class
> - using the Local or Remote annotation on the interface
> - in the deployment descriptor
> If EJB A implements I and EJB B extends A , EJB B must also declare it implements I in order to be spec compliant:
> public interface I {...}
>
> @Stateless
> public class A implements I {...}
>
> @Stateless
> public class B extends A {...}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months