[jira] Commented: (SM-1071) Provisioning system
[ https://issues.apache.org/activemq/browse/SM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40158 ] Guillaume Nodet commented on SM-1071: - I have been thinking about something like this for the Apache Directory Server as well. When we restructure around OSGi I want to be able to leverage OBR and add some group/cluster configuration concepts so that we can bring up a new server and point it to a config server url and a group name and have it provision bundles and configure itself. Of course I want to build this centralized management facility on top of ApacheDS LDAP to store configuration information by group, node name, etc., but this is a generic idea that could apply to a lot of OSGi applications, particularly server side apps like ServiceMix. Yeah, I was thinking about that too. If you use virtualization at the same time (like VMWare) it can be very powerful. Using http for accesing the config has some pros too, because you could use svn for example. (or other CMS / rest api). Anyway, a simple facade api should be able to abstract the backend. I am also thinking about some change management features for versioned configuration packages (for audit history, rollback to snapshot, etc.) and the ability to move change packages through development, QA, and production environments. I know a lot of this is beyond the scope of this issue, but it would be interesting to see if we can work together to satisfy the common requirements we have. Yeah, a bit beyond the scope ... but still very interesting. If we use svn or a CMS, wouldn't this feature be available at a cheap price ? at least for versioning of configurations. I don't know much about ldap. What kind of features would it bring ? > Provisioning system > --- > > Key: SM-1071 > URL: https://issues.apache.org/activemq/browse/SM-1071 > Project: ServiceMix > Issue Type: New Feature >Reporter: Guillaume Nodet > Fix For: 4.0 > > > Maybe using OBR > (http://felix.apache.org/site/apache-felix-osgi-bundle-repository-obr.html) or > Equinox (http://wiki.eclipse.org/index.php/Equinox_Provisioning). > Basically, i'm thinking about two things: > * leverage OBR to install features easily (activemq, ode, cxf, etc...) > * dynamic / automatic provisioning of applications > For the second one, a service could pull an HTTP url from time to time to > check is a new configuration for itself is available. if yes, download it > and uninstall stop / uninstall unneeded bundes, install new ones, etc... > The configuration would be a simple xml defining which bundles / version > should be started -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release ServiceMix 3.1.2
Hi Alex, Good catch, it should be .zip for windows platform, I update the http://cwiki.apache.org/confluence/display/SM/ServiceMix+3.1.2 Thanks very much Freeman Alex Boisvert wrote: Just a random question but shouldn't the Windows download be a .zip instead of .tar.gz? (I'm using the Linux version so it doesn't really affect me) alex On 9/20/07, Freeman Fang <[EMAIL PROTECTED]> wrote: Hi All, I have uploaded a version of ServiceMix 3.1.2 for you to review. See http://cwiki.apache.org/confluence/display/SM/ServiceMix+3.1.2 for all the links and release notes. [ ] +1 Release ServiceMix 3.1.2 [ ] ± 0 [ ] -1 Do not release ServiceMix 3.1.2 Cheers Freeman
Re: [VOTE] Release ServiceMix 3.1.2
Just a random question but shouldn't the Windows download be a .zip instead of .tar.gz? (I'm using the Linux version so it doesn't really affect me) alex On 9/20/07, Freeman Fang <[EMAIL PROTECTED]> wrote: > > Hi All, > > I have uploaded a version of ServiceMix 3.1.2 for you to review. See > http://cwiki.apache.org/confluence/display/SM/ServiceMix+3.1.2 > for all the links and release notes. > > [ ] +1 Release ServiceMix 3.1.2 > [ ] ± 0 > [ ] -1 Do not release ServiceMix 3.1.2 > > Cheers > > Freeman >
Re: ServiceMix 3.2?
I can probably devote a little time testing in the next week or so. Although extremely busy with a project I'm working on. I'll start taking a look at it this weekend. -jeff gnodet wrote: > > In the coming weeks, just after releasing 3.1.2. Let's plan for first > half of october or sooner if possible. Wanna help a bit and already > test the examples and distribution ? > > On 9/20/07, jpuro <[EMAIL PROTECTED]> wrote: >> >> When is the planned release of this? >> >> Thanks, >> >> Jeff >> -- >> View this message in context: >> http://www.nabble.com/ServiceMix-3.2--tf4490048s12049.html#a12805483 >> Sent from the ServiceMix - Dev mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/ServiceMix-3.2--tf4490048s12049.html#a12810650 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
[jira] Commented: (SM-1066) Distributed registry
[ https://issues.apache.org/activemq/browse/SM-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40157 ] Chris Custine commented on SM-1066: --- I think there are a couple of ways to achieve this. Similar to SM-1071, this might be achieved with Configuration Admin but I don't think there is any way currently to have distributed configurations in the spec. This is partly the reason for my idea to use ApacheDS as a centralized Configuration Admin system. Even if you did this outside of OSGi, it might make sense to embed a small ApacheDS LDAP server somewhere and have your cluster nodes configure themselves from that data. Just an idea... > Distributed registry > > > Key: SM-1066 > URL: https://issues.apache.org/activemq/browse/SM-1066 > Project: ServiceMix > Issue Type: New Feature >Reporter: Guillaume Nodet > Fix For: 4.0 > > > We need a way to implement a distributed NMR registry. Endpoints registered > in the NMR should be available for other instances on the cluster. > Or is this a purely distributed OSGi registry without being tied to > ServiceMix ? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1071) Provisioning system
[ https://issues.apache.org/activemq/browse/SM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40156 ] Chris Custine commented on SM-1071: --- I have been thinking about something like this for the Apache Directory Server as well. When we restructure around OSGi I want to be able to leverage OBR and add some group/cluster configuration concepts so that we can bring up a new server and point it to a config server url and a group name and have it provision bundles and configure itself. Of course I want to build this centralized management facility on top of ApacheDS LDAP to store configuration information by group, node name, etc., but this is a generic idea that could apply to a lot of OSGi applications, particularly server side apps like ServiceMix. I am also thinking about some change management features for versioned configuration packages (for audit history, rollback to snapshot, etc.) and the ability to move change packages through development, QA, and production environments. I know a lot of this is beyond the scope of this issue, but it would be interesting to see if we can work together to satisfy the common requirements we have. > Provisioning system > --- > > Key: SM-1071 > URL: https://issues.apache.org/activemq/browse/SM-1071 > Project: ServiceMix > Issue Type: New Feature >Reporter: Guillaume Nodet > Fix For: 4.0 > > > Maybe using OBR > (http://felix.apache.org/site/apache-felix-osgi-bundle-repository-obr.html) or > Equinox (http://wiki.eclipse.org/index.php/Equinox_Provisioning). > Basically, i'm thinking about two things: > * leverage OBR to install features easily (activemq, ode, cxf, etc...) > * dynamic / automatic provisioning of applications > For the second one, a service could pull an HTTP url from time to time to > check is a new configuration for itself is available. if yes, download it > and uninstall stop / uninstall unneeded bundes, install new ones, etc... > The configuration would be a simple xml defining which bundles / version > should be started -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release ServiceMix 3.1.2
On 9/20/07, Freeman Fang <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I have uploaded a version of ServiceMix 3.1.2 for you to review. See
> http://cwiki.apache.org/confluence/display/SM/ServiceMix+3.1.2
> for all the links and release notes.
>
> [ ] +1 Release ServiceMix 3.1.2
> [ ] ± 0
> [ ] -1 Do not release ServiceMix 3.1.2
While the binary starts up just fine, I cannot get a build from source
to complete successfully when working with a clean Maven repo.
Currently a clean build failing on the step1 profile with the
following:
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) org.apache.geronimo.specs:geronimo-servlet_2.4_spec:jar:1.1
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.geronimo.specs
-DartifactId=geronimo-servlet_2.4_spec \
-Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there: mvn deploy:deploy-file
-DgroupId=org.apache.geronimo.specs
-DartifactId=geronimo-servlet_2.4_spec \
-Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.servicemix:servicemix-components:jar:3.1.2
2) org.apache.geronimo.specs:geronimo-servlet_2.4_spec:jar:1.1
2) janino:janino:jar:2.3.2
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=janino -DartifactId=janino \
-Dversion=2.3.2 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there: mvn deploy:deploy-file -DgroupId=janino
-DartifactId=janino \
-Dversion=2.3.2 -Dpackaging=jar -Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.servicemix:servicemix-components:jar:3.1.2
2) janino:janino:jar:2.3.2
3) jivesoftware:smackx:jar:2.2.1
Try downloading the file manually from:
http://www.jivesoftware.org/smack/
Then, install it using the command:
mvn install:install-file -DgroupId=jivesoftware -DartifactId=smackx \
-Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there: mvn deploy:deploy-file -DgroupId=jivesoftware
-DartifactId=smackx \
-Dversion=2.2.1 -Dpackaging=jar -Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.servicemix:servicemix-components:jar:3.1.2
2) jivesoftware:smackx:jar:2.2.1
4) javax.activation:activation:jar:1.1
Try downloading the file manually from:
https://maven-repository.dev.java.net/nonav/repository/javax.activation/jars/activation-1.1.jar
Then, install it using the command:
mvn install:install-file -DgroupId=javax.activation
-DartifactId=activation \
-Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there: mvn deploy:deploy-file -DgroupId=javax.activation
-DartifactId=activation \
-Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.servicemix:servicemix-components:jar:3.1.2
2) org.codehaus.xfire:xfire-all:jar:1.2.5
3) org.codehaus.xfire:xfire-core:jar:1.2.5
4) javax.activation:activation:jar:1.1
--
4 required artifacts are missing.
for artifact:
org.apache.servicemix:servicemix-components:jar:3.1.2
from the specified remote repositories:
central (http://www.ibiblio.org/maven2),
servicemix-m2-repo
(http://svn.apache.org/repos/asf/incubator/servicemix/m2-repo),
apache.snapshots (http://svn.apache.org/maven-snapshot-repository),
apache-incubating (http://people.apache.org/repo/m2-incubating-repository),
codehaus-snapshots (http://repository.codehaus.org)
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61Ehttp://activemq.org/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Castor - http://castor.org/
[VOTE] Release ServiceMix 3.1.2
Hi All, I have uploaded a version of ServiceMix 3.1.2 for you to review. See http://cwiki.apache.org/confluence/display/SM/ServiceMix+3.1.2 for all the links and release notes. [ ] +1 Release ServiceMix 3.1.2 [ ] ± 0 [ ] -1 Do not release ServiceMix 3.1.2 Cheers Freeman
[jira] Created: (SM-1075) Investigate camel / servicemix integration
Investigate camel / servicemix integration -- Key: SM-1075 URL: https://issues.apache.org/activemq/browse/SM-1075 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Fix For: 4.0 Currently camel and servicemix works mainly side by side. The main value added of Camel is the DSL, so I'm wondering if it would be possible / worthwhile to rebuild the camel dsl on top of a stateless asynchronous api like servicemix one. This would enable a complete integration by not only sharing the exchange model, but also the endpoints and components. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1074) Lifecycle / clean shutdown
Lifecycle / clean shutdown -- Key: SM-1074 URL: https://issues.apache.org/activemq/browse/SM-1074 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Fix For: 4.0 We need to find a way to provide a clean shutdown of the NMR without loosing any messages. This means that Binding Components must stop accepting new requets (http, jms, etc..) while the pending messages are still be processed. When all messages have been processed, all components / endpoints can be shutdown. Maybe we need to add a method on the Endpoint interface like pause() / resume() that would only affect BC consumers and would inform them to stop consuming messages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1073) org.oasis_open.docs.wsn.b_2.Notify objects get silently dumped by DefaultMarshaller
org.oasis_open.docs.wsn.b_2.Notify objects get silently dumped by
DefaultMarshaller
---
Key: SM-1073
URL: https://issues.apache.org/activemq/browse/SM-1073
Project: ServiceMix
Issue Type: Bug
Components: servicemix-core
Affects Versions: 3.2
Environment: Windows XP
Reporter: Ryan Moquin
This is a bug in some form (that at the very least an exception or message
should be logged). I passed a jaxb object from one of my services into the
NotificationBroker.notify() method and a org.oasis_open.docs.wsn.b_2.Notify is
constructed with my object as the content:
public void notify(String topic, Object msg) throws JBIException {
Notify notify = new Notify();
NotificationMessageHolderType holder = new
NotificationMessageHolderType();
if (topic != null) {
TopicExpressionType topicExp = new TopicExpressionType();
topicExp.getContent().add(topic);
holder.setTopic(topicExp);
}
holder.setMessage(new NotificationMessageHolderType.Message());
holder.getMessage().setAny(msg);
notify.getNotificationMessage().add(holder);
send(notify);
}
Eventually the following method gets executed (in DefaultMarshaller) with the
Notify object that was created as the parameter in body, but since the Notify
object isn't an instance of any of the 3 things it's looking for, it returns
null (as a side note, the message variable isn't even used in this method):
protected Source asContent(NormalizedMessage message, Object body) {
if (body instanceof Source) {
return (Source) body;
} else if (body instanceof String) {
// lets assume String is the XML to send
return new StringSource((String) body);
} else if (body instanceof Node) {
return new DOMSource((Node) body);
}
return null;
}
This null then is put into the message variable as the content (line 56 on
DefaultMarshaller, the marshal method), hence the Notify object gets tossed:
Source content = asContent(message, body);
message.setContent(content);
This was all called by DefaultServicemixClient, which returns back to the
following method, with the in variable now populated with null as the content:
protected void populateMessage(MessageExchange exchange, Map exchangeProperties,
Map inMessageProperties, Object content)
throws MessagingException {
NormalizedMessage in = exchange.getMessage("in");
populateExchangeProperties(exchange, exchangeProperties);
populateMessageProperties(in, inMessageProperties);
getMarshaler().marshal(exchange, in, content);
}
Some sort of exception should be thrown since it doesn't like the Notify
method, instead of silently inserting null. More importantly though,
Servicemix shouldn't create an object to use that it doesn't like.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: ServiceMix 3.2?
In the coming weeks, just after releasing 3.1.2. Let's plan for first half of october or sooner if possible. Wanna help a bit and already test the examples and distribution ? On 9/20/07, jpuro <[EMAIL PROTECTED]> wrote: > > When is the planned release of this? > > Thanks, > > Jeff > -- > View this message in context: > http://www.nabble.com/ServiceMix-3.2--tf4490048s12049.html#a12805483 > Sent from the ServiceMix - Dev mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
ServiceMix 3.2?
When is the planned release of this? Thanks, Jeff -- View this message in context: http://www.nabble.com/ServiceMix-3.2--tf4490048s12049.html#a12805483 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
[jira] Commented: (SM-1071) Provisioning system
[ https://issues.apache.org/activemq/browse/SM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40155 ] Guillaume Nodet commented on SM-1071: - I don't think this is really specific to servicemix, so it may be interesting to check with the felix community for that. > Provisioning system > --- > > Key: SM-1071 > URL: https://issues.apache.org/activemq/browse/SM-1071 > Project: ServiceMix > Issue Type: New Feature >Reporter: Guillaume Nodet > Fix For: 4.0 > > > Maybe using OBR > (http://felix.apache.org/site/apache-felix-osgi-bundle-repository-obr.html) or > Equinox (http://wiki.eclipse.org/index.php/Equinox_Provisioning). > Basically, i'm thinking about two things: > * leverage OBR to install features easily (activemq, ode, cxf, etc...) > * dynamic / automatic provisioning of applications > For the second one, a service could pull an HTTP url from time to time to > check is a new configuration for itself is available. if yes, download it > and uninstall stop / uninstall unneeded bundes, install new ones, etc... > The configuration would be a simple xm defining which bundles / version > should be started -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1071) Provisioning system
[ https://issues.apache.org/activemq/browse/SM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-1071: Description: Maybe using OBR (http://felix.apache.org/site/apache-felix-osgi-bundle-repository-obr.html) or Equinox (http://wiki.eclipse.org/index.php/Equinox_Provisioning). Basically, i'm thinking about two things: * leverage OBR to install features easily (activemq, ode, cxf, etc...) * dynamic / automatic provisioning of applications For the second one, a service could pull an HTTP url from time to time to check is a new configuration for itself is available. if yes, download it and uninstall stop / uninstall unneeded bundes, install new ones, etc... The configuration would be a simple xml defining which bundles / version should be started was: Maybe using OBR (http://felix.apache.org/site/apache-felix-osgi-bundle-repository-obr.html) or Equinox (http://wiki.eclipse.org/index.php/Equinox_Provisioning). Basically, i'm thinking about two things: * leverage OBR to install features easily (activemq, ode, cxf, etc...) * dynamic / automatic provisioning of applications For the second one, a service could pull an HTTP url from time to time to check is a new configuration for itself is available. if yes, download it and uninstall stop / uninstall unneeded bundes, install new ones, etc... The configuration would be a simple xm defining which bundles / version should be started > Provisioning system > --- > > Key: SM-1071 > URL: https://issues.apache.org/activemq/browse/SM-1071 > Project: ServiceMix > Issue Type: New Feature >Reporter: Guillaume Nodet > Fix For: 4.0 > > > Maybe using OBR > (http://felix.apache.org/site/apache-felix-osgi-bundle-repository-obr.html) or > Equinox (http://wiki.eclipse.org/index.php/Equinox_Provisioning). > Basically, i'm thinking about two things: > * leverage OBR to install features easily (activemq, ode, cxf, etc...) > * dynamic / automatic provisioning of applications > For the second one, a service could pull an HTTP url from time to time to > check is a new configuration for itself is available. if yes, download it > and uninstall stop / uninstall unneeded bundes, install new ones, etc... > The configuration would be a simple xml defining which bundles / version > should be started -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1072) Versioning of servicemix endpoints
Versioning of servicemix endpoints -- Key: SM-1072 URL: https://issues.apache.org/activemq/browse/SM-1072 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Fix For: 4.0 To investigate ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1071) Provisioning system
Provisioning system --- Key: SM-1071 URL: https://issues.apache.org/activemq/browse/SM-1071 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Fix For: 4.0 Maybe using OBR (http://felix.apache.org/site/apache-felix-osgi-bundle-repository-obr.html) or Equinox (http://wiki.eclipse.org/index.php/Equinox_Provisioning). Basically, i'm thinking about two things: * leverage OBR to install features easily (activemq, ode, cxf, etc...) * dynamic / automatic provisioning of applications For the second one, a service could pull an HTTP url from time to time to check is a new configuration for itself is available. if yes, download it and uninstall stop / uninstall unneeded bundes, install new ones, etc... The configuration would be a simple xm defining which bundles / version should be started -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
ServiceMix 4.0 dev plan
I've create a few JIRAs for ServiceMix 4.0. See https://issues.apache.org/activemq/browse/SM/fixforversion/11845 If anyone wants to work on something, please assign one to yourself. I haven't put any more precise version / milestone fix yet... Feel free to comment and start discussion around each of these topics. Also, this does not include any documentation / examples etc which need to be done too. I'm thinking a docbook based users guide might be a good idea. Also, I think we should releasing milestone as soon as possible and have small release cycles -- quite the contrary we did on smx 3.x ;-) So maybe a first one in october after releasing 3.1.2 and 3.2 asap. -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
[jira] Created: (SM-1066) Distributed registry
Distributed registry Key: SM-1066 URL: https://issues.apache.org/activemq/browse/SM-1066 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Fix For: 4.0 We need a way to implement a distributed NMR registry. Endpoints registered in the NMR should be available for other instances on the cluster. Or is this a purely distributed OSGi registry without being tied to ServiceMix ? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1065) ActiveMQ integration
ActiveMQ integration Key: SM-1065 URL: https://issues.apache.org/activemq/browse/SM-1065 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Fix For: 4.0 ActiveMQ jars are already OSGified, but we may want to create a bundle that would create a broker by default and registering a pooled connection factory in OSGi maybe. That way, everyone could use the ConnectionFactory registered in OSGi. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1070) ODE integration
[ https://issues.apache.org/activemq/browse/SM-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-1070: Fix Version/s: 4.0 > ODE integration > --- > > Key: SM-1070 > URL: https://issues.apache.org/activemq/browse/SM-1070 > Project: ServiceMix > Issue Type: New Feature >Reporter: Guillaume Nodet > Fix For: 4.0 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1069) JAX-WS support
JAX-WS support -- Key: SM-1069 URL: https://issues.apache.org/activemq/browse/SM-1069 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Fix For: 4.0 It should be easy to expose a JAX-WS annotated bean on the bus, or even outside using http/soap ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1070) ODE integration
ODE integration --- Key: SM-1070 URL: https://issues.apache.org/activemq/browse/SM-1070 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1064) Endpoint filtering and selection
Endpoint filtering and selection Key: SM-1064 URL: https://issues.apache.org/activemq/browse/SM-1064 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Fix For: 4.0 We need to refine the org.apache.servicemix.api.Reference interface and the way they are build. It may be worth defining two interfaces for filtering, selecting, querying and choosing endpoint. This could be used to apply policies and/or interceptors to endpoints. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1067) JMS / JCA flow
JMS / JCA flow -- Key: SM-1067 URL: https://issues.apache.org/activemq/browse/SM-1067 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Fix For: 4.0 Implement a JMS / JCA flow. Note that the JMS flow in 3.x is not really reliable and does not support redelivery / rollback / transactions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1068) Transaction support
Transaction support --- Key: SM-1068 URL: https://issues.apache.org/activemq/browse/SM-1068 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Fix For: 4.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1063) Policy framework
Policy framework Key: SM-1063 URL: https://issues.apache.org/activemq/browse/SM-1063 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Fix For: 4.0 I think it would be interesting to have a policy framework so that some aspects could be applied to endpoints easily. A WS-Policy document could be attached to an endpoint (the same way as the wsdl, using a known property containing a url pointing to the document). Each assertion would be parsed and would automatically be processed by the policy handler. Policy handlers could be registered on the NMR and would provide support for a given kind of assertions. For example: persistence, transaction, security could be applied using WS-Policy. I think it would also be worth to have such policies applied using some endpoint filters so that they can be applied globally without modifying the endpoints themselves. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1062) Security framework
Security framework -- Key: SM-1062 URL: https://issues.apache.org/activemq/browse/SM-1062 Project: ServiceMix Issue Type: New Feature Reporter: Guillaume Nodet Fix For: 4.0 Need to support authentication, authorization, encryption on both the message level and transport level. We could leverage Acegi and/or JSR-115 and the existing smx 3.x security framework. We also need to support WS-Security as a way to authenticate / encrypt. SAML ? This may be linked to the policy framework so that a security policy could be applied easily to some endpoints. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-1060) cxf se should support ComponentContext and DeliveryChannel injection
cxf se should support ComponentContext and DeliveryChannel injection Key: SM-1060 URL: https://issues.apache.org/activemq/browse/SM-1060 Project: ServiceMix Issue Type: Improvement Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: How to get the ComponentContext in CXF SU?
Freeman, I think being able to inject the endpoint DeliveryChannel and ComponentContext is a really important feature. Can you raise a JIRA for that please ? On 9/20/07, Freeman Fang <[EMAIL PROTECTED]> wrote: > Hi Ryan, > > Attachment is the schema for servicemix-cxf-se. > > So far the cxf-se is not exactly same as jsr-181 service engine, so I > think now we don't support it. > Also I investigate the jsr-181 client proxy issue you mentioned in > previous mail, we don't support it in cxf se neither, sorry for > misleading previous response. > The main purpose we add cxf-bc and cxf-se is leverage cxf ws-* features. > You can see the tests and examples how the typical scenario looks like. > > If you need any feature we don't support now, please fill jira issue. > > Best Regards > > Freeman > > Ryan Moquin wrote: > > I'm still having a hard time figuring out how to replicated my interservice > > communication through the bus between two CXF services in Servicemix. My > > latest problem is that this doesn't appear to work: > > > > > > > > > > > > > > > > > > > > According to the servicemix docs, it says I should be able to reference the > > context which was created as a parent bean. > > > > Is there an xsd I can look at for cxfse? I need to figure out how I can do > > interservice communication with it over the bus still. > > > > > > > -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
Re: question about servicemix 3.1.2 release
So I've just forwarded to the dev list the infra jira issues about moving ServiceMix resources. Basically, mailing lists will become [EMAIL PROTECTED], the web site will be moved to http://servicemix.apache.org/, the svn repo to https://svn.apache.org/repos/asf/servicemix/ Infra should take care about all this. For the samples, I don't think this is necessary to change them right now, so just change the main pom and it should be fine. On 9/20/07, Freeman Fang <[EMAIL PROTECTED]> wrote: > Hi Guillaume, > I also notice that in our samples and archtype pom, there are incubating > repositories listed, which now is > http://people.apache.org/repo/m2-incubating-repository, I guess those > also need be replaced but I am not sure what is the new url > And in our root pom. there is some basic description about servicemix > such as scm and distributionManagement has incubator thing as well, > what's the new replacement for those? > Thanks very much > > Freeman > > Freeman Fang wrote: > > Hi Guillaume, > > What's the new servicemix site after graduate, before we are > > http://incubator.apache.org/servicemix/, should it be > > http://apache.org/servicemix/ now? > > Who is responsible for creating this site? > > > > Best Regards > > > > Freeman > > > > Freeman Fang wrote: > >> Hi Guillaume, > >> I just deploy it on apache server, my home directory. > >> http://people.apache.org/~ffang/maven_staging/org/apache/servicemix/ > >> But this one with incubating. > >> And I will change the version and remove incubation disclaimers to > >> re-deploy it. Then we can start vote. > >> > >> Best Regards > >> > >> Freeman > >> > >> > >> Guillaume Nodet wrote: > >>> How's the release going ? > >>> As ServiceMix has now graduated and depending where you are in the > >>> process, > >>> it may be nice to remove the incubation disclaimers and "incubating" > >>> from the version and have our first official release. > >>> Thoughts ? > >>> > >>> On 9/14/07, Freeman Fang <[EMAIL PROTECTED]> wrote: > >>> > Thanks Guillaume > Fixed the release wiki. > > Freeman > > Guillaume Nodet wrote: > > > ServiceMix 3.1.2 does not depend on camel afaik, only trunk > > does.And for the > > branch, you should try using https instead of http > > (could you fix the release instructions if they are misleading?) > > > > On 9/13/07, Freeman Fang <[EMAIL PROTECTED]> wrote: > > > > > >> Hi Guillaume, > >> > >> The release guide say that there should be no snapshot > >> dependency, but > >> servicemix-camel depend on camel 1.1 snapshot, without this snapshot > >> dependency, this service-engine can't get compiled. How to > >> handle this > >> problem? > >> And I failed to do > >> svn mkdir > >> http://svn.apache.org/repos/asf/incubator/servicemix/branches/servicemix- > >> > >> 3.1.2 > >> -m "ServiceMix 3.1.2 Release Branch" > >> The error is > >> svn: MKACTIVITY of > >> '/repos/asf/!svn/act/334b9964-033a-0410-a474-8f0ea706a33b': 403 > >> Forbidden (http://svn.apache.org) > >> Any Suggestion is appreciated. > >> Thanks very much > >> > >> > >> Freeman > >> > >> Guillaume Nodet wrote: > >> > >> > >>> I have updated the releasing notes to something that I hope will > >>> work > >>> > >>> > >> ;-) > >> > >> > >>> See http://cwiki.apache.org/confluence/display/SM/Release+Guide > >>> If you have any questions, just yell ! > >>> > >>> On 9/12/07, Nodet Guillaume <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>> > On Sep 12, 2007, at 8:46 AM, Freeman Fang wrote: > > Hi all, > > When are we going to release servicemix 3.1.2? As a new > commiter in > servicemix team, I'd like to know how is the release process looks > > > >> like. > >> > >> > If possible, shall I be release manager of this time? :-) > > Yeah of course you can :-) > There are some instructions available at > http://incubator.apache.org/servicemix/release-guide.html > but these are a bit outdated, so we'll have to update those > (and maven > > > >> can > >> > >> > not really be used for > creating the release)... > Let me have a breakfast and write something more accurate... > > Any suggestion is appreciated. > > Best Regards > > > Freeman > > > -- > Cheers, > Guillaume Nodet > > Blog: http://gnodet.blogspot.com/ > > > > > >>> > > > > > > > >>> > >>> > >>> > >> > > > -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
Fwd: [jira] Created: (INFRA-1367) Create new TLP ServiceMix
FYI -- Forwarded message -- From: Guillaume Nodet (JIRA) <[EMAIL PROTECTED]> Date: Sep 19, 2007 9:41 PM Subject: [jira] Created: (INFRA-1367) Create new TLP ServiceMix To: [EMAIL PROTECTED] Create new TLP ServiceMix - Key: INFRA-1367 URL: https://issues.apache.org/jira/browse/INFRA-1367 Project: Infrastructure Issue Type: Task Security Level: public (Regular issues) Components: TLP Admin Reporter: Guillaume Nodet The board has agreed to create the ServiceMix top level project. To aid in the process, would the Infrastructure team please do the following: #=== [0] Root Tasks Create unix group "servicemix" Create new DNS entry "servicemix.apache.org" and configure into website server instance #=== [1] Mailing List (i) addresses Please migrate the existing archives, subscribers and moderators to the following lists: [EMAIL PROTECTED] from servicemix-dev@geronimo.apache.org [EMAIL PROTECTED] from [EMAIL PROTECTED] [EMAIL PROTECTED] from [EMAIL PROTECTED] [EMAIL PROTECTED] from [EMAIL PROTECTED] (ii) New list Please create this new mailing list at the same time, with same moderators than the dev list [EMAIL PROTECTED] (iii) archives: please provide for merged archives for: servicemix-dev@geronimo.apache.org merged with [EMAIL PROTECTED]; [EMAIL PROTECTED] merged with [EMAIL PROTECTED]; [EMAIL PROTECTED] merged with [EMAIL PROTECTED]; and [EMAIL PROTECTED] merged with [EMAIL PROTECTED] mbox 1. http://servicemix.apache.org/mail/servicemix/dev/MM.gz 2. http://servicemix.apache.org/mail/servicemix/users/MM.gz 3. http://servicemix.apache.org/mail/servicemix/commits/MM.gz 4. http://servicemix.apache.org/mail/servicemix/issues/MM.gz 5. [EMAIL PROTECTED] to be archived in the private area. (iv) options I. Reply-To: Header [X] yes [ ] no NOTE: [EMAIL PROTECTED] -> [EMAIL PROTECTED] NOTE: [EMAIL PROTECTED] -> [EMAIL PROTECTED] II. Message Trailer [ ] yes [X] no #=== [2] Source Tracker (i) Subversion Move the existing incubator/servicemix tree to TLP #=== [3] Initial Committer list Same as existing #=== [4] cwiki The cwiki does not need to be moved. [5] Add gnodet (PMC chair) to appropriate authorizations in auth file. [6] Create "servicemix" directory in /www/www.apache.org/dist directory for publishing software. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/
