[JBoss JIRA] (WFLY-13384) Add IIOP Naming View Management Command
by Brad Maxwell (Jira)
Brad Maxwell created WFLY-13384:
-----------------------------------
Summary: Add IIOP Naming View Management Command
Key: WFLY-13384
URL: https://issues.redhat.com/browse/WFLY-13384
Project: WildFly
Issue Type: Feature Request
Components: IIOP
Affects Versions: 19.0.0.Final
Reporter: Brad Maxwell
Assignee: Tomasz Adamski
Currently there is not a way to view the IIOP Naming Bindings.
Similar to the JNDI View shown below, a management command to get a view of the IIOP Naming bindings would be useful.
{code}
/subsystem=naming:jndi-view
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFLY-10612) Include EJB's IIOP Binding when EJB is deployed logging
by Ranabir Chakraborty (Jira)
[ https://issues.redhat.com/browse/WFLY-10612?page=com.atlassian.jira.plugi... ]
Ranabir Chakraborty reassigned WFLY-10612:
------------------------------------------
Assignee: Ranabir Chakraborty (was: Tomasz Adamski)
> 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: Ranabir Chakraborty
> Priority: Major
> Attachments: WFLY-10612.jar, java.policy
>
>
> 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, 5 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, java.policy
>
>
> 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, 5 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: (was: 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, java.policy
>
>
> 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, 5 months
[JBoss JIRA] (WFLY-13003) Support the SameSite cookie attribute
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13003?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-13003:
------------------------------------
Fix Version/s: 19.1.0.Final
20.0.0.Beta1
> Support the SameSite cookie attribute
> -------------------------------------
>
> Key: WFLY-13003
> URL: https://issues.redhat.com/browse/WFLY-13003
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Reporter: Stuart Douglas
> Assignee: Flavia Rainone
> Priority: Major
> Fix For: 19.1.0.Final, 20.0.0.Beta1
>
>
> Chrome 80 is going to significantly change how cookies are handled, as per this notice at [1], with a bit of an explanation of what the same site attribute means at [2].
> At the moment the Servlet specification has no way of setting this particular attribute, and it is not possible to configure it via container specific configuration in WildFly at present (it can only be done by writing some Undertow specific code).
> I propose we add a same-site-cookie-attribute predicated handler to undertow, which takes an optional cookie name regex, and the value for the attribute to set.
> This would allow users to configure the SameSite attribute based on cookie name, and also potentially based on any other attributes including user agent, as it sounds like some browsers may have bugs that means this might need to be set on a per user agent basis.
> [1] https://www.chromestatus.com/feature/5088147346030592
> [2] https://web.dev/samesite-cookies-explained/
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 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: (was: 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, java.policy
>
>
> 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, 5 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, java.policy
>
>
> 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, 5 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: java.policy
> 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, java.policy
>
>
> 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, 5 months