On 5/4/07, Peter Neubauer <[EMAIL PROTECTED]> wrote:
Anyone else with more knowledge who can shed some light on this?
Essentially, OSGi Alliance Enterprise Expert Group (EEG) is currently
in the process of collecting Request For Proposals (RFPs) which is a
fairly open process to the general pu
Richard S. Hall wrote:
The svn repo move has occurred. For people with checked out copies,
you will need to use the "svn switch" command to associate your
workspace with the new URL. I believe the command for doing this for
the trunk is:
svn switch https://svn.apache.org/repos/asf/felix/tr
The svn repo move has occurred. For people with checked out copies, you
will need to use the "svn switch" command to associate your workspace
with the new URL. I believe the command for doing this for the trunk is:
svn switch https://svn.apache.org/repos/asf/felix/trunk
If you have other di
Well,
I am not involved in the spec but I would guess that at the most
Spring would become an optional part of the spec since one of the main
goals of OSGi is to be lean and slim. At the least I guess that the
Declarative Services spec will be changed to make the declaration part
Spring context-xm
[
https://issues.apache.org/jira/browse/FELIX-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clement Escoffier closed FELIX-278.
---
All seems ok. I close the issue.
> Allow iPOJO instance to be unamed
> --
Carlos Herrando wrote:
OK, many thanks.
Keep in mind, if you want to use it, you might very well just be able to
modify its pom file to depend on a new servlet JAR, since we had been
using it with servlet 2.3 previously, I believe...
-> richard
Richard S. Hall escribió:
Carlos Herrando w
OK, many thanks.
Richard S. Hall escribió:
Carlos Herrando wrote:
Hello,
I've just build the trunk, but the HTTP service bundle isn't created.
Then if I write "mvn install" inside the http folder I get an error.
Could you help me to build the HTTP bundle?
This is precisely why it isn't being
Carlos Herrando wrote:
Hello,
I've just build the trunk, but the HTTP service bundle isn't created.
Then if I write "mvn install" inside the http folder I get an error.
Could you help me to build the HTTP bundle?
This is precisely why it isn't being built from the trunk pom file... :-)
The iss
Richard S. Hall a écrit :
Clement can correct me if I am wrong, but this also sounds similar to
his "arch" command for iPOJO, which can be used to reflect on iPOJO
components.
You're right.
However, there is two difference :
- the iPOJO Architecture support the extensibility (as iPOJO is
exte
Hello,
I've just build the trunk, but the HTTP service bundle isn't created.
Then if I write "mvn install" inside the http folder I get an error.
Could you help me to build the HTTP bundle?
Best regards
Carlos.
I don't know if there are any pointers.
Interface21 joined the OSGi Alliance recently and are working withing
the enterprise expert group on the possibility of defining a spec
related to Spring-OSGi.
I don't think there is much more news than that.
-> richard
Carsten Ziegeler wrote:
Last we
Chris Custine wrote:
Since Individual users can configure their own private notifications,
this
is probably unnecessary.
Would be my thought too, especially since I often make lots of little
formatting changes and don't always remember to check that "minor
change" box.
I am not sure why it
Clement Escoffier wrote:
Hello
Felix Meschberger a écrit :
Hi Richard,
In Felix-277 you propose to "privatize" the ServiceTracker and make the
LogService package a dynamic dependency. I think, this is a good idea
and
will, as noted in the issue, implement this.
While doing this, there is an
I think that sounds reasonable, this is a good use case for
importing/exporting the same package...
As Clement noted, you could use the same approach for the log service if
you prefer to have a consistent approach, since I imagine the bloat is
negligible.
Either way, I am fine with it.
-> r
Clement can correct me if I am wrong, but this also sounds similar to
his "arch" command for iPOJO, which can be used to reflect on iPOJO
components.
-> richard
Felix Meschberger wrote:
Hi Didier,
Thanks for the hint, and also to Marcel.
So I will look at those two projects for inspiration.
Last week at a conference Rod Johnson did a presentation on the
future of Spring. Well, the interesting part was the brief
introduction of the Spring OSGi sub project. He mentioned several
times (and had in on his slides) that Spring might become part of
OSGi R5. Does anyone know something
[
https://issues.apache.org/jira/browse/FELIX-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall resolved FELIX-278.
---
Resolution: Fixed
Assignee: Richard S. Hall
I applied the patch. Clement, please close i
Since Individual users can configure their own private notifications, this
is probably unnecessary.
On 5/3/07, Richard S. Hall <[EMAIL PROTECTED]> wrote:
This is the first time I have noticed Confluence sending messages to the
commits list. Do we want this?
If so, then we should change the ma
This is the first time I have noticed Confluence
sending messages to the commits list. Do we want this?
If so, then we should change the mailing list that Confluence is using;
currently, it is using [EMAIL PROTECTED], but it should switch it to
[EMAIL PROTECTED] if we want it posting messages.
Hi Didier,
Thanks for the hint, and also to Marcel.
So I will look at those two projects for inspiration.
Regards
Felix
On 5/3/07, Didier Donsez <[EMAIL PROTECTED]> wrote:
Humberto has defined too this kind of API for ServiceBinder.
He provided also a graphical console to display component i
Humberto has defined too this kind of API for ServiceBinder.
He provided also a graphical console to display component instances and
the current bindings between them.
http://www.humbertocervantes.net/servicebinder/images/ArchViewer.png
Didier
Marcel Offermans wrote:
Hello Felix,
On May 3,
Hello Felix,
On May 3, 2007, at 13:59 , Felix Meschberger wrote:
> The API itself is exported and there will probably be some service
providing the actual access
This is interesting, because such an API would probably be similar to
the API that is currently used in the dependency manager.
Hello
Felix Meschberger a écrit :
Hi Richard,
In Felix-277 you propose to "privatize" the ServiceTracker and make the
LogService package a dynamic dependency. I think, this is a good idea and
will, as noted in the issue, implement this.
While doing this, there is another Compendium Service dep
Hi Richard,
In Felix-277 you propose to "privatize" the ServiceTracker and make the
LogService package a dynamic dependency. I think, this is a good idea and
will, as noted in the issue, implement this.
While doing this, there is another Compendium Service dependency in the scr:
Configuration Ad
Hi all,
While working on the Felix scr project and using it heavily inhouse, I
realized, that I have troubles manageing the components: I cannot easily
see, which components are registered, which are active, and so force. So I
thought about adding a management API to the scr project which would e
[
https://issues.apache.org/jira/browse/FELIX-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_1249
]
Felix Meschberger commented on FELIX-279:
-
I will modify the way, that components are activated from synchrono
[
https://issues.apache.org/jira/browse/FELIX-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned FELIX-279:
---
Assignee: Felix Meschberger
> Concurrency Issues when enabling components
> --
Concurrency Issues when enabling components
---
Key: FELIX-279
URL: https://issues.apache.org/jira/browse/FELIX-279
Project: Felix
Issue Type: Bug
Components: Declarative Services
[
https://issues.apache.org/jira/browse/FELIX-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on FELIX-277 started by Felix Meschberger.
> Improve SCR packaging to make it simpler to deploy and use
> --
>
[
https://issues.apache.org/jira/browse/FELIX-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493332
]
Felix Meschberger commented on FELIX-277:
-
Sounds reasonable. I will do that.
> Improve SCR packaging to make
[
https://issues.apache.org/jira/browse/FELIX-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned FELIX-277:
---
Assignee: Felix Meschberger
> Improve SCR packaging to make it simpler to deploy and u
31 matches
Mail list logo
