Re: Exception on Bamboo server...

On Feb 19, 2008 7:38 AM, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > Caused by: org.tmatesoft.svn.core.SVNException: svn: Failed to add > directory 'pax-confman-service': object of the same name already exists Looks as if old dirs cannot be deleted, will take a look at the file storage area on the

Exception on Bamboo server...

There is a lot of these exceptions happening in Bamboo, written to the tomcat log. 2008-02-19 07:42:15,101 ERROR [BAM::BuildChangeDetector] [DefaultBuildChangeDetector] Failed to get the build source code com.atlassian.bamboo.repository.RepositoryException: PAX Confman - Default at com

[issues] Created: (CONFMAN-7) LDAP Loader

LDAP Loader --- Key: CONFMAN-7 URL: http://issues.ops4j.org/jira/browse/CONFMAN-7 Project: Pax ConfMan Issue Type: New Feature Reporter: Niclas Hedhman Assignee: Niclas Hedhman A ConfigurationProvider for LD

[issues] Created: (CONFMAN-6) SQL Loader

SQL Loader -- Key: CONFMAN-6 URL: http://issues.ops4j.org/jira/browse/CONFMAN-6 Project: Pax ConfMan Issue Type: New Feature Reporter: Niclas Hedhman Assignee: Niclas Hedhman The ConfMan should be able to lo

[issues] Created: (CONFMAN-5) ConfigurationProvider interface

ConfigurationProvider interface --- Key: CONFMAN-5 URL: http://issues.ops4j.org/jira/browse/CONFMAN-5 Project: Pax ConfMan Issue Type: New Feature Reporter: Niclas Hedhman Assignee: Niclas

Re: Differencies in class loader usage in http service implementations

On Tuesday 19 February 2008 01:25, Damian Gołda wrote: > What implementation of HttpService works correct? Neither. > P.S. > In OSGI 4.1 spec I can't find anything about classloaders in > HttpService description. Correct observation. Http Service spec doesn't involve classloading, and servlets

Re: Differencies in class loader usage in http service implementations

Hi Damian, I cannot tell who's right. But to me using the context class loader from the registration moment does not look as the right approach as it can be any class loader not the one that registered the servlet. Back to your case, can you be more detailed about your use case? How is the servlet

Differencies in class loader usage in http service implementations

In my application I used Equinox HttpService implementation but now I'm trying to move to Pax Web. I have a problem with different class loader strategy used in these two implementations: 1. While registering of servlet, Equinox creates ServletRegistration instance and stores current context classl

[issues] Commented: (INFRA-49) Remove dgolda user

[ http://issues.ops4j.org/jira/browse/INFRA-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11084 ] Damian Golda commented on INFRA-49: --- Thank you. > Remove dgolda user > -- > > Key: INFRA-

[issues] Created: (INFRA-50) Setup Bamboo to deploy snapshots to http://repository.ops4j.org/mvn-snapshots in On Change plans

Setup Bamboo to deploy snapshots to http://repository.ops4j.org/mvn-snapshots in On Change plans Key: INFRA-50 URL: http://issues.ops4j.org/jira/browse/INFRA-50

[issues] Created: (INFRA-49) Remove dgolda user

Remove dgolda user -- Key: INFRA-49 URL: http://issues.ops4j.org/jira/browse/INFRA-49 Project: Infrastructure Issue Type: Task Components: UserManagement Reporter: Damian Golda Assignee: Pete

[issues] Created: (PAXSB-4) BundleClassLoader.getResources(String) don't use parent classloader

BundleClassLoader.getResources(String) don't use parent classloader Key: PAXSB-4 URL: http://issues.ops4j.org/jira/browse/PAXSB-4 Project: Pax Swissbox Issue Type: Bug

[issues] Created: (PAXSB-3) BundleClassLoader.getResources(String) should return empty enumeration instead of null

BundleClassLoader.getResources(String) should return empty enumeration instead of null -- Key: PAXSB-3 URL: http://issues.ops4j.org/jira/browse/PAXSB-3 Project: Pax S