Re: Blueprint schema blocks nested static class names

2012-05-23 Thread Daniel Kulp
On Tuesday, May 22, 2012 05:51:10 PM Sergey Beryozkin wrote: I've attached a simple patch to https://issues.apache.org/jira/browse/ARIES-855 Let me know please if you think it can be committed now or expect a bit more work done on it. Looks fine by me. Commit away! Right now I'm

Re: Blueprint schema blocks nested static class names

2012-05-22 Thread Sergey Beryozkin
I've attached a simple patch to https://issues.apache.org/jira/browse/ARIES-855 Let me know please if you think it can be committed now or expect a bit more work done on it. Right now I'm thinking that retrying once only in case of the bean load failure is reasonable. Introducing a system

Re: Blueprint schema blocks nested static class names

2012-05-14 Thread Sergey Beryozkin
Hi All I managed to click on the link leading to the subscription page :-) and eventually forwarded the original post to the osgi-dev Thanks, Sergey On 11/05/12 13:49, David Bosschaert wrote: Just for clarity, the mailing lists and bugzilla instance mentioned before [1]

Re: Blueprint schema blocks nested static class names

2012-05-04 Thread Sergey Beryozkin
Hi Jeremy Hi, The blueprint.xsd is defined by the OSGi Alliance, so this would need to be changed in the spec. The Blueprint spec doesn't mention inner classes so there's nothing AFAICT in the spec that excludes the use of them - so arguably you could open a bug at the OSGi Alliance [1].

Blueprint schema blocks nested static class names

2012-04-02 Thread Sergey Beryozkin
Hi, The blueprint schema [1] blocks the class names containing a '$' character, specifically, a Tclass types expects all the Java class names to match the xsd:NCName pattern. Thus attempting to load a class such as a.b.MyClass$MyNestedClass fails with the schema validation error which as it