You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@batchee.apache.org by st...@apache.org on 2014/03/30 12:35:45 UTC

[2/6] git commit: BATCHEE-16 move back to JAR

BATCHEE-16 move back to JAR


Project: http://git-wip-us.apache.org/repos/asf/incubator-batchee/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-batchee/commit/6f6a7466
Tree: http://git-wip-us.apache.org/repos/asf/incubator-batchee/tree/6f6a7466
Diff: http://git-wip-us.apache.org/repos/asf/incubator-batchee/diff/6f6a7466

Branch: refs/heads/master
Commit: 6f6a7466a6560fa9893a99becd21db7a1dc5e0af
Parents: 02a6a85
Author: Mark Struberg <st...@apache.org>
Authored: Wed Mar 26 21:20:12 2014 +0100
Committer: Mark Struberg <st...@apache.org>
Committed: Sun Mar 30 10:17:24 2014 +0200

----------------------------------------------------------------------
 gui/servlet/pom.xml | 1 -
 1 file changed, 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-batchee/blob/6f6a7466/gui/servlet/pom.xml
----------------------------------------------------------------------
diff --git a/gui/servlet/pom.xml b/gui/servlet/pom.xml
index a4e540f..3fa6bd3 100644
--- a/gui/servlet/pom.xml
+++ b/gui/servlet/pom.xml
@@ -28,7 +28,6 @@
 
   <artifactId>batchee-servlet</artifactId>
   <name>BatchEE :: GUI :: Servlet</name>
-  <packaging>war</packaging>
 
   <dependencies>
     <dependency>


Re: Fwd: [2/6] git commit: BATCHEE-16 move back to JAR

Posted by Romain Manni-Bucau <rm...@gmail.com>.
the point is when deploying all embedding you want both and we want
both gui be very close (the same actually) so this is a good trade
off. Write actions are now disabled so it should be fine. Last point
for 0.1 I think we don't really care. 0.1 is really about jbatch
module, then tooling around IMHO.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau



2014-03-30 21:41 GMT+02:00 Mark Struberg <st...@yahoo.de>:
> Ok, I c. Why not make an own batchee-reporting WAR? Much easier and this is really a benefit.
> The problem I have with the solution of making the batchee-servlet a WAR is that you would first need to disable all the 'active' options to use it. It must really only be a reporting WAR.
>
> LieGrue,
> strub
>
>
> On Sunday, 30 March 2014, 21:38, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
> I run batches with batchee cli and have the reporting thanks to the war.
>>Romain Manni-Bucau
>>Twitter: @rmannibucau
>>Blog: http://rmannibucau.wordpress.com/
>>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>Github: https://github.com/rmannibucau
>>
>>
>>
>>
>>2014-03-30 21:30 GMT+02:00 Mark Struberg <st...@yahoo.de>:
>>> I don't see the benefit. Your original batch jobs already need some way to start them. Are you not using the batchee-servlet or JAX-RS for it? How do you start them?
>>>
>>> The batchee-servlet does allow full control over the JobOperator, but without having the batches in your ClassPath, you can only utilize a small part of it (reading out the status). But this is already available via the parts you need in your JOB WARs anyway...
>>>
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>> On Sunday, 30 March 2014, 19:43, Romain Manni-Bucau <rm...@gmail.com> wrote:
>>>
>>> I dont agree. YOU want to control your batches with it, I just want to
>>>>read data about executions and that's really useful to drop anoter war
>>>>instead of updating an existing app. That's really mandatory Mark. We
>>>>can release it in alpha or printing a warning but we need it.
>>>>Romain Manni-Bucau
>>>>Twitter: @rmannibucau
>>>>Blog: http://rmannibucau.wordpress.com/
>>>>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>>Github: https://github.com/rmannibucau
>>>>
>>>>
>>>>
>>>>
>>>>2014-03-30 19:39 GMT+02:00 Mark Struberg <st...@yahoo.de>:
>>>>> To make it more clear: the only clean solution we have is to create your own WAR for your project which contains the batch jobs either directly in WEB-INF/classes or in jars in WEB-INF/lib + packaging the BatchEE servlet-gui jar into it.
>>>>> This is also the easiest to re-deploy.
>>>>>
>>>>> And this is also the easiest to secure - or do you like to have your batches open to the public?
>>>>>
>>>>>
>>>>> LIeGrue,
>>>>> strub
>>>>>
>>>>> On , Mark Struberg <st...@yahoo.de> wrote:
>>>>>
>>>>> we really need a different setup for WARs being useful. Currently they are just broken as it does _not_ allow you to control jobs which are deployed in other ClassLoaders.
>>>>>>We first need a clean solution to that problem and THEN we can think about a standalone WAR to control batches.
>>>>>>
>>>>>>LieGrue,
>>>>>>strub
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>On Sunday, 30 March 2014, 19:19, Romain Manni-Bucau <rm...@gmail.com> wrote:
>>>>>>
>>>>>>well i'm -1 for it even for 0.1 and if war doesn't allow to control
>>>>>>>batches since that's the first need. Embedding it would be a pain for
>>>>>>>50% of the projects. Doesn't cost anything to deploy both and will
>>>>>>>prevent issue later when we'll do it (no change or coordinates).
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>Romain Manni-Bucau
>>>>>>>Twitter: @rmannibucau
>>>>>>>Blog: http://rmannibucau.wordpress.com/
>>>>>>>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>>>>>Github: https://github.com/rmannibucau
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>---------- Forwarded message ----------
>>>>>>>From:  <st...@apache.org>
>>>>>>>Date: 2014-03-30 12:35 GMT+02:00
>>>>>>>Subject: [2/6] git commit: BATCHEE-16 move back to JAR
>>>>>>>To: commits@batchee.incubator.apache.org
>>>>>>>
>>>>>>>
>>>>>>>BATCHEE-16 move back to JAR
>>>>>>>
>>>>>>>
>>>>>>>Project: http://git-wip-us.apache.org/repos/asf/incubator-batchee/repo
>>>>>>>Commit: http://git-wip-us.apache.org/repos/asf/incubator-batchee/commit/6f6a7466
>>>>>>>Tree: http://git-wip-us.apache.org/repos/asf/incubator-batchee/tree/6f6a7466
>>>>>>>Diff: http://git-wip-us.apache.org/repos/asf/incubator-batchee/diff/6f6a7466
>>>>>>>
>>>>>>>Branch: refs/heads/master
>>>>>>>Commit: 6f6a7466a6560fa9893a99becd21db7a1dc5e0af
>>>>>>>Parents: 02a6a85
>>>>>>>Author: Mark Struberg <st...@apache.org>
>>>>>>>Authored: Wed Mar 26 21:20:12 2014 +0100
>>>>>>>Committer: Mark Struberg <st...@apache.org>
>>>>>>>Committed: Sun Mar 30 10:17:24 2014 +0200
>>>>>>>
>>>>>>>----------------------------------------------------------------------
>>>>>>>gui/servlet/pom.xml | 1 -
>>>>>>>1 file changed, 1 deletion(-)
>>>>>>>----------------------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>>http://git-wip-us.apache.org/repos/asf/incubator-batchee/blob/6f6a7466/gui/servlet/pom.xml
>>>>>>>----------------------------------------------------------------------
>>>>>>>diff --git a/gui/servlet/pom.xml b/gui/servlet/pom.xml
>>>>>>>index a4e540f..3fa6bd3 100644
>>>>>>>--- a/gui/servlet/pom.xml
>>>>>>>+++ b/gui/servlet/pom.xml
>>>>>>>@@ -28,7 +28,6 @@
>>>>>>>
>>>>>>>   <artifactId>batchee-servlet</artifactId>
>>>>>>>   <name>BatchEE :: GUI :: Servlet</name>
>>>>>>>-  <packaging>war</packaging>
>>>>>>>
>>>>>>>   <dependencies>
>>>>>>>     <dependency>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>
>>

Re: Fwd: [2/6] git commit: BATCHEE-16 move back to JAR

Posted by Mark Struberg <st...@yahoo.de>.
Ok, I c. Why not make an own batchee-reporting WAR? Much easier and this is really a benefit. 
The problem I have with the solution of making the batchee-servlet a WAR is that you would first need to disable all the 'active' options to use it. It must really only be a reporting WAR.

LieGrue,
strub


On Sunday, 30 March 2014, 21:38, Romain Manni-Bucau <rm...@gmail.com> wrote:
 
I run batches with batchee cli and have the reporting thanks to the war.
>Romain Manni-Bucau
>Twitter: @rmannibucau
>Blog: http://rmannibucau.wordpress.com/
>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>Github: https://github.com/rmannibucau
>
>
>
>
>2014-03-30 21:30 GMT+02:00 Mark Struberg <st...@yahoo.de>:
>> I don't see the benefit. Your original batch jobs already need some way to start them. Are you not using the batchee-servlet or JAX-RS for it? How do you start them?
>>
>> The batchee-servlet does allow full control over the JobOperator, but without having the batches in your ClassPath, you can only utilize a small part of it (reading out the status). But this is already available via the parts you need in your JOB WARs anyway...
>>
>>
>> LieGrue,
>> strub
>>
>>
>> On Sunday, 30 March 2014, 19:43, Romain Manni-Bucau <rm...@gmail.com> wrote:
>>
>> I dont agree. YOU want to control your batches with it, I just want to
>>>read data about executions and that's really useful to drop anoter war
>>>instead of updating an existing app. That's really mandatory Mark. We
>>>can release it in alpha or printing a warning but we need it.
>>>Romain Manni-Bucau
>>>Twitter: @rmannibucau
>>>Blog: http://rmannibucau.wordpress.com/
>>>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>Github: https://github.com/rmannibucau
>>>
>>>
>>>
>>>
>>>2014-03-30 19:39 GMT+02:00 Mark Struberg <st...@yahoo.de>:
>>>> To make it more clear: the only clean solution we have is to create your own WAR for your project which contains the batch jobs either directly in WEB-INF/classes or in jars in WEB-INF/lib + packaging the BatchEE servlet-gui jar into it.
>>>> This is also the easiest to re-deploy.
>>>>
>>>> And this is also the easiest to secure - or do you like to have your batches open to the public?
>>>>
>>>>
>>>> LIeGrue,
>>>> strub
>>>>
>>>> On , Mark Struberg <st...@yahoo.de> wrote:
>>>>
>>>> we really need a different setup for WARs being useful. Currently they are just broken as it does _not_ allow you to control jobs which are deployed in other ClassLoaders.
>>>>>We first need a clean solution to that problem and THEN we can think about a standalone WAR to control batches.
>>>>>
>>>>>LieGrue,
>>>>>strub
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>On Sunday, 30 March 2014, 19:19, Romain Manni-Bucau <rm...@gmail.com> wrote:
>>>>>
>>>>>well i'm -1 for it even for 0.1 and if war doesn't allow to control
>>>>>>batches since that's the first need. Embedding it would be a pain for
>>>>>>50% of the projects. Doesn't cost anything to deploy both and will
>>>>>>prevent issue later when we'll do it (no change or coordinates).
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>Romain Manni-Bucau
>>>>>>Twitter: @rmannibucau
>>>>>>Blog: http://rmannibucau.wordpress.com/
>>>>>>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>>>>Github: https://github.com/rmannibucau
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>---------- Forwarded message ----------
>>>>>>From:  <st...@apache.org>
>>>>>>Date: 2014-03-30 12:35 GMT+02:00
>>>>>>Subject: [2/6] git commit: BATCHEE-16 move back to JAR
>>>>>>To: commits@batchee.incubator.apache.org
>>>>>>
>>>>>>
>>>>>>BATCHEE-16 move back to JAR
>>>>>>
>>>>>>
>>>>>>Project: http://git-wip-us.apache.org/repos/asf/incubator-batchee/repo
>>>>>>Commit: http://git-wip-us.apache.org/repos/asf/incubator-batchee/commit/6f6a7466
>>>>>>Tree: http://git-wip-us.apache.org/repos/asf/incubator-batchee/tree/6f6a7466
>>>>>>Diff: http://git-wip-us.apache.org/repos/asf/incubator-batchee/diff/6f6a7466
>>>>>>
>>>>>>Branch: refs/heads/master
>>>>>>Commit: 6f6a7466a6560fa9893a99becd21db7a1dc5e0af
>>>>>>Parents: 02a6a85
>>>>>>Author: Mark Struberg <st...@apache.org>
>>>>>>Authored: Wed Mar 26 21:20:12 2014 +0100
>>>>>>Committer: Mark Struberg <st...@apache.org>
>>>>>>Committed: Sun Mar 30 10:17:24 2014 +0200
>>>>>>
>>>>>>----------------------------------------------------------------------
>>>>>>gui/servlet/pom.xml | 1 -
>>>>>>1 file changed, 1 deletion(-)
>>>>>>----------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>http://git-wip-us.apache.org/repos/asf/incubator-batchee/blob/6f6a7466/gui/servlet/pom.xml
>>>>>>----------------------------------------------------------------------
>>>>>>diff --git a/gui/servlet/pom.xml b/gui/servlet/pom.xml
>>>>>>index a4e540f..3fa6bd3 100644
>>>>>>--- a/gui/servlet/pom.xml
>>>>>>+++ b/gui/servlet/pom.xml
>>>>>>@@ -28,7 +28,6 @@
>>>>>>
>>>>>>   <artifactId>batchee-servlet</artifactId>
>>>>>>   <name>BatchEE :: GUI :: Servlet</name>
>>>>>>-  <packaging>war</packaging>
>>>>>>
>>>>>>   <dependencies>
>>>>>>     <dependency>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>
>

Re: Fwd: [2/6] git commit: BATCHEE-16 move back to JAR

Posted by Romain Manni-Bucau <rm...@gmail.com>.
I run batches with batchee cli and have the reporting thanks to the war.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau



2014-03-30 21:30 GMT+02:00 Mark Struberg <st...@yahoo.de>:
> I don't see the benefit. Your original batch jobs already need some way to start them. Are you not using the batchee-servlet or JAX-RS for it? How do you start them?
>
> The batchee-servlet does allow full control over the JobOperator, but without having the batches in your ClassPath, you can only utilize a small part of it (reading out the status). But this is already available via the parts you need in your JOB WARs anyway...
>
>
> LieGrue,
> strub
>
>
> On Sunday, 30 March 2014, 19:43, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
> I dont agree. YOU want to control your batches with it, I just want to
>>read data about executions and that's really useful to drop anoter war
>>instead of updating an existing app. That's really mandatory Mark. We
>>can release it in alpha or printing a warning but we need it.
>>Romain Manni-Bucau
>>Twitter: @rmannibucau
>>Blog: http://rmannibucau.wordpress.com/
>>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>Github: https://github.com/rmannibucau
>>
>>
>>
>>
>>2014-03-30 19:39 GMT+02:00 Mark Struberg <st...@yahoo.de>:
>>> To make it more clear: the only clean solution we have is to create your own WAR for your project which contains the batch jobs either directly in WEB-INF/classes or in jars in WEB-INF/lib + packaging the BatchEE servlet-gui jar into it.
>>> This is also the easiest to re-deploy.
>>>
>>> And this is also the easiest to secure - or do you like to have your batches open to the public?
>>>
>>>
>>> LIeGrue,
>>> strub
>>>
>>> On , Mark Struberg <st...@yahoo.de> wrote:
>>>
>>> we really need a different setup for WARs being useful. Currently they are just broken as it does _not_ allow you to control jobs which are deployed in other ClassLoaders.
>>>>We first need a clean solution to that problem and THEN we can think about a standalone WAR to control batches.
>>>>
>>>>LieGrue,
>>>>strub
>>>>
>>>>
>>>>
>>>>
>>>>On Sunday, 30 March 2014, 19:19, Romain Manni-Bucau <rm...@gmail.com> wrote:
>>>>
>>>>well i'm -1 for it even for 0.1 and if war doesn't allow to control
>>>>>batches since that's the first need. Embedding it would be a pain for
>>>>>50% of the projects. Doesn't cost anything to deploy both and will
>>>>>prevent issue later when we'll do it (no change or coordinates).
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>Romain Manni-Bucau
>>>>>Twitter: @rmannibucau
>>>>>Blog: http://rmannibucau.wordpress.com/
>>>>>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>>>Github: https://github.com/rmannibucau
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>---------- Forwarded message ----------
>>>>>From:  <st...@apache.org>
>>>>>Date: 2014-03-30 12:35 GMT+02:00
>>>>>Subject: [2/6] git commit: BATCHEE-16 move back to JAR
>>>>>To: commits@batchee.incubator.apache.org
>>>>>
>>>>>
>>>>>BATCHEE-16 move back to JAR
>>>>>
>>>>>
>>>>>Project: http://git-wip-us.apache.org/repos/asf/incubator-batchee/repo
>>>>>Commit: http://git-wip-us.apache.org/repos/asf/incubator-batchee/commit/6f6a7466
>>>>>Tree: http://git-wip-us.apache.org/repos/asf/incubator-batchee/tree/6f6a7466
>>>>>Diff: http://git-wip-us.apache.org/repos/asf/incubator-batchee/diff/6f6a7466
>>>>>
>>>>>Branch: refs/heads/master
>>>>>Commit: 6f6a7466a6560fa9893a99becd21db7a1dc5e0af
>>>>>Parents: 02a6a85
>>>>>Author: Mark Struberg <st...@apache.org>
>>>>>Authored: Wed Mar 26 21:20:12 2014 +0100
>>>>>Committer: Mark Struberg <st...@apache.org>
>>>>>Committed: Sun Mar 30 10:17:24 2014 +0200
>>>>>
>>>>>----------------------------------------------------------------------
>>>>>gui/servlet/pom.xml | 1 -
>>>>>1 file changed, 1 deletion(-)
>>>>>----------------------------------------------------------------------
>>>>>
>>>>>
>>>>>http://git-wip-us.apache.org/repos/asf/incubator-batchee/blob/6f6a7466/gui/servlet/pom.xml
>>>>>----------------------------------------------------------------------
>>>>>diff --git a/gui/servlet/pom.xml b/gui/servlet/pom.xml
>>>>>index a4e540f..3fa6bd3 100644
>>>>>--- a/gui/servlet/pom.xml
>>>>>+++ b/gui/servlet/pom.xml
>>>>>@@ -28,7 +28,6 @@
>>>>>
>>>>>   <artifactId>batchee-servlet</artifactId>
>>>>>   <name>BatchEE :: GUI :: Servlet</name>
>>>>>-  <packaging>war</packaging>
>>>>>
>>>>>   <dependencies>
>>>>>     <dependency>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>
>>
>>

Re: Fwd: [2/6] git commit: BATCHEE-16 move back to JAR

Posted by Mark Struberg <st...@yahoo.de>.
I don't see the benefit. Your original batch jobs already need some way to start them. Are you not using the batchee-servlet or JAX-RS for it? How do you start them?

The batchee-servlet does allow full control over the JobOperator, but without having the batches in your ClassPath, you can only utilize a small part of it (reading out the status). But this is already available via the parts you need in your JOB WARs anyway...


LieGrue,
strub


On Sunday, 30 March 2014, 19:43, Romain Manni-Bucau <rm...@gmail.com> wrote:
 
I dont agree. YOU want to control your batches with it, I just want to
>read data about executions and that's really useful to drop anoter war
>instead of updating an existing app. That's really mandatory Mark. We
>can release it in alpha or printing a warning but we need it.
>Romain Manni-Bucau
>Twitter: @rmannibucau
>Blog: http://rmannibucau.wordpress.com/
>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>Github: https://github.com/rmannibucau
>
>
>
>
>2014-03-30 19:39 GMT+02:00 Mark Struberg <st...@yahoo.de>:
>> To make it more clear: the only clean solution we have is to create your own WAR for your project which contains the batch jobs either directly in WEB-INF/classes or in jars in WEB-INF/lib + packaging the BatchEE servlet-gui jar into it.
>> This is also the easiest to re-deploy.
>>
>> And this is also the easiest to secure - or do you like to have your batches open to the public?
>>
>>
>> LIeGrue,
>> strub
>>
>> On , Mark Struberg <st...@yahoo.de> wrote:
>>
>> we really need a different setup for WARs being useful. Currently they are just broken as it does _not_ allow you to control jobs which are deployed in other ClassLoaders.
>>>We first need a clean solution to that problem and THEN we can think about a standalone WAR to control batches.
>>>
>>>LieGrue,
>>>strub
>>>
>>>
>>>
>>>
>>>On Sunday, 30 March 2014, 19:19, Romain Manni-Bucau <rm...@gmail.com> wrote:
>>>
>>>well i'm -1 for it even for 0.1 and if war doesn't allow to control
>>>>batches since that's the first need. Embedding it would be a pain for
>>>>50% of the projects. Doesn't cost anything to deploy both and will
>>>>prevent issue later when we'll do it (no change or coordinates).
>>>>
>>>>
>>>>
>>>>
>>>>Romain Manni-Bucau
>>>>Twitter: @rmannibucau
>>>>Blog: http://rmannibucau.wordpress.com/
>>>>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>>Github: https://github.com/rmannibucau
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>---------- Forwarded message ----------
>>>>From:  <st...@apache.org>
>>>>Date: 2014-03-30 12:35 GMT+02:00
>>>>Subject: [2/6] git commit: BATCHEE-16 move back to JAR
>>>>To: commits@batchee.incubator.apache.org
>>>>
>>>>
>>>>BATCHEE-16 move back to JAR
>>>>
>>>>
>>>>Project: http://git-wip-us.apache.org/repos/asf/incubator-batchee/repo
>>>>Commit: http://git-wip-us.apache.org/repos/asf/incubator-batchee/commit/6f6a7466
>>>>Tree: http://git-wip-us.apache.org/repos/asf/incubator-batchee/tree/6f6a7466
>>>>Diff: http://git-wip-us.apache.org/repos/asf/incubator-batchee/diff/6f6a7466
>>>>
>>>>Branch: refs/heads/master
>>>>Commit: 6f6a7466a6560fa9893a99becd21db7a1dc5e0af
>>>>Parents: 02a6a85
>>>>Author: Mark Struberg <st...@apache.org>
>>>>Authored: Wed Mar 26 21:20:12 2014 +0100
>>>>Committer: Mark Struberg <st...@apache.org>
>>>>Committed: Sun Mar 30 10:17:24 2014 +0200
>>>>
>>>>----------------------------------------------------------------------
>>>>gui/servlet/pom.xml | 1 -
>>>>1 file changed, 1 deletion(-)
>>>>----------------------------------------------------------------------
>>>>
>>>>
>>>>http://git-wip-us.apache.org/repos/asf/incubator-batchee/blob/6f6a7466/gui/servlet/pom.xml
>>>>----------------------------------------------------------------------
>>>>diff --git a/gui/servlet/pom.xml b/gui/servlet/pom.xml
>>>>index a4e540f..3fa6bd3 100644
>>>>--- a/gui/servlet/pom.xml
>>>>+++ b/gui/servlet/pom.xml
>>>>@@ -28,7 +28,6 @@
>>>>
>>>>   <artifactId>batchee-servlet</artifactId>
>>>>   <name>BatchEE :: GUI :: Servlet</name>
>>>>-  <packaging>war</packaging>
>>>>
>>>>   <dependencies>
>>>>     <dependency>
>>>>
>>>>
>>>>
>>>
>>>
>
>
>

Re: Fwd: [2/6] git commit: BATCHEE-16 move back to JAR

Posted by Romain Manni-Bucau <rm...@gmail.com>.
I dont agree. YOU want to control your batches with it, I just want to
read data about executions and that's really useful to drop anoter war
instead of updating an existing app. That's really mandatory Mark. We
can release it in alpha or printing a warning but we need it.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau



2014-03-30 19:39 GMT+02:00 Mark Struberg <st...@yahoo.de>:
> To make it more clear: the only clean solution we have is to create your own WAR for your project which contains the batch jobs either directly in WEB-INF/classes or in jars in WEB-INF/lib + packaging the BatchEE servlet-gui jar into it.
> This is also the easiest to re-deploy.
>
> And this is also the easiest to secure - or do you like to have your batches open to the public?
>
>
> LIeGrue,
> strub
>
> On , Mark Struberg <st...@yahoo.de> wrote:
>
> we really need a different setup for WARs being useful. Currently they are just broken as it does _not_ allow you to control jobs which are deployed in other ClassLoaders.
>>We first need a clean solution to that problem and THEN we can think about a standalone WAR to control batches.
>>
>>LieGrue,
>>strub
>>
>>
>>
>>
>>On Sunday, 30 March 2014, 19:19, Romain Manni-Bucau <rm...@gmail.com> wrote:
>>
>>well i'm -1 for it even for 0.1 and if war doesn't allow to control
>>>batches since that's the first need. Embedding it would be a pain for
>>>50% of the projects. Doesn't cost anything to deploy both and will
>>>prevent issue later when we'll do it (no change or coordinates).
>>>
>>>
>>>
>>>
>>>Romain Manni-Bucau
>>>Twitter: @rmannibucau
>>>Blog: http://rmannibucau.wordpress.com/
>>>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>>Github: https://github.com/rmannibucau
>>>
>>>
>>>
>>>
>>>
>>>---------- Forwarded message ----------
>>>From:  <st...@apache.org>
>>>Date: 2014-03-30 12:35 GMT+02:00
>>>Subject: [2/6] git commit: BATCHEE-16 move back to JAR
>>>To: commits@batchee.incubator.apache.org
>>>
>>>
>>>BATCHEE-16 move back to JAR
>>>
>>>
>>>Project: http://git-wip-us.apache.org/repos/asf/incubator-batchee/repo
>>>Commit: http://git-wip-us.apache.org/repos/asf/incubator-batchee/commit/6f6a7466
>>>Tree: http://git-wip-us.apache.org/repos/asf/incubator-batchee/tree/6f6a7466
>>>Diff: http://git-wip-us.apache.org/repos/asf/incubator-batchee/diff/6f6a7466
>>>
>>>Branch: refs/heads/master
>>>Commit: 6f6a7466a6560fa9893a99becd21db7a1dc5e0af
>>>Parents: 02a6a85
>>>Author: Mark Struberg <st...@apache.org>
>>>Authored: Wed Mar 26 21:20:12 2014 +0100
>>>Committer: Mark Struberg <st...@apache.org>
>>>Committed: Sun Mar 30 10:17:24 2014 +0200
>>>
>>>----------------------------------------------------------------------
>>>gui/servlet/pom.xml | 1 -
>>>1 file changed, 1 deletion(-)
>>>----------------------------------------------------------------------
>>>
>>>
>>>http://git-wip-us.apache.org/repos/asf/incubator-batchee/blob/6f6a7466/gui/servlet/pom.xml
>>>----------------------------------------------------------------------
>>>diff --git a/gui/servlet/pom.xml b/gui/servlet/pom.xml
>>>index a4e540f..3fa6bd3 100644
>>>--- a/gui/servlet/pom.xml
>>>+++ b/gui/servlet/pom.xml
>>>@@ -28,7 +28,6 @@
>>>
>>>   <artifactId>batchee-servlet</artifactId>
>>>   <name>BatchEE :: GUI :: Servlet</name>
>>>-  <packaging>war</packaging>
>>>
>>>   <dependencies>
>>>     <dependency>
>>>
>>>
>>>
>>
>>

Re: Fwd: [2/6] git commit: BATCHEE-16 move back to JAR

Posted by Mark Struberg <st...@yahoo.de>.
To make it more clear: the only clean solution we have is to create your own WAR for your project which contains the batch jobs either directly in WEB-INF/classes or in jars in WEB-INF/lib + packaging the BatchEE servlet-gui jar into it. 
This is also the easiest to re-deploy. 

And this is also the easiest to secure - or do you like to have your batches open to the public? 


LIeGrue,
strub

On , Mark Struberg <st...@yahoo.de> wrote:
 
we really need a different setup for WARs being useful. Currently they are just broken as it does _not_ allow you to control jobs which are deployed in other ClassLoaders.
>We first need a clean solution to that problem and THEN we can think about a standalone WAR to control batches.
>
>LieGrue,
>strub
>
>
>
>
>On Sunday, 30 March 2014, 19:19, Romain Manni-Bucau <rm...@gmail.com> wrote:
> 
>well i'm -1 for it even for 0.1 and if war doesn't allow to control
>>batches since that's the first need. Embedding it would be a pain for
>>50% of the projects. Doesn't cost anything to deploy both and will
>>prevent issue later when we'll do it (no change or coordinates).
>>
>>
>>
>>
>>Romain Manni-Bucau
>>Twitter: @rmannibucau
>>Blog: http://rmannibucau.wordpress.com/
>>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>Github: https://github.com/rmannibucau
>>
>>
>>
>>
>>
>>---------- Forwarded message ----------
>>From:  <st...@apache.org>
>>Date: 2014-03-30 12:35 GMT+02:00
>>Subject: [2/6] git commit: BATCHEE-16 move back to JAR
>>To: commits@batchee.incubator.apache.org
>>
>>
>>BATCHEE-16 move back to JAR
>>
>>
>>Project: http://git-wip-us.apache.org/repos/asf/incubator-batchee/repo
>>Commit: http://git-wip-us.apache.org/repos/asf/incubator-batchee/commit/6f6a7466
>>Tree: http://git-wip-us.apache.org/repos/asf/incubator-batchee/tree/6f6a7466
>>Diff: http://git-wip-us.apache.org/repos/asf/incubator-batchee/diff/6f6a7466
>>
>>Branch: refs/heads/master
>>Commit: 6f6a7466a6560fa9893a99becd21db7a1dc5e0af
>>Parents: 02a6a85
>>Author: Mark Struberg <st...@apache.org>
>>Authored: Wed Mar 26 21:20:12 2014 +0100
>>Committer: Mark Struberg <st...@apache.org>
>>Committed: Sun Mar 30 10:17:24 2014 +0200
>>
>>----------------------------------------------------------------------
>>gui/servlet/pom.xml | 1 -
>>1 file changed, 1 deletion(-)
>>----------------------------------------------------------------------
>>
>>
>>http://git-wip-us.apache.org/repos/asf/incubator-batchee/blob/6f6a7466/gui/servlet/pom.xml
>>----------------------------------------------------------------------
>>diff --git a/gui/servlet/pom.xml b/gui/servlet/pom.xml
>>index a4e540f..3fa6bd3 100644
>>--- a/gui/servlet/pom.xml
>>+++ b/gui/servlet/pom.xml
>>@@ -28,7 +28,6 @@
>>
>>   <artifactId>batchee-servlet</artifactId>
>>   <name>BatchEE :: GUI :: Servlet</name>
>>-  <packaging>war</packaging>
>>
>>   <dependencies>
>>     <dependency>
>>
>>
>>
>
>

Re: Fwd: [2/6] git commit: BATCHEE-16 move back to JAR

Posted by Mark Struberg <st...@yahoo.de>.
we really need a different setup for WARs being useful. Currently they are just broken as it does _not_ allow you to control jobs which are deployed in other ClassLoaders.
We first need a clean solution to that problem and THEN we can think about a standalone WAR to control batches.

LieGrue,
strub



On Sunday, 30 March 2014, 19:19, Romain Manni-Bucau <rm...@gmail.com> wrote:
 
well i'm -1 for it even for 0.1 and if war doesn't allow to control
>batches since that's the first need. Embedding it would be a pain for
>50% of the projects. Doesn't cost anything to deploy both and will
>prevent issue later when we'll do it (no change or coordinates).
>
>
>
>
>Romain Manni-Bucau
>Twitter: @rmannibucau
>Blog: http://rmannibucau.wordpress.com/
>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>Github: https://github.com/rmannibucau
>
>
>
>
>
>---------- Forwarded message ----------
>From:  <st...@apache.org>
>Date: 2014-03-30 12:35 GMT+02:00
>Subject: [2/6] git commit: BATCHEE-16 move back to JAR
>To: commits@batchee.incubator.apache.org
>
>
>BATCHEE-16 move back to JAR
>
>
>Project: http://git-wip-us.apache.org/repos/asf/incubator-batchee/repo
>Commit: http://git-wip-us.apache.org/repos/asf/incubator-batchee/commit/6f6a7466
>Tree: http://git-wip-us.apache.org/repos/asf/incubator-batchee/tree/6f6a7466
>Diff: http://git-wip-us.apache.org/repos/asf/incubator-batchee/diff/6f6a7466
>
>Branch: refs/heads/master
>Commit: 6f6a7466a6560fa9893a99becd21db7a1dc5e0af
>Parents: 02a6a85
>Author: Mark Struberg <st...@apache.org>
>Authored: Wed Mar 26 21:20:12 2014 +0100
>Committer: Mark Struberg <st...@apache.org>
>Committed: Sun Mar 30 10:17:24 2014 +0200
>
>----------------------------------------------------------------------
>gui/servlet/pom.xml | 1 -
>1 file changed, 1 deletion(-)
>----------------------------------------------------------------------
>
>
>http://git-wip-us.apache.org/repos/asf/incubator-batchee/blob/6f6a7466/gui/servlet/pom.xml
>----------------------------------------------------------------------
>diff --git a/gui/servlet/pom.xml b/gui/servlet/pom.xml
>index a4e540f..3fa6bd3 100644
>--- a/gui/servlet/pom.xml
>+++ b/gui/servlet/pom.xml
>@@ -28,7 +28,6 @@
>
>   <artifactId>batchee-servlet</artifactId>
>   <name>BatchEE :: GUI :: Servlet</name>
>-  <packaging>war</packaging>
>
>   <dependencies>
>     <dependency>
>
>
>

Fwd: [2/6] git commit: BATCHEE-16 move back to JAR

Posted by Romain Manni-Bucau <rm...@gmail.com>.
well i'm -1 for it even for 0.1 and if war doesn't allow to control
batches since that's the first need. Embedding it would be a pain for
50% of the projects. Doesn't cost anything to deploy both and will
prevent issue later when we'll do it (no change or coordinates).




Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau




---------- Forwarded message ----------
From:  <st...@apache.org>
Date: 2014-03-30 12:35 GMT+02:00
Subject: [2/6] git commit: BATCHEE-16 move back to JAR
To: commits@batchee.incubator.apache.org


BATCHEE-16 move back to JAR


Project: http://git-wip-us.apache.org/repos/asf/incubator-batchee/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-batchee/commit/6f6a7466
Tree: http://git-wip-us.apache.org/repos/asf/incubator-batchee/tree/6f6a7466
Diff: http://git-wip-us.apache.org/repos/asf/incubator-batchee/diff/6f6a7466

Branch: refs/heads/master
Commit: 6f6a7466a6560fa9893a99becd21db7a1dc5e0af
Parents: 02a6a85
Author: Mark Struberg <st...@apache.org>
Authored: Wed Mar 26 21:20:12 2014 +0100
Committer: Mark Struberg <st...@apache.org>
Committed: Sun Mar 30 10:17:24 2014 +0200

----------------------------------------------------------------------
 gui/servlet/pom.xml | 1 -
 1 file changed, 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-batchee/blob/6f6a7466/gui/servlet/pom.xml
----------------------------------------------------------------------
diff --git a/gui/servlet/pom.xml b/gui/servlet/pom.xml
index a4e540f..3fa6bd3 100644
--- a/gui/servlet/pom.xml
+++ b/gui/servlet/pom.xml
@@ -28,7 +28,6 @@

   <artifactId>batchee-servlet</artifactId>
   <name>BatchEE :: GUI :: Servlet</name>
-  <packaging>war</packaging>

   <dependencies>
     <dependency>