[jira] [Resolved] (DELTASPIKE-956) Clearly document transaction integration patterns for repository classes
[ https://issues.apache.org/jira/browse/DELTASPIKE-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved DELTASPIKE-956. -- Resolution: Fixed Assignee: John D. Ament Fix Version/s: 1.5.1 Clearly document transaction integration patterns for repository classes Key: DELTASPIKE-956 URL: https://issues.apache.org/jira/browse/DELTASPIKE-956 Project: DeltaSpike Issue Type: New Feature Components: Data-Module, Documentation, JPA-Module Affects Versions: 1.4.1 Reporter: John D. Ament Assignee: John D. Ament Fix For: 1.5.1 I was implementing Data on top of WildFly 9 today. After about an hour of battling I got it to work end to end. In my case I was using a REST API, but used these steps: - Annotate the outermost layer with @javax.transactional.Transactional - Set the transaction strategy to container managed (Separate JIRA ticket coming for this pain) Only then did saves work properly for the repository interface. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DELTASPIKE-955) Built in class deactivator
[
https://issues.apache.org/jira/browse/DELTASPIKE-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John D. Ament updated DELTASPIKE-955:
-
Description:
Add a built in ClassDeactivator that maybe reads from
apache-deltaspike.properties
Today I was reimplementing DS for the data module. One of the things I noticed
was that there's no built in support for deactivation (via plain
configuration). If look at
https://deltaspike.apache.org/documentation/spi.html#ClassDeactivator it seems
like one of the key features missing is to add a property, e.g.
{code}
deactivate.fqcn=true
{code}
Which would deactivate that class. Seems like a cool native deactivator that
we could bundle in by default, but still activate via config.
was:
Add a built in ClassDeactivator that maybe reads from
apache-deltaspike.properties
Today I was reimplementing DS for the data module. One of the things I noticed
was that there's no built in support for deactivation (via plain
configuration). If look at
https://deltaspike.apache.org/documentation/spi.html#ClassDeactivator it seems
like one of the key features missing is to add a property, e.g.
```
deactivate.fqcn=true
```
Which would deactivate that class. Seems like a cool native deactivator that
we could bundle in by default, but still activate via config.
Built in class deactivator
--
Key: DELTASPIKE-955
URL: https://issues.apache.org/jira/browse/DELTASPIKE-955
Project: DeltaSpike
Issue Type: New Feature
Components: Core
Affects Versions: 1.4.1
Reporter: John D. Ament
Add a built in ClassDeactivator that maybe reads from
apache-deltaspike.properties
Today I was reimplementing DS for the data module. One of the things I
noticed was that there's no built in support for deactivation (via plain
configuration). If look at
https://deltaspike.apache.org/documentation/spi.html#ClassDeactivator it
seems like one of the key features missing is to add a property, e.g.
{code}
deactivate.fqcn=true
{code}
Which would deactivate that class. Seems like a cool native deactivator that
we could bundle in by default, but still activate via config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Wildfly 9 Tests?
All, Looking at http://deltaspike.apache.org/documentation/build.html it seems we don't build and test against Wildfly 9, only 8. One key difference is that now the arquillian container is separately managed. Is this simply an over sight? John
[ANNOUNCE] Release of Apache DeltaSpike 1.5.0
The Apache DeltaSpike team is pleased to announce the 19th release of DeltaSpike. Apache DeltaSpike is not a CDI-container, but a portable CDI extension. Documentation: http://deltaspike.apache.org/documentation/ Download: http://deltaspike.apache.org/download.html Release Notes: http://s.apache.org/DeltaSpike_1.5.0 Enjoy! Gerhard Petracek
RE: Wildfly 9 Tests?
Now that IBM finally got an EE7 server certified (http://www.oracle.com/technetwork/java/javaee/overview/compatibility-jsp-136984.html )... does it make sense to add them to the suite (particularly if we are going to add Wildfly 9)? _Marvin -Original Message- From: John D. Ament [mailto:johndam...@apache.org] Sent: Sunday, August 16, 2015 10:07 PM To: deltaspike dev@deltaspike.apache.org Subject: Wildfly 9 Tests? All, Looking at http://deltaspike.apache.org/documentation/build.html it seems we don't build and test against Wildfly 9, only 8. One key difference is that now the Arquillian container is separately managed. Is this simply an over sight? John
Re: Wildfly 9 Tests?
Marvin, It's definitely worth starting the conversations about. Personally, I feel like the switch of impls between OWB and Weld may create a lot of regression issues, but I've seen pretty quick turn around from the devs on it (just not as quick of a release schedule). John On Sun, Aug 16, 2015 at 10:39 PM Marvin Toll marvint...@gtcgroup.com wrote: Now that IBM finally got an EE7 server certified ( http://www.oracle.com/technetwork/java/javaee/overview/compatibility-jsp-136984.html )... does it make sense to add them to the suite (particularly if we are going to add Wildfly 9)? _Marvin -Original Message- From: John D. Ament [mailto:johndam...@apache.org] Sent: Sunday, August 16, 2015 10:07 PM To: deltaspike dev@deltaspike.apache.org Subject: Wildfly 9 Tests? All, Looking at http://deltaspike.apache.org/documentation/build.html it seems we don't build and test against Wildfly 9, only 8. One key difference is that now the Arquillian container is separately managed. Is this simply an over sight? John
[jira] [Updated] (DELTASPIKE-955) Built in class deactivator
[
https://issues.apache.org/jira/browse/DELTASPIKE-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John D. Ament updated DELTASPIKE-955:
-
Component/s: Documentation
Configuration
Built in class deactivator
--
Key: DELTASPIKE-955
URL: https://issues.apache.org/jira/browse/DELTASPIKE-955
Project: DeltaSpike
Issue Type: New Feature
Components: Configuration, Core, Documentation
Affects Versions: 1.4.1
Reporter: John D. Ament
Assignee: John D. Ament
Fix For: 1.5.1
Add a built in ClassDeactivator that maybe reads from
apache-deltaspike.properties
Today I was reimplementing DS for the data module. One of the things I
noticed was that there's no built in support for deactivation (via plain
configuration). If look at
https://deltaspike.apache.org/documentation/spi.html#ClassDeactivator it
seems like one of the key features missing is to add a property, e.g.
{code}
deactivate.fqcn=true
{code}
Which would deactivate that class. Seems like a cool native deactivator that
we could bundle in by default, but still activate via config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (DELTASPIKE-955) Built in class deactivator
[
https://issues.apache.org/jira/browse/DELTASPIKE-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John D. Ament resolved DELTASPIKE-955.
--
Resolution: Fixed
Fix Version/s: 1.5.1
Built in class deactivator
--
Key: DELTASPIKE-955
URL: https://issues.apache.org/jira/browse/DELTASPIKE-955
Project: DeltaSpike
Issue Type: New Feature
Components: Configuration, Core, Documentation
Affects Versions: 1.4.1
Reporter: John D. Ament
Assignee: John D. Ament
Fix For: 1.5.1
Add a built in ClassDeactivator that maybe reads from
apache-deltaspike.properties
Today I was reimplementing DS for the data module. One of the things I
noticed was that there's no built in support for deactivation (via plain
configuration). If look at
https://deltaspike.apache.org/documentation/spi.html#ClassDeactivator it
seems like one of the key features missing is to add a property, e.g.
{code}
deactivate.fqcn=true
{code}
Which would deactivate that class. Seems like a cool native deactivator that
we could bundle in by default, but still activate via config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
