11:38 p.m.
Decouple Transient "determine*" JNDI Logic from Object Model
------------------------------------------------------------
Key: JBMETA-68
URL: http://jira.jboss.com/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.CR1
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
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
11:43 p.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[ http://jira.jboss.com/jira/browse/JBMETA-68?page=all ]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
Attachment: jbmeta68.patch
Attached patch for work to jboss-metadata; must time this properly with a release so as
not to disrupt AS
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: http://jira.jboss.com/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.CR1
Attachments: jbmeta68.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
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
1:18 a.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[ http://jira.jboss.com/jira/browse/JBMETA-68?page=all ]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161933
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: http://jira.jboss.com/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.CR1
Attachments: jbmeta68.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
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
3:15 p.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[ http://jira.jboss.com/jira/browse/JBMETA-68?page=all ]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
Attachment: (was: jbmeta68.patch)
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: http://jira.jboss.com/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.CR1
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
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
3:17 p.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[ http://jira.jboss.com/jira/browse/JBMETA-68?page=all ]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
Attachment: jbmeta68.patch
Updated patch to include Carlo's forum comments
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: http://jira.jboss.com/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.CR1
Attachments: jbmeta68.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
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
5:03 p.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[ http://jira.jboss.com/jira/browse/JBMETA-68?page=all ]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
Attachment: (was: jbmeta68.patch)
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: http://jira.jboss.com/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.CR1
Attachments: jbmeta68.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
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
5:03 p.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[ http://jira.jboss.com/jira/browse/JBMETA-68?page=all ]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
Attachment: jbmeta68.patch
Updated patch
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: http://jira.jboss.com/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.CR1
Attachments: jbmeta68.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
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
5:13 p.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[ http://jira.jboss.com/jira/browse/JBMETA-68?page=all ]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
Attachment: jbmeta68-as_compilation_resolve.patch
Added patch to resolve compilation errors in AS due to metadata changes
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: http://jira.jboss.com/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.CR1
Attachments: jbmeta68-as_compilation_resolve.patch, jbmeta68.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
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
12:08 a.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[ http://jira.jboss.com/jira/browse/JBMETA-68?page=all ]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
Attachment: (was: jbmeta68.patch)
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: http://jira.jboss.com/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.CR1
Attachments: jbmeta68-as_compilation_resolve.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
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
11:13 a.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[ http://jira.jboss.com/jira/browse/JBMETA-68?page=all ]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
Attachment: jbmeta68-as.patch
Added updated patch for AS to use changes to jboss-metadata
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: http://jira.jboss.com/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.CR1
Attachments: jbmeta68-as.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
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
11:13 a.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[ http://jira.jboss.com/jira/browse/JBMETA-68?page=all ]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
Attachment: (was: jbmeta68-as_compilation_resolve.patch)
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: http://jira.jboss.com/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.CR1
Attachments: jbmeta68-as.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
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
3:49 p.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[ http://jira.jboss.com/jira/browse/JBMETA-68?page=all ]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
Attachment: (was: jbmeta68-as.patch)
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: http://jira.jboss.com/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.Beta28
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
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
3:51 p.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[ http://jira.jboss.com/jira/browse/JBMETA-68?page=all ]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
Attachment: jbmeta68-as.patch
Updated Patch for AS to use pending release of jboss-metadata Beta28
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: http://jira.jboss.com/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.Beta28
Attachments: jbmeta68-as.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
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
8:24 a.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[ http://jira.jboss.com/jira/browse/JBMETA-68?page=all ]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
Attachment: (was: jbmeta68-as.patch)
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: http://jira.jboss.com/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.Beta28
Attachments: jbmeta68-as.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
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
8:24 a.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[ http://jira.jboss.com/jira/browse/JBMETA-68?page=all ]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
Attachment: jbmeta68-as.patch
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: http://jira.jboss.com/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assigned To: Andrew Lee Rubinger
Priority: Critical
Fix For: 1.0.0.Beta28
Attachments: jbmeta68-as.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
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
5:51 a.m.
New subject: [JBoss JIRA] Assigned: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[
https://jira.jboss.org/jira/browse/JBMETA-68?page=com.atlassian.jira.plug...
]
Andrew Lee Rubinger reassigned JBMETA-68:
-----------------------------------------
Assignee: Scott M Stark (was: Andrew Lee Rubinger)
Please resolve as 1.0.0.Beta29
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: https://jira.jboss.org/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assignee: Scott M Stark
Priority: Critical
Fix For: 1.0.0.Beta28
Attachments: jbmeta68-as.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:10 a.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[
https://jira.jboss.org/jira/browse/JBMETA-68?page=com.atlassian.jira.plug...
]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
Attachment: jbmeta68-as.patch
Added final patch to AS for resolution
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: https://jira.jboss.org/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assignee: Scott M Stark
Priority: Critical
Fix For: 1.0.0.Beta28
Attachments: jbmeta68-as.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:10 a.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[
https://jira.jboss.org/jira/browse/JBMETA-68?page=com.atlassian.jira.plug...
]
Andrew Lee Rubinger updated JBMETA-68:
--------------------------------------
Attachment: (was: jbmeta68-as.patch)
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: https://jira.jboss.org/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assignee: Scott M Stark
Priority: Critical
Fix For: 1.0.0.Beta28
Attachments: jbmeta68-as.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:23 a.m.
New subject: [JBoss JIRA] Updated: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[
https://jira.jboss.org/jira/browse/JBMETA-68?page=com.atlassian.jira.plug...
]
Alexey Loubyansky updated JBMETA-68:
------------------------------------
Fix Version/s: 1.0.0.Beta29
(was: 1.0.0.Beta28)
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: https://jira.jboss.org/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assignee: Scott M Stark
Priority: Critical
Fix For: 1.0.0.Beta29
Attachments: jbmeta68-as.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:25 a.m.
New subject: [JBoss JIRA] Resolved: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[
https://jira.jboss.org/jira/browse/JBMETA-68?page=com.atlassian.jira.plug...
]
Alexey Loubyansky resolved JBMETA-68.
-------------------------------------
Resolution: Done
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: https://jira.jboss.org/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assignee: Scott M Stark
Priority: Critical
Fix For: 1.0.0.Beta29
Attachments: jbmeta68-as.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:21 a.m.
New subject: [JBoss JIRA] Commented: (JBMETA-68) Decouple Transient "determine*" JNDI Logic from Object Model
[
https://jira.jboss.org/jira/browse/JBMETA-68?page=com.atlassian.jira.plug...
]
Ales Justin commented on JBMETA-68:
-----------------------------------
ProxyFactoryHelper
was:
if (localBinding == null || localBinding.jndiBinding() != null ||
localBinding.jndiBinding().trim().length() == 0)
should be:
if (localBinding == null || (localBinding.jndiBinding() != null &&
localBinding.jndiBinding().trim().length() == 0))
Was introduces NPE when 2nd condition is false.
Decouple Transient "determine*" JNDI Logic from Object
Model
------------------------------------------------------------
Key: JBMETA-68
URL: https://jira.jboss.org/jira/browse/JBMETA-68
Project: JBoss Metadata
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Andrew Lee Rubinger
Assignee: Scott M Stark
Priority: Critical
Fix For: 1.0.0.Beta29
Attachments: jbmeta68-as.patch
Current "determineResolved*JndiName()" methods, with default logic, are mixing
concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
* Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and
children
* Remove ClassLoader from DeploymentSummary; this is transient anyway
* Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD
instance
* Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and
ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of
resolving JNDI Names.
* Implement the Resolveable* SPI Interfaces in Decorators
* Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from
the caller
* Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
* Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI
Binding Policies
* Update grammars accordingly
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5896
days inactive
5924
days old
20 comments
3 participants
participants (3)
-
Ales Justin (JIRA) -
Alexey Loubyansky (JIRA)
-
Andrew Lee Rubinger (JIRA)