Nabble - XBean

[jira] Assigned: (XBEAN-141) NumberFormatException upon installing the shaded subprojects - asm and finder - into Apache Felix 2.0.0

2009-10-12T08:23:31Z

[ https://issues.apache.org/jira/browse/XBEAN-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacek Laskowski reassigned XBEAN-141:
-------------------------------------

Assignee: Jacek Laskowski

> NumberFormatException upon installing the shaded subprojects - asm and finder - into Apache Felix 2.0.0
> -------------------------------------------------------------------------------------------------------
>
> Key: XBEAN-141
> URL: https://issues.apache.org/jira/browse/XBEAN-141
> Project: XBean
> Issue Type: Bug
> Components: reflect
> Affects Versions: 3.6
> Reporter: Jacek Laskowski
> Assignee: Jacek Laskowski
> Fix For: 3.7
>
>
> The header Bundle-Version is set to 3.7-SNAPSHOT and it's done manually in pom.xml while shading. It should be 3.7.0.SNAPSHOT as maven-bundle-plugin does for the other subprojects.
> jlaskowski@work /cygdrive/c/apps/felix-framework
> $ java -jar bin/felix.jar
> Welcome to Felix
> ================
> -> version
> 2.0.0
> -> install file:/C:\.m2\org\apache\xbean\xbean-asm-shaded\3.7-SNAPSHOT\xbean-asm-shaded-3.7-SNAPSHOT.jar
> java.lang.NumberFormatException: For input string: "7-SNAPSHOT"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> at java.lang.Integer.parseInt(Integer.java:458)
> at java.lang.Integer.parseInt(Integer.java:499)
> at org.osgi.framework.Version.<init>(Version.java:129)
> at org.osgi.framework.Version.parseVersion(Version.java:218)
> at org.apache.felix.framework.util.manifestparser.ManifestParser.<init>(ManifestParser.java:77)
> at org.apache.felix.framework.ModuleImpl.<init>(ModuleImpl.java:200)
> at org.apache.felix.framework.BundleImpl.createModule(BundleImpl.java:1095)
> at org.apache.felix.framework.BundleImpl.<init>(BundleImpl.java:82)
> at org.apache.felix.framework.Felix.installBundle(Felix.java:2379)
> at org.apache.felix.framework.Felix.installBundle(Felix.java:2282)
> at org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:130)
> at org.apache.felix.shell.impl.InstallCommandImpl.install(InstallCommandImpl.java:104)
> at org.apache.felix.shell.impl.InstallCommandImpl.execute(InstallCommandImpl.java:68)
> at org.apache.felix.shell.impl.Activator$ShellServiceImpl.executeCommand(Activator.java:281)
> at org.apache.felix.shell.tui.Activator$ShellTuiRunnable.run(Activator.java:184)
> at java.lang.Thread.run(Thread.java:619)
> java.lang.NumberFormatException: For input string: "7-SNAPSHOT"

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: xbean-dev

[jira] Closed: (XBEAN-141) NumberFormatException upon installing the shaded subprojects - asm and finder - into Apache Felix 2.0.0

2009-10-12T08:23:31Z

[ https://issues.apache.org/jira/browse/XBEAN-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacek Laskowski closed XBEAN-141.
---------------------------------

Resolution: Fixed

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] ------------------------------------------------------------------------
[INFO] Apache XBean .......................................... SUCCESS [23.907s]
[INFO] Apache XBean :: Spring ................................ SUCCESS [39.765s]
[INFO] Apache XBean :: Maven Plugin .......................... SUCCESS [32.031s]
[INFO] Apache XBean :: Classloader ........................... SUCCESS [5.110s]
[INFO] Apache XBean :: ClassPath ............................. SUCCESS [2.000s]
[INFO] Apache XBean :: Classpath Resource Finder ............. SUCCESS [8.187s]
[INFO] Apache XBean :: Naming ................................ SUCCESS [3.766s]
[INFO] Apache XBean :: ASM shaded (repackaged) ............... SUCCESS [2.406s]
[INFO] Apache XBean :: Reflect ............................... SUCCESS [11.203s]
[INFO] Apache XBean :: Telnet ................................ SUCCESS [40.391s]
[INFO] Apache XBean :: Finder shaded (repackaged) ............ SUCCESS [0.687s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 minutes 51 seconds
[INFO] Finished at: Mon Oct 12 17:19:57 CEST 2009
[INFO] Final Memory: 94M/254M
[INFO] ------------------------------------------------------------------------

jlaskowski@work /cygdrive/c/oss/xbean
$ svn status
M xbean-finder-shaded/pom.xml
M xbean-asm-shaded/pom.xml

jlaskowski@work /cygdrive/c/oss/xbean
$ svn ci -m 'XBEAN-141 NumberFormatException upon installing the shaded subprojects - asm and reflect - into Apache Felix 2.0.0' .
Sending xbean-asm-shaded/pom.xml
Sending xbean-finder-shaded/pom.xml
Transmitting file data ..
Committed revision 824381.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: xbean-dev

[jira] Updated: (XBEAN-141) NumberFormatException upon installing the shaded subprojects - asm and finder - into Apache Felix 2.0.0

2009-10-12T03:53:31Z

[ https://issues.apache.org/jira/browse/XBEAN-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacek Laskowski updated XBEAN-141:
----------------------------------

Summary: NumberFormatException upon installing the shaded subprojects - asm and finder - into Apache Felix 2.0.0 (was: NumberFormatException upon installing the shaded subprojects - asm and reflect - into Apache Felix 2.0.0)

finder not reflect

> NumberFormatException upon installing the shaded subprojects - asm and finder - into Apache Felix 2.0.0
> -------------------------------------------------------------------------------------------------------
>
> Key: XBEAN-141
> URL: https://issues.apache.org/jira/browse/XBEAN-141
> Project: XBean
> Issue Type: Bug
> Components: reflect
> Affects Versions: 3.6
> Reporter: Jacek Laskowski
> Fix For: 3.7
>
>
> The header Bundle-Version is set to 3.7-SNAPSHOT and it's done manually in pom.xml while shading. It should be 3.7.0.SNAPSHOT as maven-bundle-plugin does for the other subprojects.
> jlaskowski@work /cygdrive/c/apps/felix-framework
> $ java -jar bin/felix.jar
> Welcome to Felix
> ================
> -> version
> 2.0.0
> -> install file:/C:\.m2\org\apache\xbean\xbean-asm-shaded\3.7-SNAPSHOT\xbean-asm-shaded-3.7-SNAPSHOT.jar
> java.lang.NumberFormatException: For input string: "7-SNAPSHOT"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
> at java.lang.Integer.parseInt(Integer.java:458)
> at java.lang.Integer.parseInt(Integer.java:499)
> at org.osgi.framework.Version.<init>(Version.java:129)
> at org.osgi.framework.Version.parseVersion(Version.java:218)
> at org.apache.felix.framework.util.manifestparser.ManifestParser.<init>(ManifestParser.java:77)
> at org.apache.felix.framework.ModuleImpl.<init>(ModuleImpl.java:200)
> at org.apache.felix.framework.BundleImpl.createModule(BundleImpl.java:1095)
> at org.apache.felix.framework.BundleImpl.<init>(BundleImpl.java:82)
> at org.apache.felix.framework.Felix.installBundle(Felix.java:2379)
> at org.apache.felix.framework.Felix.installBundle(Felix.java:2282)
> at org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:130)
> at org.apache.felix.shell.impl.InstallCommandImpl.install(InstallCommandImpl.java:104)
> at org.apache.felix.shell.impl.InstallCommandImpl.execute(InstallCommandImpl.java:68)
> at org.apache.felix.shell.impl.Activator$ShellServiceImpl.executeCommand(Activator.java:281)
> at org.apache.felix.shell.tui.Activator$ShellTuiRunnable.run(Activator.java:184)
> at java.lang.Thread.run(Thread.java:619)
> java.lang.NumberFormatException: For input string: "7-SNAPSHOT"

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: xbean-dev

[jira] Created: (XBEAN-141) NumberFormatException upon installing the shaded subprojects - asm and reflect - into Apache Felix 2.0.0

2009-10-12T03:35:31Z

NumberFormatException upon installing the shaded subprojects - asm and reflect - into Apache Felix 2.0.0
--------------------------------------------------------------------------------------------------------

Key: XBEAN-141
URL: https://issues.apache.org/jira/browse/XBEAN-141
Project: XBean
Issue Type: Bug
Components: reflect
Affects Versions: 3.6
Reporter: Jacek Laskowski
Fix For: 3.7

The header Bundle-Version is set to 3.7-SNAPSHOT and it's done manually in pom.xml while shading. It should be 3.7.0.SNAPSHOT as maven-bundle-plugin does for the other subprojects.

jlaskowski@work /cygdrive/c/apps/felix-framework
$ java -jar bin/felix.jar

Welcome to Felix
================

-> version
2.0.0
-> install file:/C:\.m2\org\apache\xbean\xbean-asm-shaded\3.7-SNAPSHOT\xbean-asm-shaded-3.7-SNAPSHOT.jar
java.lang.NumberFormatException: For input string: "7-SNAPSHOT"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:458)
at java.lang.Integer.parseInt(Integer.java:499)
at org.osgi.framework.Version.<init>(Version.java:129)
at org.osgi.framework.Version.parseVersion(Version.java:218)
at org.apache.felix.framework.util.manifestparser.ManifestParser.<init>(ManifestParser.java:77)
at org.apache.felix.framework.ModuleImpl.<init>(ModuleImpl.java:200)
at org.apache.felix.framework.BundleImpl.createModule(BundleImpl.java:1095)
at org.apache.felix.framework.BundleImpl.<init>(BundleImpl.java:82)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2379)
at org.apache.felix.framework.Felix.installBundle(Felix.java:2282)
at org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:130)
at org.apache.felix.shell.impl.InstallCommandImpl.install(InstallCommandImpl.java:104)
at org.apache.felix.shell.impl.InstallCommandImpl.execute(InstallCommandImpl.java:68)
at org.apache.felix.shell.impl.Activator$ShellServiceImpl.executeCommand(Activator.java:281)
at org.apache.felix.shell.tui.Activator$ShellTuiRunnable.run(Activator.java:184)
at java.lang.Thread.run(Thread.java:619)
java.lang.NumberFormatException: For input string: "7-SNAPSHOT"

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: xbean-dev

[jira] Closed: (XBEAN-140) ClassFinder needs better processing of creating list of classes from JARs

2009-10-09T00:09:31Z

[ https://issues.apache.org/jira/browse/XBEAN-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vamsavardhana Reddy closed XBEAN-140.
-------------------------------------

Resolution: Duplicate

Duplicate of XBEAN-126.

> ClassFinder needs better processing of creating list of classes from JARs
> -------------------------------------------------------------------------
>
> Key: XBEAN-140
> URL: https://issues.apache.org/jira/browse/XBEAN-140
> Project: XBean
> Issue Type: Bug
> Components: finder
> Affects Versions: 3.5
> Reporter: Vamsavardhana Reddy
>
> I am using the ClassFinder with Geronimo code. One of the JARs that needed to be processed in my case is com\sun\xml\bind\jaxb-xjc\2.0.5\jaxb-xjc-2.0.5.jar. This jar contains a directory named 1.0 with some classes in it. When ClassFinder is processes this JAR, it is constructing class names like "1.0.com.sun.codemodel.CodeWriter" etc which are not valid class names and can't be located in the jar at "/1/0/com/sun/codemodel/CodeWriter.class" (but is present at "/1.0/com/sun/codemodel/CodeWriter.class"). This is resulting in stack traces like the following:
> java.lang.Exception: Could not load 1/0/com/sun/codemodel/CodeWriter.class
> at org.apache.xbean.finder.ClassFinder.readClassDef(ClassFinder.java:726)
> at org.apache.xbean.finder.ClassFinder.<init>(ClassFinder.java:141)
> at org.apache.xbean.finder.ClassFinder.<init>(ClassFinder.java:97)
> at org.apache.xbean.finder.ClassFinder.<init>(ClassFinder.java:86)
> at org.apache.openejb.config.AnnotationDeployer$DiscoverAnnotatedBeans.deploy(AnnotationDeployer.java:269)
> at org.apache.openejb.config.AnnotationDeployer$DiscoverAnnotatedBeans.deploy(AnnotationDeployer.java:247)
> at org.apache.openejb.config.AnnotationDeployer.deploy(AnnotationDeployer.java:167)
> at org.apache.tuscany.sca.contribution.jee.JavaEEModuleHelper.getMetadataCompleteModules(JavaEEModuleHelper.java:116)
> at org.apache.tuscany.sca.contribution.jee.impl.JavaEEIntrospectorImpl.introspectWebArchive(JavaEEIntrospectorImpl.java:80)
> at org.apache.tuscany.sca.contribution.jee.impl.WebArchiveProcessor.read(WebArchiveProcessor.java:46)
> at org.apache.tuscany.sca.contribution.jee.impl.WebArchiveProcessor.read(WebArchiveProcessor.java:1)
> at org.apache.tuscany.sca.contribution.processor.DefaultURLArtifactProcessorExtensionPoint$LazyURLArtifactProcessor.read(DefaultURLArtifactProcessorExtensionPoint.java:222)
> at org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtifactProcessor.read(ExtensibleURLArtifactProcessor.java:96)
> at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processReadPhase(ContributionServiceImpl.java:541)
> at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:419)
> at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:198)
> at org.apache.geronimo.tuscany.EmbeddedRuntimeGBean.doStart(EmbeddedRuntimeGBean.java:90)
> ...
> I guess there will also be problems when a directory inside the jar has a dot in its name. It is better to eliminate invalid class names while creating the list of classes.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: xbean-dev

[jira] Commented: (XBEAN-140) ClassFinder needs better processing of creating list of classes from JARs

2009-10-08T09:40:31Z

[ https://issues.apache.org/jira/browse/XBEAN-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763553#action_12763553 ]

David Jencks commented on XBEAN-140:
------------------------------------

Isn't this a duplicate of XBEAN-126, fixed in 3.6?

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: xbean-dev

[jira] Created: (XBEAN-140) ClassFinder needs better processing of creating list of classes from JARs

2009-10-07T23:35:31Z

ClassFinder needs better processing of creating list of classes from JARs
-------------------------------------------------------------------------

Key: XBEAN-140
URL: https://issues.apache.org/jira/browse/XBEAN-140
Project: XBean
Issue Type: Bug
Components: finder
Affects Versions: 3.5
Reporter: Vamsavardhana Reddy

I am using the ClassFinder with Geronimo code. One of the JARs that needed to be processed in my case is com\sun\xml\bind\jaxb-xjc\2.0.5\jaxb-xjc-2.0.5.jar. This jar contains a directory named 1.0 with some classes in it. When ClassFinder is processes this JAR, it is constructing class names like "1.0.com.sun.codemodel.CodeWriter" etc which are not valid class names and can't be located in the jar at "/1/0/com/sun/codemodel/CodeWriter.class" (but is present at "/1.0/com/sun/codemodel/CodeWriter.class"). This is resulting in stack traces like the following:

java.lang.Exception: Could not load 1/0/com/sun/codemodel/CodeWriter.class
at org.apache.xbean.finder.ClassFinder.readClassDef(ClassFinder.java:726)
at org.apache.xbean.finder.ClassFinder.<init>(ClassFinder.java:141)
at org.apache.xbean.finder.ClassFinder.<init>(ClassFinder.java:97)
at org.apache.xbean.finder.ClassFinder.<init>(ClassFinder.java:86)
at org.apache.openejb.config.AnnotationDeployer$DiscoverAnnotatedBeans.deploy(AnnotationDeployer.java:269)
at org.apache.openejb.config.AnnotationDeployer$DiscoverAnnotatedBeans.deploy(AnnotationDeployer.java:247)
at org.apache.openejb.config.AnnotationDeployer.deploy(AnnotationDeployer.java:167)
at org.apache.tuscany.sca.contribution.jee.JavaEEModuleHelper.getMetadataCompleteModules(JavaEEModuleHelper.java:116)
at org.apache.tuscany.sca.contribution.jee.impl.JavaEEIntrospectorImpl.introspectWebArchive(JavaEEIntrospectorImpl.java:80)
at org.apache.tuscany.sca.contribution.jee.impl.WebArchiveProcessor.read(WebArchiveProcessor.java:46)
at org.apache.tuscany.sca.contribution.jee.impl.WebArchiveProcessor.read(WebArchiveProcessor.java:1)
at org.apache.tuscany.sca.contribution.processor.DefaultURLArtifactProcessorExtensionPoint$LazyURLArtifactProcessor.read(DefaultURLArtifactProcessorExtensionPoint.java:222)
at org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtifactProcessor.read(ExtensibleURLArtifactProcessor.java:96)
at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processReadPhase(ContributionServiceImpl.java:541)
at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:419)
at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:198)
at org.apache.geronimo.tuscany.EmbeddedRuntimeGBean.doStart(EmbeddedRuntimeGBean.java:90)
...

I guess there will also be problems when a directory inside the jar has a dot in its name. It is better to eliminate invalid class names while creating the list of classes.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: xbean-dev

[jira] Closed: (XBEAN-109) org.apache.xbean.classloader.JarFileClassLoader can not handle pathnames with containing spaces

2009-09-22T08:50:16Z

[ https://issues.apache.org/jira/browse/XBEAN-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed XBEAN-109.
------------------------------

Resolution: Fixed
Fix Version/s: 3.6

I think we are just closing issues once they are fixed. Ideally we would make the jira options the same as the geronimo ones.

> org.apache.xbean.classloader.JarFileClassLoader can not handle pathnames with containing spaces
> ------------------------------------------------------------------------------------------------
>
> Key: XBEAN-109
> URL: https://issues.apache.org/jira/browse/XBEAN-109
> Project: XBean
> Issue Type: Bug
> Components: classloader
> Environment: jdk1.6, Windows 2000 Latest version from SVN
> Reporter: Ingo Bormann
> Assignee: Ivan
> Fix For: 3.6
>
> Attachments: xbean.diff
>
>
> A lot of classes in the package org.apache.xbean.classloader use File.toURL() instead of File.toURI().toURL(). File.toURL() is deprecated and does not work on windows with pathnames containing spaces. If a pathname contains spaces then File.toURL() does not convert spaces correctly. Javadoc recommends to use File.toURI().toURL() instead.
> I have a patched version where this is fixed for the full package org.apache.xbean.classloader.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: xbean-dev

Re: [VOTE] xbean 3.6 3rd try

2009-09-22T02:14:04Z

David,
Thanks for this release - looks like
http://issues.apache.org/jira/browse/XBEAN-109
was also committed @ revision 776705 but not marked as closed in Jira - so 14 issues.

Regards,
Matthias

djencks wrote:

I've prepared a 3rd release candidate for xbean 3.6:

https://repository.apache.org/content/repositories/geronimo-staging-007/

Site staged at:

http://people.apache.org/~djencks/staging-site/maven/xbean/3.6/

It looks like we fixed 13 issues for 3.6:

https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310312&fixfor=12313981

Please vote:

[ ] +1 release this
[ ] 0 dunno
[ ] -1 Don't release this

Vote will remain open 72 hours.

Many thanks
david jencks

From forum: xbean-dev

Re: [VOTE] xbean 3.6 3rd try

2009-09-16T07:24:04Z

Oops. Just for completeness... Sent my vote to the wrong list...

On Sep 15, 2009, at 9:57 PM, Kevan Miller wrote:

> +1 given the updated checksums.
>
> --kevan
> On Sep 14, 2009, at 4:20 PM, Kevan Miller wrote:
>
>> Looks good, except the md5/sha1 checksum errors. I'm -1 until
>> they're fixed.
>>
>> --kevan
>> On Sep 11, 2009, at 7:07 PM, David Jencks wrote:
>>
>>> I've prepared a 3rd release candidate for xbean 3.6:
>>>
>>> https://repository.apache.org/content/repositories/geronimo-staging-007/
>>>
>>> Site staged at:
>>>
>>> http://people.apache.org/~djencks/staging-site/maven/xbean/3.6/
>>>
>>> It looks like we fixed 13 issues for 3.6:
>>>
>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310312&fixfor=12313981
>>>
>>> Please vote:
>>>
>>> [ ] +1 release this
>>> [ ] 0 dunno
>>> [ ] -1 Don't release this
>>>
>>> Vote will remain open 72 hours.
>>>
>>> Many thanks
>>> david jencks
>>
>

From forum: xbean-dev

[RESULT] [VOTE] xbean 3.6 3rd try

2009-09-15T23:42:41Z

Vote passes with 6 +1 (dblevins, gnodet, djencks, jbohn, and kmiller
(on the geronimo dev list) and no other votes.

I'll promote the staged artifacts and move the site over.

many thanks
david jencks

On Sep 11, 2009, at 4:07 PM, David Jencks wrote:

> I've prepared a 3rd release candidate for xbean 3.6:
>
> https://repository.apache.org/content/repositories/geronimo-staging-007/
>
> Site staged at:
>
> http://people.apache.org/~djencks/staging-site/maven/xbean/3.6/
>
> It looks like we fixed 13 issues for 3.6:
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310312&fixfor=12313981
>
> Please vote:
>
> [ ] +1 release this
> [ ] 0 dunno
> [ ] -1 Don't release this
>
> Vote will remain open 72 hours.
>
> Many thanks
> david jencks

From forum: xbean-dev

Re: [VOTE] xbean 3.6 3rd try

2009-09-15T18:52:46Z

+1

Joe

David Jencks wrote:

> I've prepared a 3rd release candidate for xbean 3.6:
>
> https://repository.apache.org/content/repositories/geronimo-staging-007/
>
> Site staged at:
>
> http://people.apache.org/~djencks/staging-site/maven/xbean/3.6/
>
> It looks like we fixed 13 issues for 3.6:
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310312&fixfor=12313981
>
>
> Please vote:
>
> [ ] +1 release this
> [ ] 0 dunno
> [ ] -1 Don't release this
>
> Vote will remain open 72 hours.
>
> Many thanks
> david jencks

From forum: xbean-dev

Re: [VOTE] xbean 3.6 3rd try

2009-09-15T17:47:51Z

David, I've verified that it was committed to trunk in May. We've set its
fix version to 3.6. Not sure we still have the chance to make it into 3.6...
Thanks a lot!

-Jack

On Tue, Sep 15, 2009 at 12:52 AM, David Jencks <david_jencks@...>wrote:

>
> On Sep 13, 2009, at 6:44 PM, Jack Cai wrote:
>
> Can we also include the fix for XBEAN-122? It fixes important problems in
>> the naming module.
>>
>
> According to JIRA this was committed back in march. Can you verify this
> and set the Fix version in the jira issue if appropriate?
>
> thanks
> david jencks
>
>
>
>> I thought that usually all the fixes will make into a new release. :-)
>>
>> -Jack
>>
>
>

From forum: xbean-dev

Re: [VOTE] xbean 3.6 3rd try

2009-09-15T16:27:36Z

+1
david jencks

On Sep 11, 2009, at 4:07 PM, David Jencks wrote:

From forum: xbean-dev

Re: [VOTE] xbean 3.6 3rd try

2009-09-14T13:20:29Z

Looks good, except the md5/sha1 checksum errors. I'm -1 until they're
fixed.

--kevan
On Sep 11, 2009, at 7:07 PM, David Jencks wrote:

From forum: xbean-dev

Re: [VOTE] xbean 3.6 3rd try

2009-09-14T09:52:55Z

On Sep 13, 2009, at 6:44 PM, Jack Cai wrote:

> Can we also include the fix for XBEAN-122? It fixes important
> problems in
> the naming module.

According to JIRA this was committed back in march. Can you verify
this and set the Fix version in the jira issue if appropriate?

thanks
david jencks

>
> I thought that usually all the fixes will make into a new release. :-)
>
> -Jack

From forum: xbean-dev

Re: [VOTE] xbean 3.6 3rd try

2009-09-13T18:44:46Z

Can we also include the fix for XBEAN-122? It fixes important problems in
the naming module.

I thought that usually all the fixes will make into a new release. :-)

-Jack

From forum: xbean-dev

Re: [VOTE] xbean 3.6 3rd try

2009-09-13T09:33:06Z

+1

On Saturday, September 12, 2009, David Jencks <david_jencks@...> wrote:

--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

From forum: xbean-dev

Re: [VOTE] xbean 3.6 3rd try

2009-09-12T19:52:57Z

+1

Extra special thanks, David.

-David

On Sep 11, 2009, at 4:07 PM, David Jencks wrote:

From forum: xbean-dev

[VOTE] xbean 3.6 3rd try

2009-09-11T16:07:24Z

I've prepared a 3rd release candidate for xbean 3.6:

https://repository.apache.org/content/repositories/geronimo-staging-007/

Site staged at:

http://people.apache.org/~djencks/staging-site/maven/xbean/3.6/

It looks like we fixed 13 issues for 3.6:

https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310312&fixfor=12313981

Please vote:

[ ] +1 release this
[ ] 0 dunno
[ ] -1 Don't release this

Vote will remain open 72 hours.

Many thanks
david jencks

From forum: xbean-dev

[jira] Closed: (XBEAN-138) List of complex type results in any with content ##other which is broken for activemq.xds

2009-09-11T16:03:57Z

[ https://issues.apache.org/jira/browse/XBEAN-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed XBEAN-138.
------------------------------

Resolution: Duplicate

Hiram filed and fixed this as XBEAN-139

> List of complex type results in any with content ##other which is broken for activemq.xds
> -----------------------------------------------------------------------------------------
>
> Key: XBEAN-138
> URL: https://issues.apache.org/jira/browse/XBEAN-138
> Project: XBean
> Issue Type: Bug
> Components: spring
> Affects Versions: 3.6
> Reporter: Gary Tully
>
> there is a problem with the auto generation of ActiveMQ configuration schema (activemq.xsd) and any content generated for a complexType containing a List and would like to have ActiveMQ 5.3 use 3.6.
> For example the generated content :
> <xs:element name='policyEntries' minOccurs='0' maxOccurs='1'>
> <xs:annotation>
> <xs:documentation><![CDATA[
> Sets the individual entries on the policy map
> ]]></xs:documentation>
> </xs:annotation>
> <xs:complexType>
> <xs:sequence minOccurs='0' maxOccurs='unbounded'><xs:any namespace='##other'/></xs:sequence>
> </xs:complexType>
> </xs:element>
> should be (without the namespace ##other qualifier on the content) :
> <xs:element name='policyEntries' minOccurs='0' maxOccurs='1'>
> <xs:annotation>
> <xs:documentation><![CDATA[
> Sets the individual entries on the policy map
> ]]></xs:documentation>
> </xs:annotation>
> <xs:complexType>
> <xs:sequence minOccurs='0' maxOccurs='unbounded'><xs:any minOccurs='0' maxOccurs='unbounded'/></xs:sequence>
> </xs:complexType>
> </xs:element>
> Such that a policyEntry from the same namespace is valid.
> This is generated from:
> /**
> * Sets the individual entries on the policy map
> *
> * @org.apache.xbean.ElementType class="org.apache.activemq.broker.region.policy.PolicyEntry"
> */
> public void setPolicyEntries(List entries) {
> @ http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/region/policy/PolicyMap.java?view=markup

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: xbean-dev

[CANCELLED] [VOTE] xbean 3.6 2nd try

2009-09-11T12:36:03Z

Gonna try again with the patch from hiram for xbean-spring.

thanks
david jencks

On Sep 10, 2009, at 4:35 PM, David Jencks wrote:

> I've prepared a 2nd release candidate for xbean 3.6:
>
> https://repository.apache.org/content/repositories/geronimo-staging-001/
>
> Site staged at:
>
> http://people.apache.org/~djencks/staging-site/maven/xbean/3.6/
>
> It looks like we fixed 12 issues for 3.6:
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310312&fixfor=12313981
>
> Please vote:
>
> [ ] +1 release this
> [ ] 0 dunno
> [ ] -1 Don't release this
>
> Vote will remain open 72 hours.
>
> Many thanks
> david jencks

From forum: xbean-dev

[jira] Commented: (XBEAN-139) XSD generation invalid: List fields declared as sequence of

2009-09-11T08:26:57Z

[ https://issues.apache.org/jira/browse/XBEAN-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754171#action_12754171 ]

Hiram Chirino commented on XBEAN-139:
-------------------------------------

Patch applied in rev 813877

> XSD generation invalid: List fields declared as sequence of <xs:any namespace='##other'/>
> -----------------------------------------------------------------------------------------
>
> Key: XBEAN-139
> URL: https://issues.apache.org/jira/browse/XBEAN-139
> Project: XBean
> Issue Type: Bug
> Components: spring
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 3.6
>
>
> The problem with declaring them as <xs:any namespace='##other'/> is that it may be valid to inject objects into the list which are declared in the name space of the generated xsd.
> see: http://www.nabble.com/-VOTE--xbean-3.6-2nd-try-td25401282s134.html

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: xbean-dev

[jira] Assigned: (XBEAN-139) XSD generation invalid: List fields declared as sequence of

2009-09-11T08:24:59Z

[ https://issues.apache.org/jira/browse/XBEAN-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino reassigned XBEAN-139:
-----------------------------------

Assignee: Hiram Chirino

> XSD generation invalid: List fields declared as sequence of <xs:any namespace='##other'/>
> -----------------------------------------------------------------------------------------
>
> Key: XBEAN-139
> URL: https://issues.apache.org/jira/browse/XBEAN-139
> Project: XBean
> Issue Type: Bug
> Components: spring
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
>
> The problem with declaring them as <xs:any namespace='##other'/> is that it may be valid to inject objects into the list which are declared in the name space of the generated xsd.
> see: http://www.nabble.com/-VOTE--xbean-3.6-2nd-try-td25401282s134.html

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: xbean-dev

[jira] Created: (XBEAN-139) XSD generation invalid: List fields declared as sequence of

2009-09-11T08:24:59Z

XSD generation invalid: List fields declared as sequence of <xs:any namespace='##other'/>
-----------------------------------------------------------------------------------------

Key: XBEAN-139
URL: https://issues.apache.org/jira/browse/XBEAN-139
Project: XBean
Issue Type: Bug
Components: spring
Reporter: Hiram Chirino

The problem with declaring them as <xs:any namespace='##other'/> is that it may be valid to inject objects into the list which are declared in the name space of the generated xsd.

see: http://www.nabble.com/-VOTE--xbean-3.6-2nd-try-td25401282s134.html

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: xbean-dev

Re: [VOTE] xbean 3.6 2nd try

2009-09-11T08:17:40Z

I just put one together. I'll open an issue and commit shortly.

On Fri, Sep 11, 2009 at 9:47 AM, Gary Tully <gary.tully@...> wrote:

> -1 if possible
>
> sorry that I did not catch this earlier.
>
> there is a problem with the auto generation of ActiveMQ configuration
> schema
> (activemq.xsd) and any content generated for a complexType containing a
> List
> and would like to have ActiveMQ 5.3 use 3.6.
>
> For example the generated content :
> <xs:element name='policyEntries' minOccurs='0' maxOccurs='1'>
> <xs:annotation>
> <xs:documentation><![CDATA[
> Sets the individual entries on the policy map
> ]]></xs:documentation>
> </xs:annotation>
> <xs:complexType>
> <xs:sequence minOccurs='0' maxOccurs='unbounded'><xs:any
> namespace='##other'/></xs:sequence>
> </xs:complexType>
> </xs:element>
>
> should be (without the namespace ##other qualifier on the content) :
>
> <xs:element name='policyEntries' minOccurs='0' maxOccurs='1'>
> <xs:annotation>
> <xs:documentation><![CDATA[
> Sets the individual entries on the policy map
> ]]></xs:documentation>
> </xs:annotation>
> <xs:complexType>
> <xs:sequence minOccurs='0' maxOccurs='unbounded'><xs:any
> minOccurs='0' maxOccurs='unbounded'/></xs:sequence>
> </xs:complexType>
> </xs:element>
>
> Such that a policyEntry from the same namespace is valid.
>
> This is generated from:
>
> /**
> * Sets the individual entries on the policy map
> *
> * @org.apache.xbean.ElementType
> class="org.apache.activemq.broker.region.policy.PolicyEntry"
> */
> public void setPolicyEntries(List entries) {
>
> @
>
> http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/region/policy/PolicyMap.java?view=markup
>
> This looks like a straight forward bug but I need to generate a test case
> and open a jira and hopefully produce a patch asap.
>
>
> --
> http://blog.garytully.com
>
> Open Source Integration
> http://fusesource.com
>

--
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://fusesource.com/

From forum: xbean-dev

[jira] Created: (XBEAN-138) List of complex type results in any with content ##other which is broken for activemq.xds

2009-09-11T07:00:57Z

List of complex type results in any with content ##other which is broken for activemq.xds
-----------------------------------------------------------------------------------------

Key: XBEAN-138
URL: https://issues.apache.org/jira/browse/XBEAN-138
Project: XBean
Issue Type: Bug
Components: spring
Affects Versions: 3.6
Reporter: Gary Tully

there is a problem with the auto generation of ActiveMQ configuration schema (activemq.xsd) and any content generated for a complexType containing a List and would like to have ActiveMQ 5.3 use 3.6.

For example the generated content :
<xs:element name='policyEntries' minOccurs='0' maxOccurs='1'>
<xs:annotation>
<xs:documentation><![CDATA[
Sets the individual entries on the policy map
]]></xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence minOccurs='0' maxOccurs='unbounded'><xs:any namespace='##other'/></xs:sequence>
</xs:complexType>
</xs:element>

should be (without the namespace ##other qualifier on the content) :

<xs:element name='policyEntries' minOccurs='0' maxOccurs='1'>
<xs:annotation>
<xs:documentation><![CDATA[
Sets the individual entries on the policy map
]]></xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence minOccurs='0' maxOccurs='unbounded'><xs:any minOccurs='0' maxOccurs='unbounded'/></xs:sequence>
</xs:complexType>
</xs:element>

Such that a policyEntry from the same namespace is valid.

This is generated from:

/**
* Sets the individual entries on the policy map
*
* @org.apache.xbean.ElementType class="org.apache.activemq.broker.region.policy.PolicyEntry"
*/
public void setPolicyEntries(List entries) {

@ http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/region/policy/PolicyMap.java?view=markup

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: xbean-dev

[VOTE] xbean 3.6 2nd try

2009-09-11T06:47:38Z

-1 if possible

sorry that I did not catch this earlier.

there is a problem with the auto generation of ActiveMQ configuration schema
(activemq.xsd) and any content generated for a complexType containing a List
and would like to have ActiveMQ 5.3 use 3.6.

For example the generated content :
<xs:element name='policyEntries' minOccurs='0' maxOccurs='1'>
<xs:annotation>
<xs:documentation><![CDATA[
Sets the individual entries on the policy map
]]></xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence minOccurs='0' maxOccurs='unbounded'><xs:any
namespace='##other'/></xs:sequence>
</xs:complexType>
</xs:element>

should be (without the namespace ##other qualifier on the content) :

<xs:element name='policyEntries' minOccurs='0' maxOccurs='1'>
<xs:annotation>
<xs:documentation><![CDATA[
Sets the individual entries on the policy map
]]></xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence minOccurs='0' maxOccurs='unbounded'><xs:any
minOccurs='0' maxOccurs='unbounded'/></xs:sequence>
</xs:complexType>
</xs:element>

Such that a policyEntry from the same namespace is valid.

This is generated from:

/**
* Sets the individual entries on the policy map
*
* @org.apache.xbean.ElementType
class="org.apache.activemq.broker.region.policy.PolicyEntry"
*/
public void setPolicyEntries(List entries) {

@
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/region/policy/PolicyMap.java?view=markup

This looks like a straight forward bug but I need to generate a test case
and open a jira and hopefully produce a patch asap.

--
http://blog.garytully.com

Open Source Integration
http://fusesource.com

From forum: xbean-dev

Re: [VOTE] xbean 3.6 2nd try

2009-09-11T01:06:20Z

+1

On Fri, Sep 11, 2009 at 01:35, David Jencks <david_jencks@...> wrote:

--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

From forum: xbean-dev

[VOTE] xbean 3.6 2nd try

2009-09-10T16:35:23Z

I've prepared a 2nd release candidate for xbean 3.6:

https://repository.apache.org/content/repositories/geronimo-staging-001/

Site staged at:

http://people.apache.org/~djencks/staging-site/maven/xbean/3.6/

It looks like we fixed 12 issues for 3.6:

https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310312&fixfor=12313981

Please vote:

[ ] +1 release this
[ ] 0 dunno
[ ] -1 Don't release this

Vote will remain open 72 hours.

Many thanks
david jencks

From forum: xbean-dev

[jira] Closed: (XBEAN-92) UrlSet excludePaths() method throws a nullpointer exception if the pathString argument is null

2009-09-10T14:40:57Z

[ https://issues.apache.org/jira/browse/XBEAN-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed XBEAN-92.
-----------------------------

Resolution: Fixed
Fix Version/s: (was: 3.5)
3.6

> UrlSet excludePaths() method throws a nullpointer exception if the pathString argument is null
> ----------------------------------------------------------------------------------------------
>
> Key: XBEAN-92
> URL: https://issues.apache.org/jira/browse/XBEAN-92
> Project: XBean
> Issue Type: Bug
> Components: finder
> Environment: IBM JDK 5
> Reporter: karan singh malhi
> Assignee: Shawn Jiang
> Priority: Blocker
> Fix For: 3.6
>
> Attachments: XBEAN-92.patch.txt
>
>
> With IBM JDK 5, when we try to get the system property java.endorsed.dirs, it returns null. This is a critical issue as it prevents OpenEjb from starting
> In UrlSet, the following method will lead to a NullPointerException:
> public UrlSet excludeJavaEndorsedDirs() throws MalformedURLException {
> return excludePaths(System.getProperty("java.endorsed.dirs"));
> }
> This is because the excludePaths() method assumes that the pathString argument is always non-null.
> public UrlSet excludePaths(String pathString) throws MalformedURLException {
> String[] paths = pathString.split(File.pathSeparator);
> UrlSet urlSet = this;
> for (String path : paths) {
> File file = new File(path);
> urlSet = urlSet.exclude(file);
> }
> return urlSet;
> }

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

From forum: xbean-dev

[CANCELLED] [VOTE] xbean 3.6

2009-09-10T14:39:00Z

I've decided to include the last minute fix for XBEAN-92

thanks
david jencks

On Sep 10, 2009, at 12:06 AM, David Jencks wrote:

> I've prepared a release candidate for xbean 3.6:
>
> https://repository.apache.org/content/repositories/geronimo-staging-053/
>
> Site staged at:
>
> http://people.apache.org/~djencks/staging-site/maven/xbean/3.6/
>
> It looks like we fixed 11 issues for 3.6:
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310312&fixfor=12313981
>
> Please vote:
>
> [ ] +1 release this
> [ ] 0 dunno
> [ ] -1 Don't release this
>
> Vote will remain open 72 hours.
>
> Many thanks
> david jencks

From forum: xbean-dev

Re: [VOTE] xbean 3.6

2009-09-10T10:17:29Z

+1 - looks good to me.

Joe

David Jencks wrote:

> I've prepared a release candidate for xbean 3.6:
>
> https://repository.apache.org/content/repositories/geronimo-staging-053/
>
> Site staged at:
>
> http://people.apache.org/~djencks/staging-site/maven/xbean/3.6/
>
> It looks like we fixed 11 issues for 3.6:
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&pid=12310312&fixfor=12313981
>
>
> Please vote:
>
> [ ] +1 release this
> [ ] 0 dunno
> [ ] -1 Don't release this
>
> Vote will remain open 72 hours.
>
> Many thanks
> david jencks
>

From forum: xbean-dev

Re: [VOTE] xbean 3.6

2009-09-10T09:42:44Z

+1

Source, build, and binaries look good.

--kevan

On Sep 10, 2009, at 3:06 AM, David Jencks wrote:

From forum: xbean-dev

Re: [VOTE] xbean 3.6

2009-09-10T02:56:29Z

+1

On Thu, Sep 10, 2009 at 09:06, David Jencks<david_jencks@...> wrote:

--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

From forum: xbean-dev