[jira] Commented: (XBEAN-60) Support multiple namespaces
[ http://issues.apache.org/jira/browse/XBEAN-60?page=comments#action_12451562 ] Stefan Kleineikenscheidt commented on XBEAN-60: --- That's actually also true for the Ant-Task. Support multiple namespaces --- Key: XBEAN-60 URL: http://issues.apache.org/jira/browse/XBEAN-60 Project: XBean Issue Type: Improvement Components: maven-plugin Affects Versions: 2.7 Reporter: Kohsuke Kawaguchi It would be nice if the maven plugin would allow one to define beans across multiple namespaces. Today, if I specify two executions of XBeanMojo, the following two files will be simply overwritten: target/xbean/META-INF/spring.handlers target/xbean/META-INF/spring.schemas -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (XBEAN-39) NPE in XBeanHelper.createBeanDefinitionReader with some Classloaders
[ http://issues.apache.org/jira/browse/XBEAN-39?page=comments#action_12427800 ] Stefan Kleineikenscheidt commented on XBEAN-39: --- A fix of this issue at Spring seems to be on its way, too: http://opensource.atlassian.com/projects/spring/browse/SPR-2401 NPE in XBeanHelper.createBeanDefinitionReader with some Classloaders Key: XBEAN-39 URL: http://issues.apache.org/jira/browse/XBEAN-39 Project: XBean Issue Type: Bug Affects Versions: 2.0, 2.1, 2.2, 2.3, 2.4, 2.5 Reporter: Stefan Kleineikenscheidt Assigned To: Guillaume Nodet Fix For: 2.6 Attachments: XBEAN-39.patch, XBEAN-39.patch XBean fails on systems with some classloaders, which do not return sensible values from the following methods pkg.getImplementationVersion(); or cl.getResourceAsStream(name); This leads to a) a NPE thrown by SpringVersion.getVersion, b) the property files with custom mappings are not found. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
RE: XBEAN-39 - what's next?
Thanks for that! :-) -- Stefan Kleineikenscheidt tel. +49 (711) 99 33 035 Rosenbergstr. 58 mob. +49 (172) 130 54 77 70176 Stuttgart (GERMANY) [EMAIL PROTECTED] From: Guillaume Nodet [mailto:[EMAIL PROTECTED] Sent: Friday, August 11, 2006 8:01 PM To: dev@geronimo.apache.org Subject: Re: XBEAN-39 - what's next? There is no need to review for bugfixes. I will commit it asap. Thanks for this patch. On 8/11/06, Stefan Kleineikenscheidt [EMAIL PROTECTED] wrote: Hi all, I've attached a second version of patch to XBEAN-39 with the changes Guillaume suggested. As far as I understand the process PMC members have to review and vote for the patch. So, I please have a look at it - and vote for it... :-) - http://issues.apache.org/jira/browse/XBEAN-39 Cheers, -Stefan -- Stefan Kleineikenscheidt tel. +49 (711) 99 33 035 Rosenbergstr. 58 mob. +49 (172) 130 54 77 70176 Stuttgart (GERMANY) [EMAIL PROTECTED] -- Cheers, Guillaume Nodet
XBEAN-39 - what's next?
Hi all, I've attached a second version of patch to XBEAN-39 with the changes Guillaume suggested. As far as I understand the process PMC members have to review and vote for the patch. So, I please have a look at it - and vote for it... :-) - http://issues.apache.org/jira/browse/XBEAN-39 Cheers, -Stefan -- Stefan Kleineikenscheidt tel. +49 (711) 99 33 035 Rosenbergstr. 58 mob. +49 (172) 130 54 77 70176 Stuttgart (GERMANY) [EMAIL PROTECTED]
[jira] Created: (XBEAN-39) NPE in XBeanHelper.createBeanDefinitionReader with some Classloaders
NPE in XBeanHelper.createBeanDefinitionReader with some Classloaders Key: XBEAN-39 URL: http://issues.apache.org/jira/browse/XBEAN-39 Project: XBean Issue Type: Bug Affects Versions: 2.5, 2.4, 2.3, 2.2, 2.1, 2.0 Reporter: Stefan Kleineikenscheidt XBean fails on systems with some classloaders, which do not return sensible values from the following methods pkg.getImplementationVersion(); or cl.getResourceAsStream(name); This leads to a) a NPE thrown by SpringVersion.getVersion, b) the property files with custom mappings are not found. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (XBEAN-39) NPE in XBeanHelper.createBeanDefinitionReader with some Classloaders
[ http://issues.apache.org/jira/browse/XBEAN-39?page=all ] Stefan Kleineikenscheidt updated XBEAN-39: -- Attachment: XBEAN-39.patch Patch attached. Solution: After everyting else has failed, XBean tries to look up a system property 'xbean.dir'. The system property points to a directory, where XBean can load the property files for the custome mapping files and a additional xbean.properties file, which contains a property 'spring.version'. NPE in XBeanHelper.createBeanDefinitionReader with some Classloaders Key: XBEAN-39 URL: http://issues.apache.org/jira/browse/XBEAN-39 Project: XBean Issue Type: Bug Affects Versions: 2.0, 2.1, 2.2, 2.3, 2.4, 2.5 Reporter: Stefan Kleineikenscheidt Attachments: XBEAN-39.patch XBean fails on systems with some classloaders, which do not return sensible values from the following methods pkg.getImplementationVersion(); or cl.getResourceAsStream(name); This leads to a) a NPE thrown by SpringVersion.getVersion, b) the property files with custom mappings are not found. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (XBEAN-39) NPE in XBeanHelper.createBeanDefinitionReader with some Classloaders
[ http://issues.apache.org/jira/browse/XBEAN-39?page=comments#action_12427176 ] Stefan Kleineikenscheidt commented on XBEAN-39: --- We are using webMethods' IntegrationServer. * Regarding the SpringVersion.getVersion problem: I like your solution better, as we avoid the properties file. * Regarding the second problem: Absolutely fine with me. :-) NPE in XBeanHelper.createBeanDefinitionReader with some Classloaders Key: XBEAN-39 URL: http://issues.apache.org/jira/browse/XBEAN-39 Project: XBean Issue Type: Bug Affects Versions: 2.0, 2.1, 2.2, 2.3, 2.4, 2.5 Reporter: Stefan Kleineikenscheidt Attachments: XBEAN-39.patch XBean fails on systems with some classloaders, which do not return sensible values from the following methods pkg.getImplementationVersion(); or cl.getResourceAsStream(name); This leads to a) a NPE thrown by SpringVersion.getVersion, b) the property files with custom mappings are not found. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (XBEAN-39) NPE in XBeanHelper.createBeanDefinitionReader with some Classloaders
[ http://issues.apache.org/jira/browse/XBEAN-39?page=all ]
Stefan Kleineikenscheidt updated XBEAN-39:
--
Attachment: XBEAN-39.patch
Attached second version of the patch. As Guillaume suggested, The XBeanHelper
tries to load a Spring 2.0 class. If that fails, it knows we are on Spring
1.2.x:
public static XmlBeanDefinitionReader createBeanDefinitionReader(
SpringApplicationContext applicationContext,
BeanDefinitionRegistry registry,
List xmlPreprocessors) {
String version = 2.0;
try {
Class spring20Clazz =
Class.forName(org.springframework.core.AttributeAccessorSupport);
version = 2.0;
} catch(ClassNotFoundException e) {
version = 1.2.8;
}
}
}
NPE in XBeanHelper.createBeanDefinitionReader with some Classloaders
Key: XBEAN-39
URL: http://issues.apache.org/jira/browse/XBEAN-39
Project: XBean
Issue Type: Bug
Affects Versions: 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
Reporter: Stefan Kleineikenscheidt
Attachments: XBEAN-39.patch, XBEAN-39.patch
XBean fails on systems with some classloaders, which do not return sensible
values from the following methods
pkg.getImplementationVersion(); or
cl.getResourceAsStream(name);
This leads to
a) a NPE thrown by SpringVersion.getVersion,
b) the property files with custom mappings are not found.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
RE: [XBEAN] Mailing lists
As a user of XBean, Id really appreciate a separate list. Thanks Guilaume for bringing this up. :-) -Stefan From: Guillaume Nodet [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 01, 2006 7:20 PM To: dev@geronimo.apache.org Subject: Re: [XBEAN] Mailing lists This is one of the reason why I'd like to have mailing list for xbean :) Else, xbean related stuff will be lost in geronimo mailing lists ... I don't have a strong opinion, but I thought it would be easier for both developers and users. -- Cheers, Guillaume Nodet On 8/1/06, Alan D. Cabrera [EMAIL PROTECTED] wrote: Guillaume Nodet wrote: While looking at http://issues.apache.org/jira/browse/XBEAN-28, I was wondering if we should ask for xbean specific mailing lists. [EMAIL PROTECTED] [EMAIL PROTECTED] I don't see enough traffic about xbean to warrant a new list. Just my 2 cents. Regards, Alan
