Re: [DISCUSS] updating prerequisite to Java 1.7 for DeltaSpike-1.8.x and higher?

2017-05-09 Thread Mark Struberg 
storing secrets in a users home folder.
I wanted to ensure that it only has read rights by the user but noone else. 
Similar to what ssh-keygen does.
This info only exists in Java7
Romain pointed me that this would only work for Unixoid systems though. But I 
think we could live with it.

Of course this is no show stopper - just a nice to have.

LieGrue,
strub


> Am 08.05.2017 um 21:05 schrieb John D. Ament :
> 
> What feature is that?
> 
> On May 8, 2017 2:51 PM, "Mark Struberg"  wrote:
> 
> Paths and other nio features for accessing file attributes.
> Those are only available in Java7, and I need those now for a new
> DeltaSpike feature...
> 
> Java6 is EOL since 2013 anyway.
> I don't even have a java6 jdk anymore...
> 
> LieGrue,
> strub
> 
> 
> 
>> Am 08.05.2017 um 20:28 schrieb Romain Manni-Bucau :
>> 
>> +0 for the same reason
>> 
>> 
>> Romain Manni-Bucau
>> @rmannibucau  |  Blog
>>  | Old Blog
>>  | Github  rmannibucau> |
>> LinkedIn  | JavaEE Factory
>> 
>> 
>> 2017-05-08 20:25 GMT+02:00 Thomas Andraschko > :
>> 
>>> +0
>>> There is no big benefit for using java7.
>>> IMO we should just upgrade to java8 if we start DS 2.0.
>>> 
>>> 2017-05-08 17:44 GMT+02:00 Mark Struberg :
>>> 
 Java9 is just around the corner and we still support Java6.
 Do we finally like to raise our prerequisites to Java7 at least?
 This would be for the upcoming 1.8.0 release and onwards.
 
 Wdyt?
 
 LieGrue,
 strub
 
>>>

[jira] [Created] (DELTASPIKE-1254) print full configuration on bootstrap

2017-05-09 Thread Mark Struberg (JIRA) 
Mark Struberg created DELTASPIKE-1254:
-

 Summary: print full configuration on bootstrap
 Key: DELTASPIKE-1254
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1254
 Project: DeltaSpike
  Issue Type: New Feature
  Components: Configuration
Affects Versions: 1.7.2
Reporter: Mark Struberg
Assignee: Mark Struberg
 Fix For: 1.8.0


Colleague asked for printing out all the ConfigSources + all configured values 
during boot. Basically the same information we now provide via JMX, but just in 
the log.

Of course this option should be off by default but might get enabled by a 
config property.

Technically this might get implemented in the ConfigExtension as easy as having 
a step in AfterDeploymentValidation which just collects the info and logs it 
out.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [DISCUSS] release 1.8.0 next week?

2017-05-09 Thread John D. Ament 
IMHO, we should resolve [1] first, and then figure out if when we want to
cut 1.8.0.

[1]:
https://lists.apache.org/thread.html/dd64597c0e79c7b2dfc2c5bdea09d7d12efc1979b41dc494b1ee8da4@%3Cdev.deltaspike.apache.org%3E


On Tue, May 9, 2017 at 8:18 AM Mark Struberg 
wrote:

> Hi folks!
>
> I'm currently working on a few tickets and would love to release early
> next week.
> Any objections?
>
> If you like to tacke some features and tickets then please shout out, so
> we can better coordinate the work on it.
>
> txs and LieGrue,
> strub

[jira] [Reopened] (DELTASPIKE-1252) data-documentation missing Optional return value

2017-05-09 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Matèrne reopened DELTASPIKE-1252:
-

You left the textual explanation in adoc:473

instead:
* The query method must either return an entity or a list of entities.

should:
* The query method must either return an entity or an Optional of an entity, a 
list of entities or a stream of entities



> data-documentation missing Optional return value
> 
>
> Key: DELTASPIKE-1252
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1252
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module, Documentation
>Affects Versions: 1.7.2
>Reporter: Jan Matèrne
>Assignee: John D. Ament
>Priority: Minor
> Fix For: 1.8.0
>
>
> http://deltaspike.apache.org/documentation/data.html lists the format for 
> methods:
> (Entity|List) (prefix)(Property[Comparator]){Operator Property 
> [Comparator]}
> Here java.util.Optional is missing:
> "(Entity|Optional|List) 
> (prefix)(Property[Comparator]){Operator Property [Comparator]}
>  
> Or in more concrete words:
> • The query method must either return an entity or an java.util.Optional 
> or a list of entities.
> • It must start with the findBy prefix ..."



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[DISCUSS] release 1.8.0 next week?

2017-05-09 Thread Mark Struberg 
Hi folks!

I'm currently working on a few tickets and would love to release early next 
week.
Any objections?

If you like to tacke some features and tickets then please shout out, so we can 
better coordinate the work on it.

txs and LieGrue,
strub

[jira] [Commented] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers

2017-05-09 Thread John D. Ament (JIRA) 

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002558#comment-16002558
 ] 

John D. Ament commented on DELTASPIKE-940:
--

While we shouldn't remove the old behavior pre-DS 2.0, it would be good to 
provide similar capabilities in both.

As a result, I think it makes sense to include qualifier in the look up while 
still allowing class based resolution.

> @Transactional and @EntityManagerConfig each use a different method to 
> resolve EntityManagers
> -
>
> Key: DELTASPIKE-940
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-940
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module, JPA-Module
>Reporter: Xavier Dury
>Assignee: John D. Ament
>Priority: Minor
> Fix For: 1.8.0
>
>
> When an application uses multiple {{EntityManager}}'s, there must be a way to 
> specify which one(s) should be used. Currently, {{@Transactional}} and 
> {{@EntityManagerConfig}} use different approaches:
> - {{@Transactional}} can take one or more qualifiers directly in its 
> {{qualifier()}} member ({{@Transactional(qualifier = MyDB.class)}})
> - While {{@EntityManagerConfig}} must define an {{EntityManagerResolver}} 
> ({{@EntityManagerConfig(entityManagerResolver = 
> MyDBEntityManagerResolver.class}})
> I think both should be unified and use a single way to specify which 
> {{EntityManager}} to use. IMHO, the {{@Transactional}} way of doing looks 
> better and should be applied to {{@EntityManagerConfig}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers

2017-05-09 Thread John D. Ament (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John D. Ament updated DELTASPIKE-940:
-
Fix Version/s: 1.8.0

> @Transactional and @EntityManagerConfig each use a different method to 
> resolve EntityManagers
> -
>
> Key: DELTASPIKE-940
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-940
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module, JPA-Module
>Reporter: Xavier Dury
>Assignee: John D. Ament
>Priority: Minor
> Fix For: 1.8.0
>
>
> When an application uses multiple {{EntityManager}}'s, there must be a way to 
> specify which one(s) should be used. Currently, {{@Transactional}} and 
> {{@EntityManagerConfig}} use different approaches:
> - {{@Transactional}} can take one or more qualifiers directly in its 
> {{qualifier()}} member ({{@Transactional(qualifier = MyDB.class)}})
> - While {{@EntityManagerConfig}} must define an {{EntityManagerResolver}} 
> ({{@EntityManagerConfig(entityManagerResolver = 
> MyDBEntityManagerResolver.class}})
> I think both should be unified and use a single way to specify which 
> {{EntityManager}} to use. IMHO, the {{@Transactional}} way of doing looks 
> better and should be applied to {{@EntityManagerConfig}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (DELTASPIKE-940) @Transactional and @EntityManagerConfig each use a different method to resolve EntityManagers

2017-05-09 Thread John D. Ament (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John D. Ament reassigned DELTASPIKE-940:


Assignee: John D. Ament  (was: Thomas Hug)

> @Transactional and @EntityManagerConfig each use a different method to 
> resolve EntityManagers
> -
>
> Key: DELTASPIKE-940
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-940
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module, JPA-Module
>Reporter: Xavier Dury
>Assignee: John D. Ament
>Priority: Minor
>
> When an application uses multiple {{EntityManager}}'s, there must be a way to 
> specify which one(s) should be used. Currently, {{@Transactional}} and 
> {{@EntityManagerConfig}} use different approaches:
> - {{@Transactional}} can take one or more qualifiers directly in its 
> {{qualifier()}} member ({{@Transactional(qualifier = MyDB.class)}})
> - While {{@EntityManagerConfig}} must define an {{EntityManagerResolver}} 
> ({{@EntityManagerConfig(entityManagerResolver = 
> MyDBEntityManagerResolver.class}})
> I think both should be unified and use a single way to specify which 
> {{EntityManager}} to use. IMHO, the {{@Transactional}} way of doing looks 
> better and should be applied to {{@EntityManagerConfig}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (DELTASPIKE-1193) Repository methods should consider Boolean and boolean the same

2017-05-09 Thread John D. Ament (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John D. Ament reassigned DELTASPIKE-1193:
-

Assignee: John D. Ament

> Repository methods should consider Boolean and boolean the same
> ---
>
> Key: DELTASPIKE-1193
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1193
> Project: DeltaSpike
>  Issue Type: Improvement
>  Components: Data-Module
>Reporter: John D. Ament
>Assignee: John D. Ament
>
> https://github.com/apache/deltaspike/blob/master/deltaspike/modules/data/impl/src/main/java/org/apache/deltaspike/data/impl/property/MethodPropertyImpl.java#L79
> In this case, we're treating boolean as valid for is methods, the same is not 
> applied to Boolean types.  This means your entities can't have Boolean 
> methods.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (DELTASPIKE-1225) deltaspike.testcontrol.stop_container should stop the container after all tests executed

2017-05-09 Thread John D. Ament (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John D. Ament reassigned DELTASPIKE-1225:
-

Assignee: John D. Ament

> deltaspike.testcontrol.stop_container should stop the container after all 
> tests executed
> 
>
> Key: DELTASPIKE-1225
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1225
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: TestControl
>Affects Versions: 1.7.2
>Reporter: Remo
>Assignee: John D. Ament
>Priority: Minor
>
> deltaspike.testcontrol.stop_container is very useful to speed up test cases. 
> However, it results that the container does not getting shutdown at all. This 
> should still be done after ALL the tests have been executed.
> With Gradle the current behavior is quite a problem. The Gradle Wrappers keep 
> by default the VM running. And as such, test cases must properly cleanup and 
> free resources. Otherwise the Gradle wrapper consumes more and more memory 
> and dies at some point.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (DELTASPIKE-1229) Allow the use of @Alternative to implement a custom TimestampsProvider

2017-05-09 Thread John D. Ament (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John D. Ament reassigned DELTASPIKE-1229:
-

Assignee: John D. Ament

> Allow the use of @Alternative to implement a custom TimestampsProvider
> --
>
> Key: DELTASPIKE-1229
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1229
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Data-Module, JPA-Module
>Affects Versions: 1.7.2
> Environment: Deltaspike 1.7.2. CDI 1.1 Wildfly AS 9.0.2.Final
>Reporter: Nico Schlebusch
>Assignee: John D. Ament
>
> I'm using the JPA {{@EntityListeners(AuditEntityListener.class)}} and the 
> audit functionality of Deltaspike Data ({{@CreatedOn}}, {{@ModifiedOn}} and 
> {{@ModifiedBy}} annotations) on an entity bean with the difference that I 
> have a custom implementation of {{java.time.ChronoLocalDateTime}} which 
> converts any {{LocalDateTime}} + {{ZoneOffset}} OR a {{ZonedDateTime}} to be 
> the UTC date & time.
> Is there a way to implement my own 
> {{org.apache.deltaspike.data.impl.audit.PrePersistAuditListener}} and 
> {{org.apache.deltaspike.data.impl.audit.PreUpdateAuditListener}} and use them 
> to create the instance of {{UTCDateTime}} required by he fields marked with 
> {{@InsertedOn}} and {{@ModiefiedOn}}?
> See this [SO 
> Question|http://stackoverflow.com/questions/41057116/deltaspike-data-cdi-jpa-custom-prepersistauditlistener-and-preupdateauditlis]
>  and the discussion on this [mail 
> thread|https://lists.apache.org/thread.html/c47a6187d03fc8f665c6b3c7ab760e80084db3b8d4f83fe9d34015d8@%3Cusers.deltaspike.apache.org%3E]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (DELTASPIKE-1236) unit testing a servlet that uses injection

2017-05-09 Thread John D. Ament (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John D. Ament closed DELTASPIKE-1236.
-
Resolution: Won't Fix

> unit testing a servlet that uses injection
> --
>
> Key: DELTASPIKE-1236
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1236
> Project: DeltaSpike
>  Issue Type: Improvement
>Affects Versions: 1.7.2
> Environment: Tomcat
>Reporter: Stephen More
>
> I have been using org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner 
> to test JSF backing beans and everything seems to be working well.
> At this point I am struggling how to test a plain old servlet that uses 
> injection, are there any examples anywhere ?
> The current - non working test code can be found here: 
> https://github.com/mores/maven-examples/tree/master/prime-deltaspike
> Servlet works as expected when deployed - output is survey says: 3.96 
> (https://github.com/mores/maven-examples/blob/master/prime-deltaspike/src/main/java/org/test/MyServlet.java)
> But when trying to run the test, windowContext appears to be null. ( 
> https://github.com/mores/maven-examples/blob/master/prime-deltaspike/src/test/java/org/test/MyServletTest.java
>  )



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DELTASPIKE-1240) [Config] add List support

2017-05-09 Thread Mark Struberg (JIRA) 

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002546#comment-16002546
 ] 

Mark Struberg commented on DELTASPIKE-1240:
---

Plz wait John, we should publish the docs once we release 1.8.0

Otherwise we will have docs for features which are not yet publicly available.

> [Config] add List support
> -
>
> Key: DELTASPIKE-1240
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1240
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Configuration
>Affects Versions: 1.7.2
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 1.8.0
>
>
> Currently there is no built-in way to configure lists of values. This is 
> useful if you think about e.g. something like
> {code}
> mycompany.myproj.batch.error.email=someone@mycomp,else@mycomp,ops@mycomp
> {code}
> Any ',' character inside the payload might get escaped via '\,' and a single 
> backslash '\' itself with double-backslash '\\'



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DELTASPIKE-1240) [Config] add List support

2017-05-09 Thread John D. Ament (JIRA) 

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002541#comment-16002541
 ] 

John D. Ament commented on DELTASPIKE-1240:
---

FYI, while there's documentation committed in this ticket it was never 
published.  I'm about to publish the docs.

> [Config] add List support
> -
>
> Key: DELTASPIKE-1240
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1240
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Configuration
>Affects Versions: 1.7.2
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 1.8.0
>
>
> Currently there is no built-in way to configure lists of values. This is 
> useful if you think about e.g. something like
> {code}
> mycompany.myproj.batch.error.email=someone@mycomp,else@mycomp,ops@mycomp
> {code}
> Any ',' character inside the payload might get escaped via '\,' and a single 
> backslash '\' itself with double-backslash '\\'



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (DELTASPIKE-1252) data-documentation missing Optional return value

2017-05-09 Thread John D. Ament (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John D. Ament resolved DELTASPIKE-1252.
---
Resolution: Fixed

> data-documentation missing Optional return value
> 
>
> Key: DELTASPIKE-1252
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1252
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module, Documentation
>Affects Versions: 1.7.2
>Reporter: Jan Matèrne
>Assignee: John D. Ament
>Priority: Minor
> Fix For: 1.8.0
>
>
> http://deltaspike.apache.org/documentation/data.html lists the format for 
> methods:
> (Entity|List) (prefix)(Property[Comparator]){Operator Property 
> [Comparator]}
> Here java.util.Optional is missing:
> "(Entity|Optional|List) 
> (prefix)(Property[Comparator]){Operator Property [Comparator]}
>  
> Or in more concrete words:
> • The query method must either return an entity or an java.util.Optional 
> or a list of entities.
> • It must start with the findBy prefix ..."



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DELTASPIKE-1252) data-documentation missing Optional return value

2017-05-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002533#comment-16002533
 ] 

ASF subversion and git services commented on DELTASPIKE-1252:
-

Commit d1e4739e3b25fc93e4206344d61ddb24dc1a1391 in deltaspike's branch 
refs/heads/master from [~johndament]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=d1e4739 ]

DELTASPIKE-1252 - Adding Java 8 semantics to EBNF-like form.


> data-documentation missing Optional return value
> 
>
> Key: DELTASPIKE-1252
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1252
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module, Documentation
>Affects Versions: 1.7.2
>Reporter: Jan Matèrne
>Assignee: John D. Ament
>Priority: Minor
> Fix For: 1.8.0
>
>
> http://deltaspike.apache.org/documentation/data.html lists the format for 
> methods:
> (Entity|List) (prefix)(Property[Comparator]){Operator Property 
> [Comparator]}
> Here java.util.Optional is missing:
> "(Entity|Optional|List) 
> (prefix)(Property[Comparator]){Operator Property [Comparator]}
>  
> Or in more concrete words:
> • The query method must either return an entity or an java.util.Optional 
> or a list of entities.
> • It must start with the findBy prefix ..."



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DELTASPIKE-1252) data-documentation missing Optional return value

2017-05-09 Thread John D. Ament (JIRA) 

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002531#comment-16002531
 ] 

John D. Ament commented on DELTASPIKE-1252:
---

Fair point... stream is missing there as well.

> data-documentation missing Optional return value
> 
>
> Key: DELTASPIKE-1252
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1252
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module, Documentation
>Affects Versions: 1.7.2
>Reporter: Jan Matèrne
>Priority: Minor
> Fix For: 1.8.0
>
>
> http://deltaspike.apache.org/documentation/data.html lists the format for 
> methods:
> (Entity|List) (prefix)(Property[Comparator]){Operator Property 
> [Comparator]}
> Here java.util.Optional is missing:
> "(Entity|Optional|List) 
> (prefix)(Property[Comparator]){Operator Property [Comparator]}
>  
> Or in more concrete words:
> • The query method must either return an entity or an java.util.Optional 
> or a list of entities.
> • It must start with the findBy prefix ..."



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (DELTASPIKE-1252) data-documentation missing Optional return value

2017-05-09 Thread John D. Ament (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John D. Ament updated DELTASPIKE-1252:
--
Fix Version/s: 1.8.0

> data-documentation missing Optional return value
> 
>
> Key: DELTASPIKE-1252
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1252
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module, Documentation
>Affects Versions: 1.7.2
>Reporter: Jan Matèrne
>Assignee: John D. Ament
>Priority: Minor
> Fix For: 1.8.0
>
>
> http://deltaspike.apache.org/documentation/data.html lists the format for 
> methods:
> (Entity|List) (prefix)(Property[Comparator]){Operator Property 
> [Comparator]}
> Here java.util.Optional is missing:
> "(Entity|Optional|List) 
> (prefix)(Property[Comparator]){Operator Property [Comparator]}
>  
> Or in more concrete words:
> • The query method must either return an entity or an java.util.Optional 
> or a list of entities.
> • It must start with the findBy prefix ..."



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (DELTASPIKE-1252) data-documentation missing Optional return value

2017-05-09 Thread John D. Ament (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John D. Ament reassigned DELTASPIKE-1252:
-

Assignee: John D. Ament

> data-documentation missing Optional return value
> 
>
> Key: DELTASPIKE-1252
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1252
> Project: DeltaSpike
>  Issue Type: Bug
>  Components: Data-Module, Documentation
>Affects Versions: 1.7.2
>Reporter: Jan Matèrne
>Assignee: John D. Ament
>Priority: Minor
> Fix For: 1.8.0
>
>
> http://deltaspike.apache.org/documentation/data.html lists the format for 
> methods:
> (Entity|List) (prefix)(Property[Comparator]){Operator Property 
> [Comparator]}
> Here java.util.Optional is missing:
> "(Entity|Optional|List) 
> (prefix)(Property[Comparator]){Operator Property [Comparator]}
>  
> Or in more concrete words:
> • The query method must either return an entity or an java.util.Optional 
> or a list of entities.
> • It must start with the findBy prefix ..."



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (DELTASPIKE-1253) allow PropertyFileConfig to also pick up property files from the file system

2017-05-09 Thread Mark Struberg (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Struberg resolved DELTASPIKE-1253.
---
Resolution: Fixed

> allow PropertyFileConfig to also pick up property files from the file system
> 
>
> Key: DELTASPIKE-1253
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1253
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Configuration
>Affects Versions: 1.7.2
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 1.8.0
>
>
> Currently PropertyFileConfig only picks up properties with a given name from 
> the classpath.
> It should also be allowed to use other URLs like file:// or http:// to pick 
> up configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DELTASPIKE-1253) allow PropertyFileConfig to also pick up property files from the file system

2017-05-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002350#comment-16002350
 ] 

ASF subversion and git services commented on DELTASPIKE-1253:
-

Commit e2b54d4db684582e563aaaf5aa09c00cee42e6f7 in deltaspike's branch 
refs/heads/master from rmannibucau
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=e2b54d4 ]

DELTASPIKE-1253 handling file path too


> allow PropertyFileConfig to also pick up property files from the file system
> 
>
> Key: DELTASPIKE-1253
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1253
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Configuration
>Affects Versions: 1.7.2
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 1.8.0
>
>
> Currently PropertyFileConfig only picks up properties with a given name from 
> the classpath.
> It should also be allowed to use other URLs like file:// or http:// to pick 
> up configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DELTASPIKE-1253) allow PropertyFileConfig to also pick up property files from the file system

2017-05-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002342#comment-16002342
 ] 

ASF subversion and git services commented on DELTASPIKE-1253:
-

Commit e7fce70c2d70ed3825119d6852110ef0dc8f4ad9 in deltaspike's branch 
refs/heads/master from [~struberg]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=e7fce70 ]

DELTASPIKE-1253 add new features to our documentation


> allow PropertyFileConfig to also pick up property files from the file system
> 
>
> Key: DELTASPIKE-1253
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1253
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Configuration
>Affects Versions: 1.7.2
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 1.8.0
>
>
> Currently PropertyFileConfig only picks up properties with a given name from 
> the classpath.
> It should also be allowed to use other URLs like file:// or http:// to pick 
> up configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DELTASPIKE-1253) allow PropertyFileConfig to also pick up property files from the file system

2017-05-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16002318#comment-16002318
 ] 

ASF subversion and git services commented on DELTASPIKE-1253:
-

Commit 270f3d0bbbc8e4e5ea8328cd23e56101bef9a4a7 in deltaspike's branch 
refs/heads/master from [~struberg]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=270f3d0 ]

DELTASPIKE-1253 support file:// for PropertyFileConfig

A PropertyFileConfig can now also pick up other URLs than from the classpath.
By returning a "file:///var/opt/myapp/my.properties" you might now load 
properties
from a file on the classpath.


> allow PropertyFileConfig to also pick up property files from the file system
> 
>
> Key: DELTASPIKE-1253
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1253
> Project: DeltaSpike
>  Issue Type: New Feature
>  Components: Configuration
>Affects Versions: 1.7.2
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 1.8.0
>
>
> Currently PropertyFileConfig only picks up properties with a given name from 
> the classpath.
> It should also be allowed to use other URLs like file:// or http:// to pick 
> up configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (DELTASPIKE-1253) allow PropertyFileConfig to also pick up property files from the file system

2017-05-09 Thread Mark Struberg (JIRA) 
Mark Struberg created DELTASPIKE-1253:
-

 Summary: allow PropertyFileConfig to also pick up property files 
from the file system
 Key: DELTASPIKE-1253
 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1253
 Project: DeltaSpike
  Issue Type: New Feature
  Components: Configuration
Affects Versions: 1.7.2
Reporter: Mark Struberg
Assignee: Mark Struberg
 Fix For: 1.8.0


Currently PropertyFileConfig only picks up properties with a given name from 
the classpath.

It should also be allowed to use other URLs like file:// or http:// to pick up 
configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)