[jira] [Updated] (ZEST-43) Solr Indexing has dependency in RDF library
[ https://issues.apache.org/jira/browse/ZEST-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin updated ZEST-43: Affects Version/s: 2.0 Solr Indexing has dependency in RDF library --- Key: ZEST-43 URL: https://issues.apache.org/jira/browse/ZEST-43 Project: Zest Issue Type: Bug Affects Versions: 2.0 Reporter: Niclas Hedhman This dependency is only for the EntityStateSerializer class, and I suspect that ValueSerialization should/could be used instead, or be made to be suitable for the tasl/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZEST-38) Scheduler throws NPE
[ https://issues.apache.org/jira/browse/ZEST-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin updated ZEST-38: Fix Version/s: 2.1 Scheduler throws NPE Key: ZEST-38 URL: https://issues.apache.org/jira/browse/ZEST-38 Project: Zest Issue Type: Bug Reporter: Niclas Hedhman Assignee: Niclas Hedhman Fix For: 2.1 Not sure why/how/when, but it happens first access... java.lang.NullPointerException at org.qi4j.library.scheduler.SchedulerMixin.dispatchForExecution(SchedulerMixin.java:183) at org.qi4j.library.scheduler.SchedulerMixin.scheduleCron(SchedulerMixin.java:120) at org.qi4j.api.unitofwork.concern.UnitOfWorkConcern.invoke(UnitOfWorkConcern.java:89) at org.qi4j.api.unitofwork.concern.UnitOfWorkConcern.invoke(UnitOfWorkConcern.java:89) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZEST-42) Changes to Directory naming in FileEntityStore
[
https://issues.apache.org/jira/browse/ZEST-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-42:
Fix Version/s: 2.1
Changes to Directory naming in FileEntityStore
--
Key: ZEST-42
URL: https://issues.apache.org/jira/browse/ZEST-42
Project: Zest
Issue Type: Improvement
Reporter: Niclas Hedhman
Assignee: Niclas Hedhman
Fix For: 2.1
The FileEntityStore is using the FileConfig library to create a directory to
store the entities in.
The FileConfig defines those as
MAC; {user}/Library/Application Support/{application}
Linux; {user}/.{application}/data
Windows; {user}/Application Data/{application}/data
The FileEntityStore then appends the identity of the FileEntityStore, and a
static data/ location after that. The identity is to ensure that multiple
FileEntityStores can be used nicely together, but the data is IMHO
unnecessary and should be removed.
Now, IF a configuration is provided to FileEntityStore, then the above
location is the root path. If no configuration is given at all, then
System.getProperty( user.dir ) + /qi4j/filestore/ is used as root path.
The root path is used as the location for any relative paths specified in the
configuration, but can be completely overridden with an absolute path..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ZEST-22) Add toValue() and toEntity() methods to the Qi4j API.
[ https://issues.apache.org/jira/browse/ZEST-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin updated ZEST-22: Fix Version/s: 2.1 Add toValue() and toEntity() methods to the Qi4j API. - Key: ZEST-22 URL: https://issues.apache.org/jira/browse/ZEST-22 Project: Zest Issue Type: Bug Reporter: Niclas Hedhman Assignee: Niclas Hedhman Fix For: 2.1 Rickard added the support for handling Associations in Values, and we also now have the full support of sharing super-types between Entities and Values. So, it would make sense that if I declare the assembly; module.entities( Person.class ); module.values( Person.class ); that I could do; Person entity = ...; Person value = api.toValue( Person,class, entity ); as well as the other way around; Person value = ...; Person entity = api.toEntity( Person.class, entity ); The implementation of this is fairly small and straight forward, and I have most of it in place in my project already, but I think it really belongs in the API itself, as this would be super-neat for Rest APIs and other work outside of UnitOfWorks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Apache Zest by-laws
On Thu, Jul 9, 2015 at 3:39 PM, Paul Merlin p...@nosphere.org wrote: So, we should review theses to ASF-ize them, shouldn't we? Yes, I think so... BUT, I can't find a Version property on issues, nor the Roadmap view I'm used to. Do I need some JIRA privileges to handle this? I have added you (and Jiri) as Administrators, as you are on the PMC. Then, to produce accurate release notes we'll have to create issues for changes that happened before entering the ASF and for changes not already recorded as issues. Something I can do before we release 2.1. Perhaps you can pick up some of that from the old Jira system? Cheers -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
[jira] [Updated] (ZEST-39) FileEntityStoreMixin throws ArithmeticException
[ https://issues.apache.org/jira/browse/ZEST-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin updated ZEST-39: Affects Version/s: 2.0 FileEntityStoreMixin throws ArithmeticException --- Key: ZEST-39 URL: https://issues.apache.org/jira/browse/ZEST-39 Project: Zest Issue Type: Bug Affects Versions: 2.0 Reporter: Niclas Hedhman This exception is quite interesting. No idea how this was possible, but happened; java.lang.ArithmeticException: / by zero at org.qi4j.entitystore.file.FileEntityStoreMixin.getDataFile(FileEntityStoreMixin.java:358) at org.qi4j.entitystore.file.FileEntityStoreMixin.getDataFile(FileEntityStoreMixin.java:369) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZEST-31) ElasticSearch Query dereferences Associations
[ https://issues.apache.org/jira/browse/ZEST-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin updated ZEST-31: Affects Version/s: 2.0 ElasticSearch Query dereferences Associations - Key: ZEST-31 URL: https://issues.apache.org/jira/browse/ZEST-31 Project: Zest Issue Type: Bug Affects Versions: 2.0 Reporter: Niclas Hedhman I think there is a problem in the ElasticSearch Query system, when it comes to handling Associations. I haven't investigated yet, but it tried to dereference the EntityReference of an Association, which of course causes an EntityTypeNotFoundException, since originating Module is down in the Infra Layer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZEST-22) Add toValue() and toEntity() methods to the Qi4j API.
[ https://issues.apache.org/jira/browse/ZEST-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin updated ZEST-22: Issue Type: New Feature (was: Bug) Add toValue() and toEntity() methods to the Qi4j API. - Key: ZEST-22 URL: https://issues.apache.org/jira/browse/ZEST-22 Project: Zest Issue Type: New Feature Reporter: Niclas Hedhman Assignee: Niclas Hedhman Fix For: 2.1 Rickard added the support for handling Associations in Values, and we also now have the full support of sharing super-types between Entities and Values. So, it would make sense that if I declare the assembly; module.entities( Person.class ); module.values( Person.class ); that I could do; Person entity = ...; Person value = api.toValue( Person,class, entity ); as well as the other way around; Person value = ...; Person entity = api.toEntity( Person.class, entity ); The implementation of this is fairly small and straight forward, and I have most of it in place in my project already, but I think it really belongs in the API itself, as this would be super-neat for Rest APIs and other work outside of UnitOfWorks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZEST-47) Complex Configuration Types
[ https://issues.apache.org/jira/browse/ZEST-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin updated ZEST-47: Issue Type: New Feature (was: Bug) Complex Configuration Types --- Key: ZEST-47 URL: https://issues.apache.org/jira/browse/ZEST-47 Project: Zest Issue Type: New Feature Reporter: Niclas Hedhman See https://ops4j1.jira.com/projects/QI/issues/QI-350 To allow complex Configuration types to be initialized from properties files. Since we now have ValueSerialization, I suggest that is used as an alternate configuration option to Properties files, so I can have YAML, XML or JSON as the static initialization format. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZEST-19) Using Qi4j as a skeleton framework in a high throughput, highly concurrent servlet deployment (and problems with race conditions)
[ https://issues.apache.org/jira/browse/ZEST-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Merlin updated ZEST-19: Affects Version/s: 2.0 Using Qi4j as a skeleton framework in a high throughput, highly concurrent servlet deployment (and problems with race conditions) - Key: ZEST-19 URL: https://issues.apache.org/jira/browse/ZEST-19 Project: Zest Issue Type: Bug Affects Versions: 2.0 Environment: Web app deployed in tomcat Reporter: Parisinos Tasos When multiple (tomcat request servicing) threads use the same Qi4j application, problems occur using ValueBuilderFactoryT and TransientBuilderFactoryT (even when using Module instead) that most probably are race conditions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZEST-29) Move the Javascript library from rhino to nashorn
[
https://issues.apache.org/jira/browse/ZEST-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-29:
Issue Type: Improvement (was: Bug)
Move the Javascript library from rhino to nashorn
-
Key: ZEST-29
URL: https://issues.apache.org/jira/browse/ZEST-29
Project: Zest
Issue Type: Improvement
Reporter: Paul Merlin
Labels: java8, javascript, library
Java 8 comes with a modern javascript engine called {{nashorn}}.
We should move the {{javascript}} library from {{rhino}} to {{nashorn}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Deprecated the Conversion Library
Niclas, I extensively use the Conversion library in my apps. Does the new UoW support for conversion between Entities and Values allows for type-relaxed conversion and does it provide a way to insert custom conversion code (see 'prototypeOpportunity' in Conversion library) ? /Paul Niclas Hedhman a écrit : Since the UnitOfWork now provides a more integrated solution to conversion between Entities and Values, the Conversion Library has no real purpose. However, I have one small app still using it, and instead of simply removing it, I am deprecating it and will be dropped in 3.0 Cheers
Re: Deprecated the Conversion Library
Some use-cases: - don't expose the whole state (eg. password hashes) - computed/transformed state (eg. entity state ~ value state) Paul Merlin a écrit : Niclas, I extensively use the Conversion library in my apps. Does the new UoW support for conversion between Entities and Values allows for type-relaxed conversion and does it provide a way to insert custom conversion code (see 'prototypeOpportunity' in Conversion library) ? /Paul Niclas Hedhman a écrit : Since the UnitOfWork now provides a more integrated solution to conversion between Entities and Values, the Conversion Library has no real purpose. However, I have one small app still using it, and instead of simply removing it, I am deprecating it and will be dropped in 3.0 Cheers
Re: Deprecated the Conversion Library
Niclas Hedhman a écrit : No it doesn't, but then I think we should spend the time to find the additional solutions to support these usecases in the primary toEntity/toValue mechanism. And with the deprecation, it is clear that these cases will have to get some work prior to 3.0. Makes sense? Yep, I'm good with that!
Re: Build failed in Jenkins: Zest - Check 2.1-SNAPSHOT distributions from develop branch on Java8 (OpenJDK) #3
I have reported to Infra that this slave is lacking Xvfb...
On Thu, Jul 9, 2015 at 3:21 AM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
See
https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/3/changes
Changes:
[hedmann] Replaced Qi4j with Zest in main documentation.
[paulmerlin] ZEST-40 README NOTICE properly UTF-8 encoded
[paulmerlin] ZEST-40 apply rename on build system
[paulmerlin] ZEST-40 Javadoc Overview
[hedmann] Wrong encoding must have been used earlier. Changed to UTF-8 for
all tradmarks ™, and merged in DocUpdate branch
[paulmerlin] ZEST-40 Fix remaining mojibakes for non-UTF-8 trademarks
[paulmerlin] ZEST-40 Use Thien logo in documentation minisite
[paulmerlin] Build javadocs in full UTF-8
[paulmerlin] ZEST-40 Various Qi4j - Zest renames and links fixes
[paulmerlin] lang-groovy: new tests and documentation review!
--
Started by an SCM change
Building remotely on jenkins-ubuntu-1404-4gb-e8e (jenkins-cloud-4GB
cloud-slave Ubuntu ubuntu) in workspace
https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/ws/
Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/zest-qi4j.git
git init
https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/ws/
# timeout=10
Fetching upstream changes from
https://git-wip-us.apache.org/repos/asf/zest-qi4j.git
git --version # timeout=10
git fetch --tags --progress
https://git-wip-us.apache.org/repos/asf/zest-qi4j.git
+refs/heads/*:refs/remotes/origin/*
git config remote.origin.url
https://git-wip-us.apache.org/repos/asf/zest-qi4j.git # timeout=10
git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* #
timeout=10
git config remote.origin.url
https://git-wip-us.apache.org/repos/asf/zest-qi4j.git # timeout=10
Fetching upstream changes from
https://git-wip-us.apache.org/repos/asf/zest-qi4j.git
git fetch --tags --progress
https://git-wip-us.apache.org/repos/asf/zest-qi4j.git
+refs/heads/*:refs/remotes/origin/*
git rev-parse refs/remotes/origin/develop^{commit} # timeout=10
git rev-parse refs/remotes/origin/origin/develop^{commit} # timeout=10
Checking out Revision cccbc92db02a3f9a2793d0ddd88ac8b4be4b131e
(refs/remotes/origin/develop)
git config core.sparsecheckout # timeout=10
git checkout -f cccbc92db02a3f9a2793d0ddd88ac8b4be4b131e
git rev-list 2868e9f6b3301c6393f8c0298ba1d74215faa9af # timeout=10
Xvfb starting$ /usr/bin/Xvfb :1 -screen 0 1024x768x24 -fbdir
/jenkins/2015-07-09_00-21-124292864023472364944xvfb
FATAL: Cannot run program /usr/bin/Xvfb: error=2, No such file or
directory
java.io.IOException: Cannot run program /usr/bin/Xvfb: error=2, No such
file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1047)
at hudson.Proc$LocalProc.init(Proc.java:244)
at hudson.Proc$LocalProc.init(Proc.java:216)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:780)
at hudson.Launcher$ProcStarter.start(Launcher.java:360)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1078)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.init(UNIXProcess.java:186)
at java.lang.ProcessImpl.start(ProcessImpl.java:130)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1028)
... 14 more
--
Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java
Jenkins build is back to normal : Zest - Check develop branch on Java7 (Oracle JDK) #40
See https://builds.apache.org/job/Zest%20-%20Check%20develop%20branch%20on%20Java7%20(Oracle%20JDK)/40/changes
Re: Apache Zest by-laws
Gang, FIY, we already have some by-laws content divided in: https://zest.apache.org/community/participate.html https://zest.apache.org/community/playing_field.html https://zest.apache.org/community/codebase.html What we don't actually do, and maybe should, is maintain a CHANGES files. I like the idea and would like to start building one for 2.0 - 2.1 changes. Something that should be easy to read, much easier than SCM history. WDYAT? /Paul Niclas Hedhman a écrit : A discussion erupted recently on ComDev (Community Development mailing list, open to all I think) about project specific by-laws. It was highlighted that the Board resolution for creating projects instructs the PMC to create the by-laws for the project. The conclusion of that thread was roughly; 1. Projects are allowed to craft their own by-laws. 2. When this text was created, it was not known how easy it is to get things wrong. 3. Over time, many/most projects operated without explicit by-laws. 4. Board would assume, if intervening, that the HTTPd project's by-laws would apply by default. 5. It would be better for the project to spell it out on its own website. So, I suggest that we all take a look at the HTTPd's by-laws and bring up anything we have questions about, disagrees with or perhaps don't understand. However I can't find those right now, unless what people mean are the guidelines... http://httpd.apache.org/dev/guidelines.html The immediate thing is Commit-Then-Review vs Review-Then-Commit. Almost no projects do RTC for 'develop', only for changes in stable branches. In general RTC slows down progress a bit, and I don't think we need it, although in reality we are doing it with feature branches Cheers
Build failed in Jenkins: Zest - Check 2.1-SNAPSHOT distributions from develop branch on Java8 (OpenJDK) #4
See https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/4/changes Changes: [hedmann] Missing inclusion of Metrics Library docs. [hedmann] Deprecating the Conversion library, as UnitOfWork now provides this functionality. [hedmann] Incorrect claim that SLF4J is used by the library. No logging output is taking place from the library itself. [hedmann] Giving some love to the InvocationCache library, which was simply in a very bad shape. [hedmann] Re-enable Test, since it now passes. [hedmann] Adding some documentation to Locking library. -- [...truncated 781 lines...] https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/ws/libraries/sql/src/main/java/org/qi4j/library/sql/common/Databases.java:87: warning: no @param for visitor public void query( String sql, ResultSetVisitor visitor ) ^ https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/ws/libraries/sql/src/main/java/org/qi4j/library/sql/common/Databases.java:87: warning: no @throws for java.sql.SQLException public void query( String sql, ResultSetVisitor visitor ) ^ https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/ws/libraries/sql/src/main/java/org/qi4j/library/sql/common/Databases.java:99: warning: no @param for sql public void query( String sql, StatementVisitor statement, ResultSetVisitor resultsetVisitor ) ^ https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/ws/libraries/sql/src/main/java/org/qi4j/library/sql/common/Databases.java:99: warning: no @param for statement public void query( String sql, StatementVisitor statement, ResultSetVisitor resultsetVisitor ) ^ https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/ws/libraries/sql/src/main/java/org/qi4j/library/sql/common/Databases.java:99: warning: no @param for resultsetVisitor public void query( String sql, StatementVisitor statement, ResultSetVisitor resultsetVisitor ) ^ https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/ws/libraries/sql/src/main/java/org/qi4j/library/sql/common/Databases.java:99: warning: no @throws for java.sql.SQLException public void query( String sql, StatementVisitor statement, ResultSetVisitor resultsetVisitor ) ^ https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/ws/libraries/sql/src/main/java/org/qi4j/library/sql/common/Databases.java:130: warning: no @param for sql public InputResultSet, SQLException query( final String sql ) ^ https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/ws/libraries/sql/src/main/java/org/qi4j/library/sql/common/Databases.java:130: warning: no @return public InputResultSet, SQLException query( final String sql ) ^ https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/ws/libraries/sql/src/main/java/org/qi4j/library/sql/common/Databases.java:178: warning: no @param for sql public InputResultSet, SQLException query( final String sql, final StatementVisitor visitor ) ^ https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/ws/libraries/sql/src/main/java/org/qi4j/library/sql/common/Databases.java:178: warning: no @param for visitor public InputResultSet, SQLException query( final String sql, final StatementVisitor visitor ) ^ https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/ws/libraries/sql/src/main/java/org/qi4j/library/sql/common/Databases.java:178: warning: no @return public InputResultSet, SQLException query( final String sql, final StatementVisitor visitor ) ^ https://builds.apache.org/job/Zest%20-%20Check%202.1-SNAPSHOT%20distributions%20from%20develop%20branch%20on%20Java8%20(OpenJDK)/ws/libraries/sql/src/main/java/org/qi4j/library/sql/common/Databases.java:39: warning: no @param for source public Databases( DataSource source ) ^
