[Design the new POJO MicroContainer] - Re: UnwrapValueUnitTestCase.testCollectionUnwrap failure on
by scott.stark@jboss.org
It looks like whatever the issue is, its random as often the test passes, but when it fails its failing over confusing an enum as another type. In this case it was treated as an Integer:
| Caused by: java.lang.NumberFormatException: For input string: "ONE"
| at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
| at java.lang.Integer.parseInt(Integer.java:447)
| at java.lang.Integer.valueOf(Integer.java:526)
| at java.lang.Integer.decode(Integer.java:919)
| at org.jboss.util.propertyeditor.IntegerEditor.setAsText(IntegerEditor.java:42)
| at org.jboss.reflect.plugins.ValueConvertor.convertValue(ValueConvertor.java:139)
| at org.jboss.reflect.plugins.ValueConvertor.convertValue(ValueConvertor.java:90)
| at org.jboss.reflect.plugins.ValueConvertor.convertValue(ValueConvertor.java:75)
| at org.jboss.reflect.spi.PrimitiveInfo.convertValue(PrimitiveInfo.java:228)
| at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.convertValue(DefaultMetaValueFactory.java:1030)
| ... 33 more
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190632#4190632
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190632
17 years, 4 months
[Design of JBoss Remoting, Unified Invokers] - Re: Remoting 3: Secure Remote Classloading (JBREM-929)
by david.lloyd@jboss.com
"alesj" wrote : "david.lloyd(a)jboss.com" wrote :
| | (1) A Remote VFS scheme
| |
| Can you post some pseudo code on the subject,
| as I have no clue about remoting, but I know a thing or two on VFS. :-)
|
Basically it would work like this. On the client you'd have a deployable configuration for remote VFS. The configuration would accept a name for the remote VFS which would be used in the uri (e.g. "vfsremote://my-remote-vfs/the/path"), and would also be used as the group name for the VFS service (so that there could be more than one provider for the same remote VFS service within a cluster, for example).
Then for every provider of that VFS instance, there would be a Remoting service deployed which would handle the forwarded VFS calls.
One interesting aspect of this is that if a node uses a vfsremote that is actually located on the same node, then the usual call-by-reference optimization takes place; it should not be too much more expensive than a regular local access.
Make sense?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190617#4190617
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190617
17 years, 4 months
[Design the new POJO MicroContainer] - UnwrapValueUnitTestCase.testCollectionUnwrap failure on comm
by scott.stark@jboss.org
I set the testFailureIgnore to false since were tyring to get jboss-man to GA, and there is this odd failure showing up when running the mvn test phase, but not under eclipse:
| Caused by: java.lang.IllegalArgumentException: No enum const class org.jboss.test.metatype.values.factory.support.TestEnum.org.jboss.test.metatype.values.factory.support.TestGeneric@be32
| at java.lang.Enum.valueOf(Enum.java:196) at org.jboss.reflect.plugins.ValueConvertor.convertValue(ValueConvertor.java:130) at org.jboss.reflect.plugins.ValueConvertor.convertValue(ValueConvertor.java:90) at org.jboss.reflect.plugins.ValueConvertor.convertValue(ValueConvertor.
| java:75) at org.jboss.reflect.plugins.ClassInfoImpl.convertValue(ClassInfoImpl.ja
| va:481)
| at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.convertValue(DefaultMetaValueFactory.java:1029)
| ... 33 more
|
Something is munging together a class instance toString with the enum class and trying to treat that as an enum string. I'm looking into how.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190611#4190611
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190611
17 years, 4 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Doc issues WAS: 1.4.1.GA ready
by clebert.suconic@jboss.com
JBoss 1.4.1.GA will be part of JBoss5, hence we won't require any library substitutions.
Because of that.. I have changed README.html to something simple as:
anonymous wrote : JBoss Messaging Version 1.4.1.GA is a release made and tested exclusively for the JBoss 5.0.0.GA only and it should be part of the JBoss5 download bundle.
|
| For the full description of this release, see the JBoss Messaging project JIRA.
|
| Enjoy!
And there are other issues as well. For instance, The BindingManager on JBoss5 is now something much simpler where it just overrides properties.
The documentation is becoming a little complicated IMO. For instance on JBoss4 you need to replace libraries while on JBoss5 you don't as we are now part of the distribution. We are getting now things like If (JBoss4) do this ... else.. don't do anything.
The "examples" is another "example".... JBoss5 don't have the destinations created by default. so we need to change the howto on the documentation.
I guess we will need to differentiate the documentation between AS4 and AS5 as the operations is becoming fairly different now.
I guess it needs to be revisited/split as part of a bigger task.
Maybe making the JBossMessaging documentation part of JBoss5 documentation?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190598#4190598
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190598
17 years, 4 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: 1.4.1.GA ready
by anil.saldhana@jboss.com
"timfox" wrote : "anil.saldhana(a)jboss.com" wrote : What will make the messaging project more agile? I opened a critical security bug last week and I am still no where in sight of even a snapshot release here. :)
| |
|
| Well... AFAIK the critical security bugs were fixed in the branch within hours of you opening the report.
|
| The vast majority of the delay has been in waiting for resolution into the JCA issue which was causing the TCK to fail, which turned out to be not JBM's fault, but a misconfig in JCA on the app server.
|
| The failure to ensure that the JBM dependencies are the same as the AS dependencies was indeed our fault - but I'm sure Clebert will sort this out quickly.
One of the criteria for adoption of a project/product in a highly secure environment is the responsiveness of the implementers to security vulnerabilities and the speed with which patches are provided. So you succeeded in both.
I suggest we sort out build issues so that releases (deltas with security patches) happen faster. ;) Everyone should adopt the greatest messaging product on earth - JBoss Messaging. :)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190594#4190594
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190594
17 years, 4 months