[jboss-jira] [JBoss JIRA] Reopened: (EJBTHREE-436) partition name should not be part of the @clustered annotation

[Martin Welss (JIRA)]

     [ http://jira.jboss.com/jira/browse/EJBTHREE-436?page=all ]

Martin Welss reopened EJBTHREE-436:
-----------------------------------

             
Same problem: to stay in my example, 3 different xml's would be needed, each for one cluster and so it would still not be possible to deploy the same .ear on all clusters.

How would you distribute a clustered ejb3 example? You force me to setup a cluster with the same partition name as yours? 

What if my 3 colleagues in the next room want to deploy your example, too on their computers. Would we have to setup individual subnetworks so they can all run jboss cluster wkith the same partition name?
  

> partition name should not be part of the @clustered annotation
> --------------------------------------------------------------
>
>                 Key: EJBTHREE-436
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-436
>             Project: EJB 3.0
>          Issue Type: Feature Request
>          Components: Clustering
>    Affects Versions: EJB 3.0 RC4 - PFD
>            Reporter: Martin Welss
>         Assigned To: Bill Burke
>            Priority: Critical
>             Fix For: EJB 3.0 RC9 - FD
>
>
> Why is the partition name part of the ejb-clustering annotation?
> Suppose there are three clusters: one for integration, one for test, one for production and each has a distinct partition name. It would not be possible to 'move' an application from integration to test without changing the code!
> And because of the attributes default value, there is no way to say to the bean 'never mind the partition name, just run everywhere'

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira