[JBoss JIRA] Created: (JBESB-500) package rules, jbpm and smooks as services

[JBoss JIRA] Created: (JBESB-592)...

[JBoss JIRA] Created: (JBESB-584)...

Kurt Stam (JIRA)

Monday, 9 April 2007 Mon, 9 Apr '07

1:39 p.m.

package rules, jbpm and smooks as services ------------------------------------------ Key: JBESB-500 URL: http://jira.jboss.com/jira/browse/JBESB-500 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.0 Beta 1 Maintenance Pack 1 Reporter: Kurt Stam Assigned To: Kurt Stam Fix For: 4.2 Milestone Release 2 If we package up all our services as individual .esb archives, we will make it much easier to deploy things like rules, smooks and jBPM. If we go down this road the can become individual self-contained deployments. And so it becomes much easier to maintain them for us as well as to deploy and use them for our users, basically another step towards JBI like architecture. So we should restructure our SVN such that i.e. 'rules' has it's own place. I think we should have three more directories: services/jbpm -> jbpm.esb services/smooks -> smooks.esb services/cbr/jbr -> cbr-jbr.esb each of them builds an .esb archive, and each project has it's own lib directory, so we can clean up the current lib/ext directory which contains everything and the kitchen sink. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Show replies by date

Kurt Stam (JIRA)

Monday, 9 April Mon, 9 Apr

1:41 p.m.

New subject: [JBoss JIRA] Updated: (JBESB-500) package rules, jbpm and smooks as services

[ http://jira.jboss.com/jira/browse/JBESB-500?page=all ] Kurt Stam updated JBESB-500: ---------------------------- Affects Version/s: 4.2 Milestone Release 1 (was: 4.0 Beta 1 Maintenance Pack 1)

...

package rules, jbpm and smooks as services ------------------------------------------ Key: JBESB-500 URL: http://jira.jboss.com/jira/browse/JBESB-500 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Affects Versions: 4.2 Milestone Release 1 Reporter: Kurt Stam Assigned To: Kurt Stam Fix For: 4.2 Milestone Release 2 If we package up all our services as individual .esb archives, we will make it much easier to deploy things like rules, smooks and jBPM. If we go down this road the can become individual self-contained deployments. And so it becomes much easier to maintain them for us as well as to deploy and use them for our users, basically another step towards JBI like architecture. So we should restructure our SVN such that i.e. 'rules' has it's own place. I think we should have three more directories: services/jbpm -> jbpm.esb services/smooks -> smooks.esb services/cbr/jbr -> cbr-jbr.esb each of them builds an .esb archive, and each project has it's own lib directory, so we can clean up the current lib/ext directory which contains everything and the kitchen sink.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Mark Little (JIRA)

Friday, 13 April Fri, 13 Apr

10:46 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-500) package rules, jbpm and smooks as services

[ http://jira.jboss.com/jira/browse/JBESB-500?page=comments#action_12359261 ] Mark Little commented on JBESB-500: ----------------------------------- As part of this, can we remove the services directory from core?

...

package rules, jbpm and smooks as services ------------------------------------------ Key: JBESB-500 URL: http://jira.jboss.com/jira/browse/JBESB-500 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Affects Versions: 4.2 Milestone Release 1 Reporter: Kurt Stam Assigned To: Kurt Stam Fix For: 4.2 Milestone Release 2 If we package up all our services as individual .esb archives, we will make it much easier to deploy things like rules, smooks and jBPM. If we go down this road the can become individual self-contained deployments. And so it becomes much easier to maintain them for us as well as to deploy and use them for our users, basically another step towards JBI like architecture. So we should restructure our SVN such that i.e. 'rules' has it's own place. I think we should have three more directories: services/jbpm -> jbpm.esb services/smooks -> smooks.esb services/cbr/jbr -> cbr-jbr.esb each of them builds an .esb archive, and each project has it's own lib directory, so we can clean up the current lib/ext directory which contains everything and the kitchen sink.

Mark Little (JIRA)

Wednesday, 18 April Wed, 18 Apr

6:27 a.m.

New subject: [JBoss JIRA] Commented: (JBESB-500) package rules, jbpm and smooks as services

[ http://jira.jboss.com/jira/browse/JBESB-500?page=comments#action_12359697 ] Mark Little commented on JBESB-500: ----------------------------------- See Kev's comment on http://jira.jboss.com/jira/browse/JBESB-438 about service dependencies.

...

package rules, jbpm and smooks as services ------------------------------------------ Key: JBESB-500 URL: http://jira.jboss.com/jira/browse/JBESB-500 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Affects Versions: 4.2 Milestone Release 1 Reporter: Kurt Stam Assigned To: Kurt Stam Fix For: 4.2 Milestone Release 2 If we package up all our services as individual .esb archives, we will make it much easier to deploy things like rules, smooks and jBPM. If we go down this road the can become individual self-contained deployments. And so it becomes much easier to maintain them for us as well as to deploy and use them for our users, basically another step towards JBI like architecture. So we should restructure our SVN such that i.e. 'rules' has it's own place. I think we should have three more directories: services/jbpm -> jbpm.esb services/smooks -> smooks.esb services/cbr/jbr -> cbr-jbr.esb each of them builds an .esb archive, and each project has it's own lib directory, so we can clean up the current lib/ext directory which contains everything and the kitchen sink.

Kurt Stam (JIRA)

Wednesday, 2 May Wed, 2 May

10:53 a.m.

New subject: [JBoss JIRA] Updated: (JBESB-500) package rules, jbpm and smooks as services

[ http://jira.jboss.com/jira/browse/JBESB-500?page=all ] Kurt Stam updated JBESB-500: ---------------------------- Fix Version/s: 4.2 (was: 4.2 Milestone Release 2)

...

package rules, jbpm and smooks as services ------------------------------------------ Key: JBESB-500 URL: http://jira.jboss.com/jira/browse/JBESB-500 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Affects Versions: 4.2 Milestone Release 1 Reporter: Kurt Stam Assigned To: Kurt Stam Fix For: 4.2 If we package up all our services as individual .esb archives, we will make it much easier to deploy things like rules, smooks and jBPM. If we go down this road the can become individual self-contained deployments. And so it becomes much easier to maintain them for us as well as to deploy and use them for our users, basically another step towards JBI like architecture. So we should restructure our SVN such that i.e. 'rules' has it's own place. I think we should have three more directories: services/jbpm -> jbpm.esb services/smooks -> smooks.esb services/cbr/jbr -> cbr-jbr.esb each of them builds an .esb archive, and each project has it's own lib directory, so we can clean up the current lib/ext directory which contains everything and the kitchen sink.

Mark Little (JIRA)

Friday, 11 May Fri, 11 May

10:39 p.m.

New subject: [JBoss JIRA] Updated: (JBESB-500) package rules, jbpm and smooks as services

[ http://jira.jboss.com/jira/browse/JBESB-500?page=all ] Mark Little updated JBESB-500: ------------------------------ Component/s: Packaging

...

package rules, jbpm and smooks as services ------------------------------------------ Key: JBESB-500 URL: http://jira.jboss.com/jira/browse/JBESB-500 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Packaging Affects Versions: 4.2 Milestone Release 1 Reporter: Kurt Stam Assigned To: Kurt Stam Fix For: 4.2 If we package up all our services as individual .esb archives, we will make it much easier to deploy things like rules, smooks and jBPM. If we go down this road the can become individual self-contained deployments. And so it becomes much easier to maintain them for us as well as to deploy and use them for our users, basically another step towards JBI like architecture. So we should restructure our SVN such that i.e. 'rules' has it's own place. I think we should have three more directories: services/jbpm -> jbpm.esb services/smooks -> smooks.esb services/cbr/jbr -> cbr-jbr.esb each of them builds an .esb archive, and each project has it's own lib directory, so we can clean up the current lib/ext directory which contains everything and the kitchen sink.

Kurt Stam (JIRA)

Thursday, 17 May Thu, 17 May

8:34 a.m.

New subject: [JBoss JIRA] Work started: (JBESB-500) package rules, jbpm and smooks as services

[ http://jira.jboss.com/jira/browse/JBESB-500?page=all ] Work on JBESB-500 started by Kurt Stam.

...

package rules, jbpm and smooks as services ------------------------------------------ Key: JBESB-500 URL: http://jira.jboss.com/jira/browse/JBESB-500 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Packaging Affects Versions: 4.2 Milestone Release 1 Reporter: Kurt Stam Assigned To: Kurt Stam Fix For: 4.2 If we package up all our services as individual .esb archives, we will make it much easier to deploy things like rules, smooks and jBPM. If we go down this road the can become individual self-contained deployments. And so it becomes much easier to maintain them for us as well as to deploy and use them for our users, basically another step towards JBI like architecture. So we should restructure our SVN such that i.e. 'rules' has it's own place. I think we should have three more directories: services/jbpm -> jbpm.esb services/smooks -> smooks.esb services/cbr/jbr -> cbr-jbr.esb each of them builds an .esb archive, and each project has it's own lib directory, so we can clean up the current lib/ext directory which contains everything and the kitchen sink.

Kurt Stam (JIRA)

Tuesday, 5 June Tue, 5 Jun

1:06 p.m.

New subject: [JBoss JIRA] Closed: (JBESB-500) package rules, jbpm and smooks as services

[ http://jira.jboss.com/jira/browse/JBESB-500?page=all ] Kurt Stam closed JBESB-500. --------------------------- Resolution: Done Also moved the message-store out into jbossesb.esb

...

package rules, jbpm and smooks as services ------------------------------------------ Key: JBESB-500 URL: http://jira.jboss.com/jira/browse/JBESB-500 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Packaging Affects Versions: 4.2 Milestone Release 1 Reporter: Kurt Stam Assigned To: Kurt Stam Fix For: 4.2 If we package up all our services as individual .esb archives, we will make it much easier to deploy things like rules, smooks and jBPM. If we go down this road the can become individual self-contained deployments. And so it becomes much easier to maintain them for us as well as to deploy and use them for our users, basically another step towards JBI like architecture. So we should restructure our SVN such that i.e. 'rules' has it's own place. I think we should have three more directories: services/jbpm -> jbpm.esb services/smooks -> smooks.esb services/cbr/jbr -> cbr-jbr.esb each of them builds an .esb archive, and each project has it's own lib directory, so we can clean up the current lib/ext directory which contains everything and the kitchen sink.

Kurt Stam (JIRA)

Thursday, 7 June Thu, 7 Jun

2:40 p.m.

New subject: [JBoss JIRA] Reopened: (JBESB-500) package rules, jbpm and smooks as services

[ http://jira.jboss.com/jira/browse/JBESB-500?page=all ] Kurt Stam reopened JBESB-500: ----------------------------- need to add spring into it's own spring.esb too.

...

package rules, jbpm and smooks as services ------------------------------------------ Key: JBESB-500 URL: http://jira.jboss.com/jira/browse/JBESB-500 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Packaging Affects Versions: 4.2 Milestone Release 1 Reporter: Kurt Stam Assigned To: Kurt Stam Fix For: 4.2 If we package up all our services as individual .esb archives, we will make it much easier to deploy things like rules, smooks and jBPM. If we go down this road the can become individual self-contained deployments. And so it becomes much easier to maintain them for us as well as to deploy and use them for our users, basically another step towards JBI like architecture. So we should restructure our SVN such that i.e. 'rules' has it's own place. I think we should have three more directories: services/jbpm -> jbpm.esb services/smooks -> smooks.esb services/cbr/jbr -> cbr-jbr.esb each of them builds an .esb archive, and each project has it's own lib directory, so we can clean up the current lib/ext directory which contains everything and the kitchen sink.

Kurt Stam (JIRA)

2:48 p.m.

New subject: [JBoss JIRA] Closed: (JBESB-500) package rules, jbpm and smooks as services

[ http://jira.jboss.com/jira/browse/JBESB-500?page=all ] Kurt Stam closed JBESB-500. --------------------------- Resolution: Done done

...

package rules, jbpm and smooks as services ------------------------------------------ Key: JBESB-500 URL: http://jira.jboss.com/jira/browse/JBESB-500 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Packaging Affects Versions: 4.2 Milestone Release 1 Reporter: Kurt Stam Assigned To: Kurt Stam Fix For: 4.2 If we package up all our services as individual .esb archives, we will make it much easier to deploy things like rules, smooks and jBPM. If we go down this road the can become individual self-contained deployments. And so it becomes much easier to maintain them for us as well as to deploy and use them for our users, basically another step towards JBI like architecture. So we should restructure our SVN such that i.e. 'rules' has it's own place. I think we should have three more directories: services/jbpm -> jbpm.esb services/smooks -> smooks.esb services/cbr/jbr -> cbr-jbr.esb each of them builds an .esb archive, and each project has it's own lib directory, so we can clean up the current lib/ext directory which contains everything and the kitchen sink.

Mark Little (JIRA)

Tuesday, 3 July Tue, 3 Jul

5:54 a.m.

New subject: [JBoss JIRA] Reopened: (JBESB-500) package rules, jbpm and smooks as services

[ http://jira.jboss.com/jira/browse/JBESB-500?page=all ] Mark Little reopened JBESB-500: -------------------------------

...

package rules, jbpm and smooks as services ------------------------------------------ Key: JBESB-500 URL: http://jira.jboss.com/jira/browse/JBESB-500 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Packaging Affects Versions: 4.2 Milestone Release 1 Reporter: Kurt Stam Assigned To: Kurt Stam Fix For: 4.2 Milestone Release 3 If we package up all our services as individual .esb archives, we will make it much easier to deploy things like rules, smooks and jBPM. If we go down this road the can become individual self-contained deployments. And so it becomes much easier to maintain them for us as well as to deploy and use them for our users, basically another step towards JBI like architecture. So we should restructure our SVN such that i.e. 'rules' has it's own place. I think we should have three more directories: services/jbpm -> jbpm.esb services/smooks -> smooks.esb services/cbr/jbr -> cbr-jbr.esb each of them builds an .esb archive, and each project has it's own lib directory, so we can clean up the current lib/ext directory which contains everything and the kitchen sink.

Mark Little (JIRA)

5:55 a.m.

New subject: [JBoss JIRA] Updated: (JBESB-500) package rules, jbpm and smooks as services

[ http://jira.jboss.com/jira/browse/JBESB-500?page=all ] Mark Little updated JBESB-500: ------------------------------ Fix Version/s: 4.2 Milestone Release 3 (was: 4.2)

...

package rules, jbpm and smooks as services ------------------------------------------ Key: JBESB-500 URL: http://jira.jboss.com/jira/browse/JBESB-500 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Packaging Affects Versions: 4.2 Milestone Release 1 Reporter: Kurt Stam Assigned To: Kurt Stam Fix For: 4.2 Milestone Release 3 If we package up all our services as individual .esb archives, we will make it much easier to deploy things like rules, smooks and jBPM. If we go down this road the can become individual self-contained deployments. And so it becomes much easier to maintain them for us as well as to deploy and use them for our users, basically another step towards JBI like architecture. So we should restructure our SVN such that i.e. 'rules' has it's own place. I think we should have three more directories: services/jbpm -> jbpm.esb services/smooks -> smooks.esb services/cbr/jbr -> cbr-jbr.esb each of them builds an .esb archive, and each project has it's own lib directory, so we can clean up the current lib/ext directory which contains everything and the kitchen sink.

Mark Little (JIRA)

5:56 a.m.

New subject: [JBoss JIRA] Closed: (JBESB-500) package rules, jbpm and smooks as services

[ http://jira.jboss.com/jira/browse/JBESB-500?page=all ] Mark Little closed JBESB-500. ----------------------------- Resolution: Done

...

package rules, jbpm and smooks as services ------------------------------------------ Key: JBESB-500 URL: http://jira.jboss.com/jira/browse/JBESB-500 Project: JBoss ESB Issue Type: Task Security Level: Public(Everyone can see) Components: Packaging Affects Versions: 4.2 Milestone Release 1 Reporter: Kurt Stam Assigned To: Kurt Stam Fix For: 4.2 Milestone Release 3 If we package up all our services as individual .esb archives, we will make it much easier to deploy things like rules, smooks and jBPM. If we go down this road the can become individual self-contained deployments. And so it becomes much easier to maintain them for us as well as to deploy and use them for our users, basically another step towards JBI like architecture. So we should restructure our SVN such that i.e. 'rules' has it's own place. I think we should have three more directories: services/jbpm -> jbpm.esb services/smooks -> smooks.esb services/cbr/jbr -> cbr-jbr.esb each of them builds an .esb archive, and each project has it's own lib directory, so we can clean up the current lib/ext directory which contains everything and the kitchen sink.

6178

days inactive

6263

days old

esb-issues@lists.jboss.org

Manage subscription

12 comments

2 participants

tags (0)

participants (2)

Kurt Stam (JIRA)
Mark Little (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

[JBoss JIRA] Created: (JBESB-500) package rules, jbpm and smooks as services