[JBoss JIRA] (DROOLS-567) Improve Examples
by Mark Proctor (JIRA)
[ https://issues.jboss.org/browse/DROOLS-567?page=com.atlassian.jira.plugin... ]
Mark Proctor commented on DROOLS-567:
-------------------------------------
Change back to use BufferedImage. Improve the synchronisation of paint(). Make pong, wumpus and invaders all share more code.
Update TextAdventure for lock handling, attacking and general improvements.
> Improve Examples
> ----------------
>
> Key: DROOLS-567
> URL: https://issues.jboss.org/browse/DROOLS-567
> Project: Drools
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Mark Proctor
> Assignee: Mark Proctor
>
> The examples did not work on Java8, related to the double buffer's use of VolatileImage
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (DROOLS-567) Improve Examples
by Mark Proctor (JIRA)
Mark Proctor created DROOLS-567:
-----------------------------------
Summary: Improve Examples
Key: DROOLS-567
URL: https://issues.jboss.org/browse/DROOLS-567
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Mark Proctor
Assignee: Mark Proctor
The examples did not work on Java8, related to the double buffer's use of VolatileImage
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (WFCORE-25) Windows PowerShell scripts in bin
by Harsha Ramesh (JIRA)
[ https://issues.jboss.org/browse/WFCORE-25?page=com.atlassian.jira.plugin.... ]
Harsha Ramesh commented on WFCORE-25:
-------------------------------------
Sure thing Brian. I submitted another patch that is required if one wishes to specify the JAVA_OPTS as an environment variable.
https://github.com/wildfly/wildfly-core/pull/58
If you need any help from my end with completing the other scripts, then please do let me know.
> Windows PowerShell scripts in bin
> ---------------------------------
>
> Key: WFCORE-25
> URL: https://issues.jboss.org/browse/WFCORE-25
> Project: WildFly Core
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Scripts
> Reporter: Brian Stansberry
> Assignee: Tomaz Cerar
> Fix For: 1.0.0.Alpha4
>
>
> Add .psh scripts that match the functionality of our .sh scripts. Leave the .bat scripts in their current limited-functionality form for people still on XP, but use PowerShell as the recommended Windows scripting language.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBSER-120) Can't add field to class as the Java Serialization says is compatible
by Jon Onstott (JIRA)
[ https://issues.jboss.org/browse/JBSER-120?page=com.atlassian.jira.plugin.... ]
Jon Onstott commented on JBSER-120:
-----------------------------------
Related stack overflow question: http://stackoverflow.com/questions/17099593/is-there-a-way-to-avoid-jboss...
> Can't add field to class as the Java Serialization says is compatible
> ---------------------------------------------------------------------
>
> Key: JBSER-120
> URL: https://issues.jboss.org/browse/JBSER-120
> Project: JBoss Serialization
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.3 GA
> Environment: WIndows 2003 server 64-bit
> Reporter: Tom Saulpaugh
> Assignee: Clebert Suconic
> Fix For: 1.1.0 Beta
>
>
> I traced through this in jboss-serialization and it appears to be a basic coding bug. Look at this code in StreamingClass.readStream(), which includes the exception being thrown:
> short numberofFields=inp.readShort();
> keyfields[slotIndex] = new short[numberofFields];
>
> ClassMetadataField fields[] = slots[slotIndex].getFields();
> if (numberofFields>fields.length)
> {
> throw new IOException("Current classpath has lesser fields on " + className + " than its original version");
> }
> for (short fieldIndex=0;fieldIndex<fields.length;fieldIndex++)
> {
> long hashfield = inp.readLong();
> ClassMetadataField fieldOnHash = slots[slotIndex].getField(hashfield);
> if (fieldOnHash==null)
> {
> throw new IOException ("Field hash " + fieldOnHash + " is not available on current classPath for class " + className);
> }
> keyfields[slotIndex][fieldIndex] = fieldOnHash.getOrder();
> }
> Note that there are numberOfFields fields on the serialized prior version of the object, while there are fields.length fields in the new version of the class being deserialized to. The code reads the serialized fields and looks up the correspondent fields on the new class by hash.
> However, note that it reads fields.length fields from the file instead of numberofFields fields!!!
> That is the problem. It reads a long from the file that is not even a hash code of a field and so can't find it in the hash array, whence the null.
> This really does mean that the latest version of JBoss serialization has a bug that causes it to fail to handle field additions on new versions of classes.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBSER-120) Can't add field to class as the Java Serialization says is compatible
by Jon Onstott (JIRA)
[ https://issues.jboss.org/browse/JBSER-120?page=com.atlassian.jira.plugin.... ]
Jon Onstott commented on JBSER-120:
-----------------------------------
This is a big issue for us; this means that we can't add fields to a class we're sending via an EJB call without having to update our MANY client projects with the new class file.
> Can't add field to class as the Java Serialization says is compatible
> ---------------------------------------------------------------------
>
> Key: JBSER-120
> URL: https://issues.jboss.org/browse/JBSER-120
> Project: JBoss Serialization
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.3 GA
> Environment: WIndows 2003 server 64-bit
> Reporter: Tom Saulpaugh
> Assignee: Clebert Suconic
> Fix For: 1.1.0 Beta
>
>
> I traced through this in jboss-serialization and it appears to be a basic coding bug. Look at this code in StreamingClass.readStream(), which includes the exception being thrown:
> short numberofFields=inp.readShort();
> keyfields[slotIndex] = new short[numberofFields];
>
> ClassMetadataField fields[] = slots[slotIndex].getFields();
> if (numberofFields>fields.length)
> {
> throw new IOException("Current classpath has lesser fields on " + className + " than its original version");
> }
> for (short fieldIndex=0;fieldIndex<fields.length;fieldIndex++)
> {
> long hashfield = inp.readLong();
> ClassMetadataField fieldOnHash = slots[slotIndex].getField(hashfield);
> if (fieldOnHash==null)
> {
> throw new IOException ("Field hash " + fieldOnHash + " is not available on current classPath for class " + className);
> }
> keyfields[slotIndex][fieldIndex] = fieldOnHash.getOrder();
> }
> Note that there are numberOfFields fields on the serialized prior version of the object, while there are fields.length fields in the new version of the class being deserialized to. The code reads the serialized fields and looks up the correspondent fields on the new class by hash.
> However, note that it reads fields.length fields from the file instead of numberofFields fields!!!
> That is the problem. It reads a long from the file that is not even a hash code of a field and so can't find it in the hash array, whence the null.
> This really does mean that the latest version of JBoss serialization has a bug that causes it to fail to handle field additions on new versions of classes.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (WFLY-3670) Flag modules to be loaded in a distinct classloader context
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-3670?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-3670:
-----------------------------------
Detecting absolute/relative paths might be problematic on Windows, and also might introduce obscure compat issues. Another option might be to add an "absolute-resource-root" item to that descriptor.
> Flag modules to be loaded in a distinct classloader context
> -----------------------------------------------------------
>
> Key: WFLY-3670
> URL: https://issues.jboss.org/browse/WFLY-3670
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Wolf-Dieter Fink
> Assignee: Jason Greene
>
> For some use-cases it will be helpful to have a module in a separate classloader (as copy) if it is used from different applications.
> An example is if the module includes classes which follow the singleton pattern but the singleton should be per application instead of instance wide.
> There are two possiblities to flag that
> - within the module.xml
> - within the module reference MAIFEST or jboss-deployment-structure.xml
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (WFCORE-30) Change startup script to read new logger code in 9.x
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-30?page=com.atlassian.jira.plugin.... ]
Brian Stansberry moved WFLY-3668 to WFCORE-30:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-30 (was: WFLY-3668)
Affects Version/s: (was: 9.0.0.Beta1)
Component/s: Scripts
(was: Scripts)
Fix Version/s: (was: 9.0.0.Beta1)
> Change startup script to read new logger code in 9.x
> ----------------------------------------------------
>
> Key: WFCORE-30
> URL: https://issues.jboss.org/browse/WFCORE-30
> Project: WildFly Core
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Scripts
> Environment: Linux
> Reporter: Jorge Solorzano
> Assignee: Tomaz Cerar
> Priority: Minor
> Original Estimate: 1 hour
> Time Spent: 10 minutes
> Remaining Estimate: 0 minutes
>
> The refactor of the wildfly-core includes changes in logger codes that affects the startup script to verify if the server is started.
> The code JBAS015874 changed to WFLYSRV0025.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months