My use cases are multiple. #1. I have an application which uses the configuration admin. I want to link the configurations to the application somehow and make sure it will be installed as part of the installation process
#2. I have a file which I know how to transform into a bundle using a URL handler and I want to install it as part of the application. I think that's the way web applications should be supported, but this is a more general thing, as you can then support much more artifact types. I'm thinking about deploying this way a simple blueprint application using the blueprint url handler from karaf for example. Given the web app spec specifies a url handler, I think it would make sense to reuse it too On Tue, Feb 16, 2010 at 12:02, Alasdair Nottingham <[email protected]> wrote: > Hi, > > I'm not entirely sure I follow what you are asking for here. Do you > want to be able to access non jar content using the AriesApplication > interface, or do you want to convert non-jar artifacts into bundles > somehow or something else? > > Thanks > Alasdair > > On 16 February 2010 08:00, Guillaume Nodet (JIRA) <[email protected]> wrote: >> AriesApplicationManagerImpl#createApplication should support artifacts that >> are not jars somehow >> ------------------------------------------------------------------------------------------------ >> >> Key: ARIES-168 >> URL: https://issues.apache.org/jira/browse/ARIES-168 >> Project: Aries >> Issue Type: Improvement >> Components: Application >> Reporter: Guillaume Nodet >> >> >> Deploying configurations for example or plain blueprint configuration files >> would be really handy >> >> -- >> This message is automatically generated by JIRA. >> - >> You can reply to this email to add a comment to the issue online. >> >> > > > > -- > Alasdair Nottingham > [email protected] > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
