[jira] [Updated] (DELTASPIKE-1238) Create a better default TransactionStrategy
[ https://issues.apache.org/jira/browse/DELTASPIKE-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-1238: -- Description: Create a better default TransactionStrategy that handles more use cases out of the box. (was: Make EnvironmentAwareTransactionStrategy the default transaction strategy, since it properly looks up container managed, resource local without requiring the user to do anything.) > Create a better default TransactionStrategy > --- > > Key: DELTASPIKE-1238 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1238 > Project: DeltaSpike > Issue Type: Improvement >Reporter: John D. Ament >Assignee: John D. Ament > > Create a better default TransactionStrategy that handles more use cases out > of the box. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (DELTASPIKE-1238) Create a better default TransactionStrategy
[ https://issues.apache.org/jira/browse/DELTASPIKE-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-1238: -- Summary: Create a better default TransactionStrategy (was: Make EnvironmentAwareTransactionStrategy the default) > Create a better default TransactionStrategy > --- > > Key: DELTASPIKE-1238 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1238 > Project: DeltaSpike > Issue Type: Improvement >Reporter: John D. Ament >Assignee: John D. Ament > > Make EnvironmentAwareTransactionStrategy the default transaction strategy, > since it properly looks up container managed, resource local without > requiring the user to do anything. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (DELTASPIKE-1238) Make EnvironmentAwareTransactionStrategy the default
[ https://issues.apache.org/jira/browse/DELTASPIKE-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament reopened DELTASPIKE-1238: --- Hey, I disagree. We can talk through it more, but it isn't a top priority for me right now. > Make EnvironmentAwareTransactionStrategy the default > > > Key: DELTASPIKE-1238 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1238 > Project: DeltaSpike > Issue Type: Improvement >Reporter: John D. Ament >Assignee: John D. Ament > > Make EnvironmentAwareTransactionStrategy the default transaction strategy, > since it properly looks up container managed, resource local without > requiring the user to do anything. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (DELTASPIKE-1195) Servlet module forces application to use distributed sessions
[ https://issues.apache.org/jira/browse/DELTASPIKE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved DELTASPIKE-1195. --- Resolution: Won't Fix Wasn't me, but the user mentioned that issue is not ours, so I think we're good. > Servlet module forces application to use distributed sessions > - > > Key: DELTASPIKE-1195 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1195 > Project: DeltaSpike > Issue Type: Bug > Components: Servlet-Module >Affects Versions: 1.7.1 >Reporter: Klaasjan Brand >Assignee: John D. Ament >Priority: Minor > > The deltaspike-servlet-module-impl jar contains a web-fragment.xml file > containing a tag. This forces every web application > including this jar file to support distributed sessions. > I know it's possible to disable the parsing of fragments, but we use > fragments for other libraries. Besides, I don't think it's the responsibility > of deltaspike to decide if web application sessions are distributable. > Could you consider removing this line? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1178) DS 1.7.0 introduced a transitive dependency to arquillian
[ https://issues.apache.org/jira/browse/DELTASPIKE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951047#comment-15951047 ] ASF subversion and git services commented on DELTASPIKE-1178: - Commit 853bd6ffca53f44d8bb482b1dbb330ec7b85c9b5 in deltaspike's branch refs/heads/master from [~struberg] [ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=853bd6f ] DELTASPIKE-1178 remove transitive dependencies to Arquillian > DS 1.7.0 introduced a transitive dependency to arquillian > - > > Key: DELTASPIKE-1178 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1178 > Project: DeltaSpike > Issue Type: Bug > Components: TestControl >Affects Versions: 1.7.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > TestControl doesn't need any Arquillian dependency at all. No idea why this > got introduced... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (DELTASPIKE-1178) DS 1.7.0 introduced a transitive dependency to arquillian
[ https://issues.apache.org/jira/browse/DELTASPIKE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1178. --- Resolution: Fixed Fix Version/s: 1.8.0 > DS 1.7.0 introduced a transitive dependency to arquillian > - > > Key: DELTASPIKE-1178 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1178 > Project: DeltaSpike > Issue Type: Bug > Components: TestControl >Affects Versions: 1.7.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 1.8.0 > > > TestControl doesn't need any Arquillian dependency at all. No idea why this > got introduced... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1178) DS 1.7.0 introduced a transitive dependency to arquillian
[ https://issues.apache.org/jira/browse/DELTASPIKE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951045#comment-15951045 ] Mark Struberg commented on DELTASPIKE-1178: --- It's in the cdictrl-owb module. Just came across this yesterday again. Will fix it. > DS 1.7.0 introduced a transitive dependency to arquillian > - > > Key: DELTASPIKE-1178 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1178 > Project: DeltaSpike > Issue Type: Bug > Components: TestControl >Affects Versions: 1.7.0 >Reporter: Mark Struberg >Assignee: Mark Struberg > > TestControl doesn't need any Arquillian dependency at all. No idea why this > got introduced... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1195) Servlet module forces application to use distributed sessions
[ https://issues.apache.org/jira/browse/DELTASPIKE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951039#comment-15951039 ] Mark Struberg commented on DELTASPIKE-1195: --- John, the servlet module is from you iirc. Do you mind to take care? txs! > Servlet module forces application to use distributed sessions > - > > Key: DELTASPIKE-1195 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1195 > Project: DeltaSpike > Issue Type: Bug > Components: Servlet-Module >Affects Versions: 1.7.1 >Reporter: Klaasjan Brand >Assignee: John D. Ament >Priority: Minor > > The deltaspike-servlet-module-impl jar contains a web-fragment.xml file > containing a tag. This forces every web application > including this jar file to support distributed sessions. > I know it's possible to disable the parsing of fragments, but we use > fragments for other libraries. Besides, I don't think it's the responsibility > of deltaspike to decide if web application sessions are distributable. > Could you consider removing this line? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (DELTASPIKE-1195) Servlet module forces application to use distributed sessions
[ https://issues.apache.org/jira/browse/DELTASPIKE-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg reassigned DELTASPIKE-1195: - Assignee: John D. Ament (was: Mark Struberg) > Servlet module forces application to use distributed sessions > - > > Key: DELTASPIKE-1195 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1195 > Project: DeltaSpike > Issue Type: Bug > Components: Servlet-Module >Affects Versions: 1.7.1 >Reporter: Klaasjan Brand >Assignee: John D. Ament >Priority: Minor > > The deltaspike-servlet-module-impl jar contains a web-fragment.xml file > containing a tag. This forces every web application > including this jar file to support distributed sessions. > I know it's possible to disable the parsing of fragments, but we use > fragments for other libraries. Besides, I don't think it's the responsibility > of deltaspike to decide if web application sessions are distributable. > Could you consider removing this line? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1212) Introduce a ConfigResolver.resolveAllProperties method
[
https://issues.apache.org/jira/browse/DELTASPIKE-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951033#comment-15951033
]
Mark Struberg commented on DELTASPIKE-1212:
---
I think this is not an accident but by design. If you use getAllProperties then
you cannot easily make assumptions about whether a specific
property-evaluation, projectstage-evaluation or variable replacement is to be
assumed. Any assumption we would take might be wrong, isn't?
One could still iterate over the keys and resolve them one by one.
> Introduce a ConfigResolver.resolveAllProperties method
> --
>
> Key: DELTASPIKE-1212
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1212
> Project: DeltaSpike
> Issue Type: New Feature
> Components: Configuration
>Affects Versions: 1.7.0
>Reporter: John D. Ament
> Fix For: 1.8.0
>
>
> Invoking ConfigResolver.getAllProperties does not expand out any inlined
> variables. In addition, assume the following properties file and project
> stage = Development
> {code}
> some-service-url=${edge-server-url}/some-service
> edge-server-url=undefined
> edge-server-url.Development=http://development:8081
> edge-server-url.Staging=http://staging:8081
> edge-server-url.Production=http://prod:8081
> {code}
> calling {{getAllProperties}} returns the raw output of this file.
> Introducing a new {{resolveAllProperties}} method would only return back the
> active values. The expected result would be
> {code}
> some-service-url=http://development:8081/some-service
> edge-server-url=http://development:8081
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (DELTASPIKE-1235) DS 2: check if we can remove our ContextControl
[ https://issues.apache.org/jira/browse/DELTASPIKE-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-1235. - Resolution: Won't Fix > DS 2: check if we can remove our ContextControl > --- > > Key: DELTASPIKE-1235 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1235 > Project: DeltaSpike > Issue Type: Wish > Components: CdiControl >Affects Versions: 2.0 >Reporter: Thomas Andraschko > Fix For: 2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1235) DS 2: check if we can remove our ContextControl
[ https://issues.apache.org/jira/browse/DELTASPIKE-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951022#comment-15951022 ] Mark Struberg commented on DELTASPIKE-1235: --- Agree with John. I'd still keep those things around. ContainerControl also has a huge benefit over the CDISE part: it can take properties for the container boot. That way you can e.g. pass information to set up DataSources, switch flags, etc. This is something CDISE does not provide. > DS 2: check if we can remove our ContextControl > --- > > Key: DELTASPIKE-1235 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1235 > Project: DeltaSpike > Issue Type: Wish > Components: CdiControl >Affects Versions: 2.0 >Reporter: Thomas Andraschko > Fix For: 2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (DELTASPIKE-1238) Make EnvironmentAwareTransactionStrategy the default
[ https://issues.apache.org/jira/browse/DELTASPIKE-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg closed DELTASPIKE-1238. - Resolution: Won't Fix would introduce performance and backward compatibility issues > Make EnvironmentAwareTransactionStrategy the default > > > Key: DELTASPIKE-1238 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1238 > Project: DeltaSpike > Issue Type: Improvement >Reporter: John D. Ament >Assignee: John D. Ament > > Make EnvironmentAwareTransactionStrategy the default transaction strategy, > since it properly looks up container managed, resource local without > requiring the user to do anything. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (DELTASPIKE-1228) ContextControl does not work in Websphere AS
[
https://issues.apache.org/jira/browse/DELTASPIKE-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed DELTASPIKE-1228.
-
Resolution: Won't Fix
> ContextControl does not work in Websphere AS
>
>
> Key: DELTASPIKE-1228
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1228
> Project: DeltaSpike
> Issue Type: Bug
>Affects Versions: 1.7.1
> Environment: Websphere 8.5.5.9
>Reporter: Matthias Wronka
>Assignee: Mark Struberg
>
> I´m getting an Exception in Websphere Application Server 8.5.5.9 when I try
> to start the SessionScope like this using ContextControl:
> {code:java}
> @Stateless
> @RunAs("scheduled")
> public class ScheduledService {
> @Inject
> private DemoConfiguration config; // contains SessionScoped references
> @Inject
> private ContextControl contextControl;
> @Schedule(hour = "*", minute = "*")
> private void doSth() {
> contextControl.startContext(SessionScoped.class);
> // ... use injected config-reference from above
> contextControl.stopContext(SessionScoped.class);
> }
> }
> {code}
> The exception is:
> {code}
> java.lang.NoClassDefFoundError: org/apache/webbeans/config/WebBeansContext at
> org.apache.deltaspike.cdise.owb.OpenWebBeansContextControl.getContextsService(OpenWebBeansContextControl.java:242)
> at
> org.apache.deltaspike.cdise.owb.OpenWebBeansContextControl.startSessionScope(OpenWebBeansContextControl.java:154)
> at
> org.apache.deltaspike.cdise.owb.OpenWebBeansContextControl.startContext(OpenWebBeansContextControl.java:80)
>
> {code}
> I think this is because of a rather old owb-implementations, that Websphere
> uses. I found the missing class in another package:
> org/apache/webbeans/*context*/WebBeansContext.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (DELTASPIKE-1228) ContextControl does not work in Websphere AS
[
https://issues.apache.org/jira/browse/DELTASPIKE-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951015#comment-15951015
]
Mark Struberg commented on DELTASPIKE-1228:
---
You have to use @RequestScoped to work in a portable way.
Btw, starting new threads can be done by having a wrapper EJB with an
@Asynchronous methods which takes a Callable.
Don't forget to increment the pool size. It's only set to 5 by default I think.
Otherwise there is not much we can do for you in DeltaSpike I fear -> closing.
> ContextControl does not work in Websphere AS
>
>
> Key: DELTASPIKE-1228
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1228
> Project: DeltaSpike
> Issue Type: Bug
>Affects Versions: 1.7.1
> Environment: Websphere 8.5.5.9
>Reporter: Matthias Wronka
>Assignee: Mark Struberg
>
> I´m getting an Exception in Websphere Application Server 8.5.5.9 when I try
> to start the SessionScope like this using ContextControl:
> {code:java}
> @Stateless
> @RunAs("scheduled")
> public class ScheduledService {
> @Inject
> private DemoConfiguration config; // contains SessionScoped references
> @Inject
> private ContextControl contextControl;
> @Schedule(hour = "*", minute = "*")
> private void doSth() {
> contextControl.startContext(SessionScoped.class);
> // ... use injected config-reference from above
> contextControl.stopContext(SessionScoped.class);
> }
> }
> {code}
> The exception is:
> {code}
> java.lang.NoClassDefFoundError: org/apache/webbeans/config/WebBeansContext at
> org.apache.deltaspike.cdise.owb.OpenWebBeansContextControl.getContextsService(OpenWebBeansContextControl.java:242)
> at
> org.apache.deltaspike.cdise.owb.OpenWebBeansContextControl.startSessionScope(OpenWebBeansContextControl.java:154)
> at
> org.apache.deltaspike.cdise.owb.OpenWebBeansContextControl.startContext(OpenWebBeansContextControl.java:80)
>
> {code}
> I think this is because of a rather old owb-implementations, that Websphere
> uses. I found the missing class in another package:
> org/apache/webbeans/*context*/WebBeansContext.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
