[JBoss JIRA] (WFLY-1077) JDK ORB Subsystem
by Dimitris Andreadis (JIRA)
[ https://issues.jboss.org/browse/WFLY-1077?page=com.atlassian.jira.plugin.... ]
Dimitris Andreadis edited comment on WFLY-1077 at 5/4/15 7:13 AM:
------------------------------------------------------------------
Isn't this JIRA completed? No fix version? That's lousy housekeeping.
Also, shouldn't WFLY issues "block" the dependent EAP7 ones?
was (Author: dimitris):
Isn't this JIRA completed? No fix version? That's lousy housekeeping.
Also, shouldn't WFLY issues "blocker" the dependent EAP7 ones?
> JDK ORB Subsystem
> -----------------
>
> Key: WFLY-1077
> URL: https://issues.jboss.org/browse/WFLY-1077
> Project: WildFly
> Issue Type: Feature Request
> Components: IIOP
> Reporter: Dimitris Andreadis
> Assignee: Tomasz Adamski
>
> Implement a JDK ORB subsystem that can act as a replacement for the JacORB subsystem.
> AFAIK, most/all JDK ORBs are based on the Sun ORB.
> Ideally the 2 ORBs (JDK & JacORB) would be both supported in case we need to go through a transition period, or we need to support a particular interop scenario for which interop communication has issues.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
[JBoss JIRA] (WFLY-1077) JDK ORB Subsystem
by Dimitris Andreadis (JIRA)
[ https://issues.jboss.org/browse/WFLY-1077?page=com.atlassian.jira.plugin.... ]
Dimitris Andreadis commented on WFLY-1077:
------------------------------------------
Isn't this JIRA completed? No fix version? That's lousy housekeeping.
Also, shouldn't WFLY issues "blocker" the dependent EAP7 ones?
> JDK ORB Subsystem
> -----------------
>
> Key: WFLY-1077
> URL: https://issues.jboss.org/browse/WFLY-1077
> Project: WildFly
> Issue Type: Feature Request
> Components: IIOP
> Reporter: Dimitris Andreadis
> Assignee: Tomasz Adamski
>
> Implement a JDK ORB subsystem that can act as a replacement for the JacORB subsystem.
> AFAIK, most/all JDK ORBs are based on the Sun ORB.
> Ideally the 2 ORBs (JDK & JacORB) would be both supported in case we need to go through a transition period, or we need to support a particular interop scenario for which interop communication has issues.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
[JBoss JIRA] (WFLY-4580) Lifecycle interceptors do not work
by Xavier Dury (JIRA)
Xavier Dury created WFLY-4580:
---------------------------------
Summary: Lifecycle interceptors do not work
Key: WFLY-4580
URL: https://issues.jboss.org/browse/WFLY-4580
Project: WildFly
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 8.2.0.Final, JBoss AS7 7.1.1.Final
Reporter: Xavier Dury
Assignee: Stuart Douglas
I've been trying to use lifecycle interceptors (intercepting PostConstruct and PreDestroy, see https://issues.jboss.org/browse/WELD-1346 for reference) in my project and those do not seem to work at all (nor on enterprise managed beans nor on regular CDI managed beans).
I tried on both JBoss AS 7.1.1 and Wildfly 8.2.0 but lifecycle interceptors are never called while other interceptors (AroundInvoke) are.
I tested the same code on OpenEJB and it works.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
[JBoss JIRA] (JBMETA-385) Add overridable flag to servlet metadata
by Jean-Frederic Clere (JIRA)
[ https://issues.jboss.org/browse/JBMETA-385?page=com.atlassian.jira.plugin... ]
Jean-Frederic Clere closed JBMETA-385.
--------------------------------------
Fix Version/s: 7.2.2.Final
Resolution: Done
> Add overridable flag to servlet metadata
> ----------------------------------------
>
> Key: JBMETA-385
> URL: https://issues.jboss.org/browse/JBMETA-385
> Project: JBoss Metadata
> Issue Type: Enhancement
> Components: web
> Affects Versions: 7.2.1.Final
> Reporter: James Livingston
> Assignee: Bartosz Baranowski
> Fix For: 7.2.2.Final
>
>
> To resolve https://bugzilla.redhat.com/show_bug.cgi?id=1094248, I believe we need an additional 'overridable' flag on the servlet metadata which indicates whether ServletContainerInitializers (and other code using servlet dynamic registration) should be allowed to override the servlet. Normally this is not allowed, however JBWeb's internal use of DefaultServlet to handle static resources should be.
> This only needs to go into 7, since the Undertow subsystem in Wildfly handles this quite differently, so does not need to pass a flag between components.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
[JBoss JIRA] (WFLY-4572) wildfly-arquillian uses slf4j-api:1.7.7.jbossorg-1 which is not available in maven central repository
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-4572?page=com.atlassian.jira.plugin.... ]
Martin Kouba commented on WFLY-4572:
------------------------------------
There is a comment in wildfly-arquillian-parent pom.xml:
{code:xml}
<!-- Needed until issues with a thin WildFly server pulling down
artifacts from a remote repo are resolved. This ensures
the needed WildFly Core artifacts are available locally
when we provision a server for the testsuite -->
<dependency>
<groupId>org.wildfly.core</groupId>
<artifactId>wildfly-core-feature-pack</artifactId>
<type>pom</type>
<version>${version.org.wildfly.core}</version>
</dependency>
{code}
> wildfly-arquillian uses slf4j-api:1.7.7.jbossorg-1 which is not available in maven central repository
> -----------------------------------------------------------------------------------------------------
>
> Key: WFLY-4572
> URL: https://issues.jboss.org/browse/WFLY-4572
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 8.2.0.Final, 9.0.0.Beta2
> Reporter: Martin Kouba
> Assignee: Paul Gier
>
> GAV: {{org.slf4j:slf4j-api:1.7.7.jbossorg-1}}
> As a result, it's not possible to build a project which depends on some referencing module, e.g. {{wildfly-arquillian-common}}, and does not define JBoss repository at the same time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months