pococapsule - Project Hosting on Google Code

Last 30 days Dec 03, 2009 HowToBuildPocoCapsule (A brief guide on building/porting PocoCapsule.) Wiki page commented on by kjin101 - Installers downloadable from this site were built from 1.0 source code. We need rebuild them based on 1.1 source code. Installers downloadable from this site were built from 1.0 source code. We need rebuild them based on 1.1 source code. Nov 26, 2009 issue 8 (Xerces 3 support) commented on by kjin101 - message from Bryan Raney: I have sucessfully compiled PocoCapsule with Xerces 3 in Windows. I only had to make the following two changes: (1) In "src/xmlreader/Makefile", on line 17: updated version number of library (from "xerces-c_2" to "xerces-c_3") (2) In "src/xmlreader/xmlreader.h", removed line 42, which #includes a deprecated header file. The "DOMString" class was deprecated in Xerces API version 2, and finally removed in version 3, but luckily doesn't seem to be actually used in the PocoCapsule code! message from Bryan Raney: I have sucessfully compiled PocoCapsule with Xerces 3 in Windows. I only had to make the following two changes: (1) In "src/xmlreader/Makefile", on line 17: updated version number of library (from "xerces-c_2" to "xerces-c_3") (2) In "src/xmlreader/xmlreader.h", removed line 42, which #includes a deprecated header file. The "DOMString" class was deprecated in Xerces API version 2, and finally removed in version 3, but luckily doesn't seem to be actually used in the PocoCapsule code! Nov 26, 2009 issue 8 (Xerces 3 support) reported by kjin101 - need some porting effort. need some porting effort. Nov 19, 2009 HowToBuildPocoCapsule (A brief guide on building/porting PocoCapsule.) Wiki page commented on by braney - Will those installers work for version 1.1 of the source code? Will those installers work for version 1.1 of the source code? Earlier this year Nov 17, 2009 issue 5 (update the license statement in source code to LGPL) Status changed by kjin101 - Status: Fixed Status: Fixed Nov 17, 2009 issue 1 (src\table.C) Status changed by kjin101 - Status: Invalid Status: Invalid Nov 17, 2009 issue 3 (support private id) Status changed by kjin101 - Feature supported in 1.1 already Status: Fixed Feature supported in 1.1 already Status: Fixed Nov 16, 2009 issue 2 (pxgenproxy has misleading return code of 0 upon exception) Status changed by kjin101 - Already fixed in 1.1 Status: Fixed Already fixed in 1.1 Status: Fixed Nov 16, 2009 issue 5 (update the license statement in source code to LGPL) commented on by kjin101 - Source code with LGPL statement in source code files is now available for download in tar file. The SVN will also be updated later. Source code with LGPL statement in source code files is now available for download in tar file. The SVN will also be updated later. Nov 16, 2009 pococapsule-cpp-1.1-src.tar (Source code (1.1 with LGPL statement in source files)) file uploaded by kjin101 Nov 16, 2009 issue 5 (update the license statement in source code to LGPL) commented on by braney - This task is important to my group being allowed to use PocoCapsule with our software. The license indicated on the "Project Home" page is not relevant to our legal department -- only what is mentioned in the code itself! Thank you for your time and support. This task is important to my group being allowed to use PocoCapsule with our software. The license indicated on the "Project Home" page is not relevant to our legal department -- only what is mentioned in the code itself! Thank you for your time and support. Sep 23, 2009 Reflection_from_Projection (Reflection from Projection) Wiki page edited by kjin101 - Revision r226 Edited wiki page through web user interface. Revision r226 Edited wiki page through web user interface. Sep 16, 2009 issue 6 (support dynamic wiring by the IoC core engine) Summary changed by kjin101 - Summary: support dynamic wiring by the IoC core engine Summary: support dynamic wiring by the IoC core engine Sep 15, 2009 issue 6 (support dynamic wiring) Summary changed by kjin101 - Summary: support dynamic wiring Summary: support dynamic wiring Aug 24, 2009 XML_in_IoC_containers_A_Hell_or_A_Realm (XML in IoC containers: A Hell or A Realm?) Wiki page edited by kjin101 - Revision r225 Edited wiki page through web user interface. Revision r225 Edited wiki page through web user interface. Aug 17, 2009 XML_in_IoC_containers_A_Hell_or_A_Realm (XML in IoC containers: A Hell or A Realm?) Wiki page edited by kjin101 - Revision r224 Edited wiki page through web user interface. Revision r224 Edited wiki page through web user interface. Aug 17, 2009 XML_in_IoC_containers_A_Hell_or_A_Realm Wiki page edited by kjin101 - Revision r223 Edited wiki page through web user interface. Revision r223 Edited wiki page through web user interface. Aug 17, 2009 XML_in_IoC_containers_A_Hell_or_A_Realm Wiki page edited by kjin101 - Revision r222 Edited wiki page through web user interface. Revision r222 Edited wiki page through web user interface. Aug 17, 2009 XML_in_IoC_containers_A_Hell_or_A_Realm (One-sentence summary of this page.) Wiki page added by kjin101 - Revision r221 Created wiki page through web user interface. Revision r221 Created wiki page through web user interface. Jun 08, 2009 HowToBuildPocoCapsule (A brief guide on building/porting PocoCapsule.) Wiki page edited by kjin101 Mar 08, 2009 Type_Safety_of_PocoCapsule (Type safety in PocoCapsule.) Wiki page edited by kjin101 Mar 08, 2009 issue 7 (Add more documentation about <array type="namevalue">) commented on by kjin101 - forwarded to the pococapsule forum: http://groups.google.com/group/pococapsule/browse_thread/thread/9f48984e1fd097e4 forwarded to the pococapsule forum: http://groups.google.com/group/pococapsule/browse_thread/thread/9f48984e1fd097e4 Mar 08, 2009 issue 7 (Add more documentation about <array type="namevalue">) Labels changed by kjin101 - > The file "pococpp-iocdsm-dev-guide102.pdf" mentions that <array> can have > type "namevalue" but doesn't really say more than that about how to use it. > I know that <item> can have "name" and "value" attributes, but it is not > at all clear how my code is supposed to access that information. <array> of namevalue was largely introduced for PocoCapsule internal use (CORBA integration). However, its usage should be self-explained. Namely, it will pass the argument as two parameters. The first one (as in the case of other array types) is the count of the array. The second parameter is the array itself. The array element in this case is a struct with two 'const char' fields. By default, the struct type id is POCO_NameValue (defined in poco.h). User can override this definition with another struct with different type name, as long as it has the name and value fields. Without using this feature, the same feature (actually, support more generic name-value) can also be achieved using DSM (similart to how <map>, <list> are supported in pococapsule). Therefore, this feature wasn't documented in detail. > It would be nice if an example was included in the documentation that shows> > how to use an array of type="namevalue", and how PocoCapsule turns that > into invocation code. For example, I tried creating such an array, and was > surprised to see the proxy code referring to a type called > "POCO_NameValue", which never seemed to be mentioned in the documentation. POCO_NameValue is defined in poco.h. Labels: Type-Enhancement Priority-Low −Type-Defect −Priority-Medium > The file "pococpp-iocdsm-dev-guide102.pdf" mentions that <array> can have > type "namevalue" but doesn't really say more than that about how to use it. > I know that <item> can have "name" and "value" attributes, but it is not > at all clear how my code is supposed to access that information. <array> of namevalue was largely introduced for PocoCapsule internal use (CORBA integration). However, its usage should be self-explained. Namely, it will pass the argument as two parameters. The first one (as in the case of other array types) is the count of the array. The second parameter is the array itself. The array element in this case is a struct with two 'const char' fields. By default, the struct type id is POCO_NameValue (defined in poco.h). User can override this definition with another struct with different type name, as long as it has the name and value fields. Without using this feature, the same feature (actually, support more generic name-value) can also be achieved using DSM (similart to how <map>, <list> are supported in pococapsule). Therefore, this feature wasn't documented in detail. > It would be nice if an example was included in the documentation that shows> > how to use an array of type="namevalue", and how PocoCapsule turns that > into invocation code. For example, I tried creating such an array, and was > surprised to see the proxy code referring to a type called > "POCO_NameValue", which never seemed to be mentioned in the documentation. POCO_NameValue is defined in poco.h. Labels: Type-Enhancement Priority-Low −Type-Defect −Priority-Medium Mar 06, 2009 issue 7 (Add more documentation about <array type="namevalue">) reported by braney - This is a enhancement request for the Developer Guide documentation. The file "pococpp-iocdsm-dev-guide102.pdf" mentions that <array> can have type "namevalue" but doesn't really say more than that about how to use it. I know that <item> can have "name" and "value" attributes, but it is not at all clear how my code is supposed to access that information. It would be nice if an example was included in the documentation that shows how to use an array of type="namevalue", and how PocoCapsule turns that into invocation code. For example, I tried creating such an array, and was surprised to see the proxy code referring to a type called "POCO_NameValue", which never seemed to be mentioned in the documentation. If this issue would be better as a forum discussion, I will be happy to participate. This is a enhancement request for the Developer Guide documentation. The file "pococpp-iocdsm-dev-guide102.pdf" mentions that <array> can have type "namevalue" but doesn't really say more than that about how to use it. I know that <item> can have "name" and "value" attributes, but it is not at all clear how my code is supposed to access that information. It would be nice if an example was included in the documentation that shows how to use an array of type="namevalue", and how PocoCapsule turns that into invocation code. For example, I tried creating such an array, and was surprised to see the proxy code referring to a type called "POCO_NameValue", which never seemed to be mentioned in the documentation. If this issue would be better as a forum discussion, I will be happy to participate. Mar 04, 2009 issue 6 (support dynamic context) reported by kjin101 - dynamic context and service replacement are able to be supported through DSM in 1.0 release. However, having part of key mechanisms supported by the IoC core engine can simplify the DSM templates significantly. dynamic context and service replacement are able to be supported through DSM in 1.0 release. However, having part of key mechanisms supported by the IoC core engine can simplify the DSM templates significantly. Mar 04, 2009 issue 5 (update the license statement in source code to LGPL) reported by kjin101 - update the license statement in source code from GPL to LGPL update the license statement in source code from GPL to LGPL Mar 04, 2009 issue 4 (support factories return var and/or ref types) commented on by kjin101 - 1. vars should be supported using holders. 2. when used as factory-bean, factory method on smart pointer vars should be called through the -> operator defined on the smart pointer class. 3. when pass by "deref", "" operator defined on the var class should be used. 1. vars should be supported using holders. 2. when used as factory-bean, factory method on smart pointer vars should be called through the -> operator defined on the smart pointer class. 3. when pass by "deref", "" operator defined on the var class should be used. Mar 04, 2009 issue 3 (support private id) Labels changed by kjin101 - Labels: Type-Enhancement −Type-Defect Labels: Type-Enhancement −Type-Defect Mar 04, 2009 issue 4 (support factories return var and/or ref types) Labels changed by kjin101 - Labels: Type-Enhancement −Type-Defect Labels: Type-Enhancement −Type-Defect Mar 04, 2009 issue 4 (support factories return var and/or ref types) reported by kjin101 - see: http://groups.google.com/group/pococapsule/browse_thread/thread/5e31a5e3c619f35b see: http://groups.google.com/group/pococapsule/browse_thread/thread/5e31a5e3c619f35b Mar 04, 2009 issue 2 (pxgenproxy has misleading return code of 0 upon exception) Owner changed by kjin101 - Owner: kjin101 Owner: kjin101 Mar 04, 2009 issue 3 (support private id) reported by kjin101 - bean node should have a 'private' attribute (false\|true). by default, the value of this attribute is "false" (to be backward compatible). If this attribute is "true", the bean will be not retrievable using getBean() etc. methods on the application context. bean node should have a 'private' attribute (false\|true). by default, the value of this attribute is "false" (to be backward compatible). If this attribute is "true", the bean will be not retrievable using getBean() etc. methods on the application context. Feb 09, 2009 issue 2 (pxgenproxy has misleading return code of 0 upon exception) Status changed by kjin101 - Thanks for the bug report. We will try to fix it in next minor release. Status: Accepted Thanks for the bug report. We will try to fix it in next minor release. Status: Accepted Jan 22, 2009 issue 2 (pxgenproxy has misleading return code of 0 upon exception) reported by braney - When I run pxgenproxy (under Linux) and it has an exception (e.g. not finding a file), its return code is 0, which means success, and is incorrect. This incorrect return value causes "make" to keep going, even though the setup_reflx.cc file is empty. What steps will reproduce the problem? 1. Install from pococapsule-cpp-1.0-Linux-x86-Install. Set POCOCAPSULE_DIR to the appropriate location. 2. cd $POCOCAPSULE_DIR/examples/basic-ioc/robotic-vehicle 3. mv robotic-application2poco.xsl robotic-application2poco.xsl_ # (this step is just to cause the exception) 4. $POCOCAPSULE_DIR/bin/pxgenproxy -r=gather setup.xml # notice the exception 5. echo $? # shows value of 0 (You can also just run "make" at step 4 and watch it produce the exception and then continue past it.) What is the expected output? What do you see instead? I expect pxgenproxy to have a non-zero return code if it encounters an exception -- especially an exception from parsing the setup.xml file! This way, the make process can catch the error and stop. Instead, I see pxgenproxy returning a return code of zero, which in Linux means success. Make interprets that as "everything is OK" and continues on to compiling the (invalid) setup_reflx.cc file. What version of the product are you using? On what operating system? I guess version 1.0. I installed via the binary installer (pococapsule-cpp-1.0-Linux-x86-Install) under SUSE Linux Enterprise Server 10. Please provide any additional information below. I have successfully compiled all of the "basic-ioc" examples. The above steps are just to demonstrate the issue. This problem occurs when I start to modify things and try to apply it to my application. If I get "setup.xml" wrong or forget an .xsl file, pxgenproxy complains but make doesn't notice the problem, which is very inconvenient while still trying to figure out how to make everything work right. When I run pxgenproxy (under Linux) and it has an exception (e.g. not finding a file), its return code is 0, which means success, and is incorrect. This incorrect return value causes "make" to keep going, even though the setup_reflx.cc file is empty. What steps will reproduce the problem? 1. Install from pococapsule-cpp-1.0-Linux-x86-Install. Set POCOCAPSULE_DIR to the appropriate location. 2. cd $POCOCAPSULE_DIR/examples/basic-ioc/robotic-vehicle 3. mv robotic-application2poco.xsl robotic-application2poco.xsl_ # (this step is just to cause the exception) 4. $POCOCAPSULE_DIR/bin/pxgenproxy -r=gather setup.xml # notice the exception 5. echo $? # shows value of 0 (You can also just run "make" at step 4 and watch it produce the exception and then continue past it.) What is the expected output? What do you see instead? I expect pxgenproxy to have a non-zero return code if it encounters an exception -- especially an exception from parsing the setup.xml file! This way, the make process can catch the error and stop. Instead, I see pxgenproxy returning a return code of zero, which in Linux means success. Make interprets that as "everything is OK" and continues on to compiling the (invalid) setup_reflx.cc file. What version of the product are you using? On what operating system? I guess version 1.0. I installed via the binary installer (pococapsule-cpp-1.0-Linux-x86-Install) under SUSE Linux Enterprise Server 10. Please provide any additional information below. I have successfully compiled all of the "basic-ioc" examples. The above steps are just to demonstrate the issue. This problem occurs when I start to modify things and try to apply it to my application. If I get "setup.xml" wrong or forget an .xsl file, pxgenproxy complains but make doesn't notice the problem, which is very inconvenient while still trying to figure out how to make everything work right. Jan 15, 2009 Type_Safety_of_PocoCapsule (Type safety in PocoCapsule.) Wiki page edited by kjin101 Jan 15, 2009 Type_Safety_of_PocoCapsule (Type safety in PocoCapsule.) Wiki page edited by kjin101 Jan 15, 2009 Type_Safety_of_PocoCapsule (Type safety in PocoCapsule.) Wiki page edited by kjin101 Jan 14, 2009 Reflection_from_Projection (Reflection from Projection) Wiki page edited by kjin101 Jan 14, 2009 Reflection_from_Projection (Reflection from Projection) Wiki page edited by kjin101 Jan 14, 2009 Reflection_from_Projection (Reflection from Projection) Wiki page edited by kjin101 Jan 13, 2009 Reflection_from_Projection (Reflection from Projection) Wiki page edited by kjin101 Older Dec 01, 2008 Reflection_from_Projection (Reflection from Projection) Wiki page edited by kjin101 Dec 01, 2008 Reflection_from_Projection (Reflection from Projection) Wiki page edited by kjin101 Nov 28, 2008 IoC_containers_vs_DI_pattern Wiki page deleted by kjin101 Nov 19, 2008 IoC_containers_vs_DI_pattern (IoC containers vs the DI design pattern) Wiki page edited by kjin101 Nov 17, 2008 Type_Safety_of_PocoCapsule (Type safety in PocoCapsule.) Wiki page edited by kjin101 Nov 17, 2008 IoC_containers_vs_DI_pattern (IoC containers vs the DI design pattern) Wiki page edited by kjin101 Nov 16, 2008 IoC_containers_vs_DI_pattern (IoC containers vs the DI design pattern) Wiki page edited by kjin101 Nov 16, 2008 Type_Safety_of_PocoCapsule (Type safety in PocoCapsule.) Wiki page edited by kjin101 Nov 16, 2008 Reflection_from_Projection (Reflection from Projection) Wiki page edited by kjin101

issue 2 (pxgenproxy has misleading return code of 0 upon exception) reported by braney - When I run pxgenproxy (under Linux) and it has an exception (e.g. not finding a file), its return code is 0, which means success, and is incorrect. This incorrect return value causes "make" to keep going, even though the setup_reflx.cc file is empty. What steps will reproduce the problem? 1. Install from pococapsule-cpp-1.0-Linux-x86-Install. Set POCOCAPSULE_DIR to the appropriate location. 2. cd $POCOCAPSULE_DIR/examples/basic-ioc/robotic-vehicle 3. mv robotic-application2poco.xsl robotic-application2poco.xsl_ # (this step is just to cause the exception) 4. $POCOCAPSULE_DIR/bin/pxgenproxy -r=gather setup.xml # notice the exception 5. echo $? # shows value of 0 (You can also just run "make" at step 4 and watch it produce the exception and then continue past it.) What is the expected output? What do you see instead? I expect pxgenproxy to have a non-zero return code if it encounters an exception -- especially an exception from parsing the setup.xml file! This way, the make process can catch the error and stop. Instead, I see pxgenproxy returning a return code of zero, which in Linux means success. Make interprets that as "everything is OK" and continues on to compiling the (invalid) setup_reflx.cc file. What version of the product are you using? On what operating system? I guess version 1.0. I installed via the binary installer (pococapsule-cpp-1.0-Linux-x86-Install) under SUSE Linux Enterprise Server 10. Please provide any additional information below. I have successfully compiled all of the "basic-ioc" examples. The above steps are just to demonstrate the issue. This problem occurs when I start to modify things and try to apply it to my application. If I get "setup.xml" wrong or forget an .xsl file, pxgenproxy complains but make doesn't notice the problem, which is very inconvenient while still trying to figure out how to make everything work right.

When I run pxgenproxy (under Linux) and it has an exception (e.g. not finding a file), its return code is 0, which means success, and is incorrect. This incorrect return value causes "make" to keep going, even though the setup_reflx.cc file is empty. What steps will reproduce the problem? 1. Install from pococapsule-cpp-1.0-Linux-x86-Install. Set POCOCAPSULE_DIR to the appropriate location. 2. cd $POCOCAPSULE_DIR/examples/basic-ioc/robotic-vehicle 3. mv robotic-application2poco.xsl robotic-application2poco.xsl_ # (this step is just to cause the exception) 4. $POCOCAPSULE_DIR/bin/pxgenproxy -r=gather setup.xml # notice the exception 5. echo $? # shows value of 0 (You can also just run "make" at step 4 and watch it produce the exception and then continue past it.) What is the expected output? What do you see instead? I expect pxgenproxy to have a non-zero return code if it encounters an exception -- especially an exception from parsing the setup.xml file! This way, the make process can catch the error and stop. Instead, I see pxgenproxy returning a return code of zero, which in Linux means success. Make interprets that as "everything is OK" and continues on to compiling the (invalid) setup_reflx.cc file. What version of the product are you using? On what operating system? I guess version 1.0. I installed via the binary installer (pococapsule-cpp-1.0-Linux-x86-Install) under SUSE Linux Enterprise Server 10. Please provide any additional information below. I have successfully compiled all of the "basic-ioc" examples. The above steps are just to demonstrate the issue. This problem occurs when I start to modify things and try to apply it to my application. If I get "setup.xml" wrong or forget an .xsl file, pxgenproxy complains but make doesn't notice the problem, which is very inconvenient while still trying to figure out how to make everything work right.

Last 30 days

Earlier this year

Older