[JBoss-dev] [ jboss-Bugs-561546 ] Scoped ear classloading not working
Bugs item #561546, was opened at 2002-05-28 07:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: Marius Kotsbak (mkotsbak) Assigned to: Scott M Stark (starksm) Summary: Scoped ear classloading not working Initial Comment: Bug 1: Steps to reproduce the bug (ejb 1.x-beans taken from the manual, but the problem is the same on 2.x): 1. Deploy test1.ear 2. Deploy test2.ear ( the order of 1,2 is important!) 3. It gives this error: 13:27:46,694 WARN [CMPFieldMetaData] ERROR : Nested Field does not have a get method because test2 has a bean-class with the same name, but with an extra field (year) that test1 does't have. It is deployed with the class of test1 even with the jboss-app.xml is present. 4. Remove both 5. Deploy test2.ear 6. Deploy test1.ear 7. The error above does not appear, because test1.ears bean-class is used, and since it incudes abstract accessor method of all fields (also year) both deploys. test1 and 2 are deployed on different jndi-names (else it complains). bug 2: * And I would say that it is a bug that jboss-app is needed at all in this case. Since the beans are deployed on different jndi-names there are no conflicts. Jboss should use the classes in the jar it is deploying while deploying an ejb-jar. (and if it doesn't find one, then go to other classloaders maybe, if someone like to place them outside). I can't see the current behavior as a feature. Marius K Boostcom -- Comment By: Scott M Stark (starksm) Date: 2002-05-29 00:15 Message: Logged In: YES user_id=175228 Scoping has been fixed in 3.0. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-561546 ] Scoped ear classloading not working
Bugs item #561546, was opened at 2002-05-28 16:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: Marius Kotsbak (mkotsbak) Assigned to: Scott M Stark (starksm) Summary: Scoped ear classloading not working Initial Comment: Bug 1: Steps to reproduce the bug (ejb 1.x-beans taken from the manual, but the problem is the same on 2.x): 1. Deploy test1.ear 2. Deploy test2.ear ( the order of 1,2 is important!) 3. It gives this error: 13:27:46,694 WARN [CMPFieldMetaData] ERROR : Nested Field does not have a get method because test2 has a bean-class with the same name, but with an extra field (year) that test1 does't have. It is deployed with the class of test1 even with the jboss-app.xml is present. 4. Remove both 5. Deploy test2.ear 6. Deploy test1.ear 7. The error above does not appear, because test1.ears bean-class is used, and since it incudes abstract accessor method of all fields (also year) both deploys. test1 and 2 are deployed on different jndi-names (else it complains). bug 2: * And I would say that it is a bug that jboss-app is needed at all in this case. Since the beans are deployed on different jndi-names there are no conflicts. Jboss should use the classes in the jar it is deploying while deploying an ejb-jar. (and if it doesn't find one, then go to other classloaders maybe, if someone like to place them outside). I can't see the current behavior as a feature. Marius K Boostcom -- Comment By: Scott M Stark (starksm) Date: 2002-05-29 09:15 Message: Logged In: YES user_id=175228 Scoping has been fixed in 3.0. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-561546 ] Scoped ear classloading not working
Bugs item #561546, was opened at 2002-05-28 16:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: Marius Kotsbak (mkotsbak) Assigned to: Scott M Stark (starksm) Summary: Scoped ear classloading not working Initial Comment: Bug 1: Steps to reproduce the bug (ejb 1.x-beans taken from the manual, but the problem is the same on 2.x): 1. Deploy test1.ear 2. Deploy test2.ear ( the order of 1,2 is important!) 3. It gives this error: 13:27:46,694 WARN [CMPFieldMetaData] ERROR : Nested Field does not have a get method because test2 has a bean-class with the same name, but with an extra field (year) that test1 does't have. It is deployed with the class of test1 even with the jboss-app.xml is present. 4. Remove both 5. Deploy test2.ear 6. Deploy test1.ear 7. The error above does not appear, because test1.ears bean-class is used, and since it incudes abstract accessor method of all fields (also year) both deploys. test1 and 2 are deployed on different jndi-names (else it complains). bug 2: * And I would say that it is a bug that jboss-app is needed at all in this case. Since the beans are deployed on different jndi-names there are no conflicts. Jboss should use the classes in the jar it is deploying while deploying an ejb-jar. (and if it doesn't find one, then go to other classloaders maybe, if someone like to place them outside). I can't see the current behavior as a feature. Marius K Boostcom -- Comment By: Scott M Stark (starksm) Date: 2002-05-29 09:15 Message: Logged In: YES user_id=175228 Scoping has been fixed in 3.0. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-561546 ] Scoped ear classloading not working
Bugs item #561546, was opened at 2002-05-28 16:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: Marius Kotsbak (mkotsbak) Assigned to: Scott M Stark (starksm) Summary: Scoped ear classloading not working Initial Comment: Bug 1: Steps to reproduce the bug (ejb 1.x-beans taken from the manual, but the problem is the same on 2.x): 1. Deploy test1.ear 2. Deploy test2.ear ( the order of 1,2 is important!) 3. It gives this error: 13:27:46,694 WARN [CMPFieldMetaData] ERROR : Nested Field does not have a get method because test2 has a bean-class with the same name, but with an extra field (year) that test1 does't have. It is deployed with the class of test1 even with the jboss-app.xml is present. 4. Remove both 5. Deploy test2.ear 6. Deploy test1.ear 7. The error above does not appear, because test1.ears bean-class is used, and since it incudes abstract accessor method of all fields (also year) both deploys. test1 and 2 are deployed on different jndi-names (else it complains). bug 2: * And I would say that it is a bug that jboss-app is needed at all in this case. Since the beans are deployed on different jndi-names there are no conflicts. Jboss should use the classes in the jar it is deploying while deploying an ejb-jar. (and if it doesn't find one, then go to other classloaders maybe, if someone like to place them outside). I can't see the current behavior as a feature. Marius K Boostcom -- Comment By: Marius Kotsbak (mkotsbak) Date: 2002-05-29 12:45 Message: Logged In: YES user_id=366650 Bug 1 if fixed :-) But IMO bug 2 exist: Steps: 1. deploy test1.jar (attached) 2. deploy test2.jar 3. Error: WARN [CMPFieldMetaData] ERROR : Nested Field does not have a get method Because the depolyer is using test1.jar's class instead of the class included in the jar it is depoying (test2)! Why can't it just check if the class is found inside the jar it is depoying before loading with a more global classloader. I hope I will get an explanation of this behavior, either if it is practically or technically impossible. I don't like ear-ing more than needed. -- Comment By: Scott M Stark (starksm) Date: 2002-05-29 09:15 Message: Logged In: YES user_id=175228 Scoping has been fixed in 3.0. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-561546 ] Scoped ear classloading not working
Bugs item #561546, was opened at 2002-05-28 16:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: Invalid Priority: 5 Submitted By: Marius Kotsbak (mkotsbak) Assigned to: Scott M Stark (starksm) Summary: Scoped ear classloading not working Initial Comment: Bug 1: Steps to reproduce the bug (ejb 1.x-beans taken from the manual, but the problem is the same on 2.x): 1. Deploy test1.ear 2. Deploy test2.ear ( the order of 1,2 is important!) 3. It gives this error: 13:27:46,694 WARN [CMPFieldMetaData] ERROR : Nested Field does not have a get method because test2 has a bean-class with the same name, but with an extra field (year) that test1 does't have. It is deployed with the class of test1 even with the jboss-app.xml is present. 4. Remove both 5. Deploy test2.ear 6. Deploy test1.ear 7. The error above does not appear, because test1.ears bean-class is used, and since it incudes abstract accessor method of all fields (also year) both deploys. test1 and 2 are deployed on different jndi-names (else it complains). bug 2: * And I would say that it is a bug that jboss-app is needed at all in this case. Since the beans are deployed on different jndi-names there are no conflicts. Jboss should use the classes in the jar it is deploying while deploying an ejb-jar. (and if it doesn't find one, then go to other classloaders maybe, if someone like to place them outside). I can't see the current behavior as a feature. Marius K Boostcom -- Comment By: Marius Kotsbak (mkotsbak) Date: 2002-05-29 12:45 Message: Logged In: YES user_id=366650 Bug 1 if fixed :-) But IMO bug 2 exist: Steps: 1. deploy test1.jar (attached) 2. deploy test2.jar 3. Error: WARN [CMPFieldMetaData] ERROR : Nested Field does not have a get method Because the depolyer is using test1.jar's class instead of the class included in the jar it is depoying (test2)! Why can't it just check if the class is found inside the jar it is depoying before loading with a more global classloader. I hope I will get an explanation of this behavior, either if it is practically or technically impossible. I don't like ear-ing more than needed. -- Comment By: Scott M Stark (starksm) Date: 2002-05-29 09:15 Message: Logged In: YES user_id=175228 Scoping has been fixed in 3.0. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-561546 ] Scoped ear classloading not working
Bugs item #561546, was opened at 2002-05-28 07:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: Marius Kotsbak (mkotsbak) Assigned to: Scott M Stark (starksm) Summary: Scoped ear classloading not working Initial Comment: Bug 1: Steps to reproduce the bug (ejb 1.x-beans taken from the manual, but the problem is the same on 2.x): 1. Deploy test1.ear 2. Deploy test2.ear ( the order of 1,2 is important!) 3. It gives this error: 13:27:46,694 WARN [CMPFieldMetaData] ERROR : Nested Field does not have a get method because test2 has a bean-class with the same name, but with an extra field (year) that test1 does't have. It is deployed with the class of test1 even with the jboss-app.xml is present. 4. Remove both 5. Deploy test2.ear 6. Deploy test1.ear 7. The error above does not appear, because test1.ears bean-class is used, and since it incudes abstract accessor method of all fields (also year) both deploys. test1 and 2 are deployed on different jndi-names (else it complains). bug 2: * And I would say that it is a bug that jboss-app is needed at all in this case. Since the beans are deployed on different jndi-names there are no conflicts. Jboss should use the classes in the jar it is deploying while deploying an ejb-jar. (and if it doesn't find one, then go to other classloaders maybe, if someone like to place them outside). I can't see the current behavior as a feature. Marius K Boostcom -- Comment By: Scott M Stark (starksm) Date: 2002-05-29 09:11 Message: Logged In: YES user_id=175228 We will not change this behavior for 3.0. If you need to deploy multiple version of the same classes you must use scoped ears. The point of flattening the class loader heirarchy was to allow for mbeans to interact with ejbs and visa-versa. Future versions may optionally detect conflicting classes and either fail the deployment or automatically generate a seperate scope. -- Comment By: Marius Kotsbak (mkotsbak) Date: 2002-05-29 03:45 Message: Logged In: YES user_id=366650 Bug 1 if fixed :-) But IMO bug 2 exist: Steps: 1. deploy test1.jar (attached) 2. deploy test2.jar 3. Error: WARN [CMPFieldMetaData] ERROR : Nested Field does not have a get method Because the depolyer is using test1.jar's class instead of the class included in the jar it is depoying (test2)! Why can't it just check if the class is found inside the jar it is depoying before loading with a more global classloader. I hope I will get an explanation of this behavior, either if it is practically or technically impossible. I don't like ear-ing more than needed. -- Comment By: Scott M Stark (starksm) Date: 2002-05-29 00:15 Message: Logged In: YES user_id=175228 Scoping has been fixed in 3.0. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-561546 ] Scoped ear classloading not working
Bugs item #561546, was opened at 2002-05-28 16:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Marius Kotsbak (mkotsbak) Assigned to: Nobody/Anonymous (nobody) Summary: Scoped ear classloading not working Initial Comment: Bug 1: Steps to reproduce the bug (ejb 1.x-beans taken from the manual, but the problem is the same on 2.x): 1. Deploy test1.ear 2. Deploy test2.ear ( the order of 1,2 is important!) 3. It gives this error: 13:27:46,694 WARN [CMPFieldMetaData] ERROR : Nested Field does not have a get method because test2 has a bean-class with the same name, but with an extra field (year) that test1 does't have. It is deployed with the class of test1 even with the jboss-app.xml is present. 4. Remove both 5. Deploy test2.ear 6. Deploy test1.ear 7. The error above does not appear, because test1.ears bean-class is used, and since it incudes abstract accessor method of all fields (also year) both deploys. test1 and 2 are deployed on different jndi-names (else it complains). bug 2: * And I would say that it is a bug that jboss-app is needed at all in this case. Since the beans are deployed on different jndi-names there are no conflicts. Jboss should use the classes in the jar it is deploying while deploying an ejb-jar. (and if it doesn't find one, then go to other classloaders maybe, if someone like to place them outside). I can't see the current behavior as a feature. Marius K Boostcom -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
