You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Greg Woolsey (JIRA)" <ta...@jakarta.apache.org> on 2006/11/20 22:04:02 UTC

[jira] Created: (TAPESTRY-1154) Nightly 4.1.1 introduces dependency in ComponentMessagesSourceImpl

Nightly 4.1.1 introduces dependency in ComponentMessagesSourceImpl
------------------------------------------------------------------

                 Key: TAPESTRY-1154
                 URL: http://issues.apache.org/jira/browse/TAPESTRY-1154
             Project: Tapestry
          Issue Type: Bug
          Components: Core
    Affects Versions: 4.1.1
         Environment: Nightly tapestry-framework-4.1.1-20061120.191155-44.jar
            Reporter: Greg Woolsey


ComponentMessagesSourceImpl suddenly imports

import edu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap;

which is a new dependent library.  I thought 4.1.1 was bug fix only - is this really necessary?  We use Java 5, which has the heart of this concurrent package built into the JRE, so I'd rather the class not use the old (now deprecated) code.

If I have to, I could try to patch my own hivemodule.xml to redefine the service with a Java 5 compatible replacement class, but that's not good long-term, as it would need updating as the referenced class is modified over time, of course.

-- 
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-1154) Nightly 4.1.1 introduces dependency in ComponentMessagesSourceImpl

Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
    [ http://issues.apache.org/jira/browse/TAPESTRY-1154?page=comments#action_12451453 ] 
            
Jesse Kuhnert commented on TAPESTRY-1154:
-----------------------------------------

I think it's listed on the site ;)

http://tapestry.apache.org/mail-lists.html

> Nightly 4.1.1 introduces dependency in ComponentMessagesSourceImpl
> ------------------------------------------------------------------
>
>                 Key: TAPESTRY-1154
>                 URL: http://issues.apache.org/jira/browse/TAPESTRY-1154
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 4.1.1
>         Environment: Nightly tapestry-framework-4.1.1-20061120.191155-44.jar
>            Reporter: Greg Woolsey
>         Assigned To: Jesse Kuhnert
>
> ComponentMessagesSourceImpl suddenly imports
> import edu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap;
> which is a new dependent library.  I thought 4.1.1 was bug fix only - is this really necessary?  We use Java 5, which has the heart of this concurrent package built into the JRE, so I'd rather the class not use the old (now deprecated) code.
> If I have to, I could try to patch my own hivemodule.xml to redefine the service with a Java 5 compatible replacement class, but that's not good long-term, as it would need updating as the referenced class is modified over time, of course.

-- 
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-1154) Nightly 4.1.1 introduces dependency in ComponentMessagesSourceImpl

Posted by "Greg Woolsey (JIRA)" <ta...@jakarta.apache.org>.
    [ http://issues.apache.org/jira/browse/TAPESTRY-1154?page=comments#action_12451428 ] 
            
Greg Woolsey commented on TAPESTRY-1154:
----------------------------------------

I would suggest, since this is a change that may be mirrored elsewhere in the code, to use a HiveMind configuration for 

"concurrentMap" that returns an instance of ConcurrentHashMap.  Have the default use the 3rd party one, and document an override for implementations that want to use the Java 5 version.  We can then just have one entry in our hivemodule.xml that overrides the default, and don't have to copy and maintain a bunch of class/interface implementations.

This would work most places, unless there are classes that won't be created by HiveMind or have access to the HiveMind registry directly or indirectly.

Would that work for you?

> Nightly 4.1.1 introduces dependency in ComponentMessagesSourceImpl
> ------------------------------------------------------------------
>
>                 Key: TAPESTRY-1154
>                 URL: http://issues.apache.org/jira/browse/TAPESTRY-1154
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 4.1.1
>         Environment: Nightly tapestry-framework-4.1.1-20061120.191155-44.jar
>            Reporter: Greg Woolsey
>         Assigned To: Jesse Kuhnert
>
> ComponentMessagesSourceImpl suddenly imports
> import edu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap;
> which is a new dependent library.  I thought 4.1.1 was bug fix only - is this really necessary?  We use Java 5, which has the heart of this concurrent package built into the JRE, so I'd rather the class not use the old (now deprecated) code.
> If I have to, I could try to patch my own hivemodule.xml to redefine the service with a Java 5 compatible replacement class, but that's not good long-term, as it would need updating as the referenced class is modified over time, of course.

-- 
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Resolved: (TAPESTRY-1154) Nightly 4.1.1 introduces dependency in ComponentMessagesSourceImpl

Posted by "Jesse Kuhnert (JIRA)" <ta...@jakarta.apache.org>.
     [ http://issues.apache.org/jira/browse/TAPESTRY-1154?page=all ]

Jesse Kuhnert resolved TAPESTRY-1154.
-------------------------------------

    Resolution: Won't Fix
      Assignee: Jesse Kuhnert

I don't like it much either, but as I plan on doing a lot more plumbing work that will require this library I'm not sure what else to do. 

We have to maintain compatibility with older jre's, so if you know a way of doing that and being able to use the new 1.5 libraries then we might have a solution. 

> Nightly 4.1.1 introduces dependency in ComponentMessagesSourceImpl
> ------------------------------------------------------------------
>
>                 Key: TAPESTRY-1154
>                 URL: http://issues.apache.org/jira/browse/TAPESTRY-1154
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 4.1.1
>         Environment: Nightly tapestry-framework-4.1.1-20061120.191155-44.jar
>            Reporter: Greg Woolsey
>         Assigned To: Jesse Kuhnert
>
> ComponentMessagesSourceImpl suddenly imports
> import edu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap;
> which is a new dependent library.  I thought 4.1.1 was bug fix only - is this really necessary?  We use Java 5, which has the heart of this concurrent package built into the JRE, so I'd rather the class not use the old (now deprecated) code.
> If I have to, I could try to patch my own hivemodule.xml to redefine the service with a Java 5 compatible replacement class, but that's not good long-term, as it would need updating as the referenced class is modified over time, of course.

-- 
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


[jira] Commented: (TAPESTRY-1154) Nightly 4.1.1 introduces dependency in ComponentMessagesSourceImpl

Posted by "Greg Woolsey (JIRA)" <ta...@jakarta.apache.org>.
    [ http://issues.apache.org/jira/browse/TAPESTRY-1154?page=comments#action_12451440 ] 
            
Greg Woolsey commented on TAPESTRY-1154:
----------------------------------------

OK, I went and actually _looked_ at which concurrent package you were using here.  I didn't realize we could just use their Java 5 specific build, which just translates calls between this stable API and the java.util.concurrent classes.  I'm OK with adding that dependency for API consistency across VM versions.  I was just caught off guard by the added dependency in the nightly build.  Where can I find check in history or subscribe to a commit mailing list so I can keep on top of these things?

> Nightly 4.1.1 introduces dependency in ComponentMessagesSourceImpl
> ------------------------------------------------------------------
>
>                 Key: TAPESTRY-1154
>                 URL: http://issues.apache.org/jira/browse/TAPESTRY-1154
>             Project: Tapestry
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 4.1.1
>         Environment: Nightly tapestry-framework-4.1.1-20061120.191155-44.jar
>            Reporter: Greg Woolsey
>         Assigned To: Jesse Kuhnert
>
> ComponentMessagesSourceImpl suddenly imports
> import edu.emory.mathcs.backport.java.util.concurrent.ConcurrentHashMap;
> which is a new dependent library.  I thought 4.1.1 was bug fix only - is this really necessary?  We use Java 5, which has the heart of this concurrent package built into the JRE, so I'd rather the class not use the old (now deprecated) code.
> If I have to, I could try to patch my own hivemodule.xml to redefine the service with a Java 5 compatible replacement class, but that's not good long-term, as it would need updating as the referenced class is modified over time, of course.

-- 
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org