[
https://issues.apache.org/jira/browse/DELTASPIKE-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212467#comment-13212467
]
Mark Struberg commented on DELTASPIKE-96:
-
That's definitely a good thing. But
for loading classes we have the mentioned fallbacks already.
however, we don't have it for the lookup via the service-loader and the
lookup of resource-bundles.
if there is no result, it's clear that we have to use the fallback (i'll
create a jira issue for it).
however, right now we just have
refactor the owb-se example to a generic se-example
---
Key: DELTASPIKE-99
URL: https://issues.apache.org/jira/browse/DELTASPIKE-99
Project: DeltaSpike
Issue Type: Task
Components:
improve the bootstrapping module for java-se for simple use-cases
-
Key: DELTASPIKE-100
URL: https://issues.apache.org/jira/browse/DELTASPIKE-100
Project: DeltaSpike
Issue
[
https://issues.apache.org/jira/browse/DELTASPIKE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-100:
Description:
#1 if users don't need the (mocked) web scopes in an java-se
Anyone want to file the S/R with Oracle? :-) (I'm willing if you want)
On Tue, Feb 21, 2012 at 5:45 AM, Mark Struberg strub...@yahoo.de wrote:
Just another note.
12.1 of the CDI spec does only specify what parts of the classpath are a
BeanArchive. But in the Spec we doesn't say anything
hi john,
i hope joseph can help with such topics directly.
regards,
gerhard
2012/2/21 John D. Ament john.d.am...@gmail.com
Anyone want to file the S/R with Oracle? :-) (I'm willing if you want)
On Tue, Feb 21, 2012 at 5:45 AM, Mark Struberg strub...@yahoo.de wrote:
Just another
hi @ all,
i pushed a fix for the current issue to [1].
@rudy:
it would be great, if you can test it with wls12c.
if we identify further cases, we have to find a better approach for the
class-loader lookup, because we need the classloader also for some caches.
regards,
gerhard
[1]
[
https://issues.apache.org/jira/browse/DELTASPIKE-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-92:
---
Component/s: (was: Core)
CDI-SE
ContainerControl API +
[
https://issues.apache.org/jira/browse/DELTASPIKE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-99:
---
Issue Type: Sub-task (was: Task)
Parent: DELTASPIKE-92
refactor the
folks,
the Arquillian we currently use doesn't work together with jboss-as-7.1.0.Final.
When will a fixed version be available? Who takes the responsibility?
LieGrue,
strub
it's fixed and tested already.
regards,
gerhard
2012/2/21 Mark Struberg strub...@yahoo.de
I remember that we changed exactly this behaviour at some point ^^
We should check why we did that back then...
LieGrue,
strub
- Original Message -
From: Rudy De Busscher
Hi!
Thanks Dan and Jason for the explanation. I wasn't aware of that. Will try to
re-run all the tests with the updated property.
Btw, if you like to run the CI for different AS versions, then you can just use
-Djboss.as.version=...
to overwrite the default setting in the pom.
LieGrue,
Here's the link explaining the Servlet 3.0 protocol.
https://docs.jboss.org/author/display/ARQ/Servlet+3.0
I recall now why it's beneficial. For one, it's used by all the other EE 6
containers, so consistency is one reason to use it. The other reason is
that it actually starts the web contexts
14 matches
Mail list logo