bean factory
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 159
Web Form Factory 0.1.3
Web Form Factory is a simple application that binds HTML forms to a database. more>>
Web Form Factory is a simple application that binds HTML forms to a database. It analyzes the HTML file you supply and identifies all the common input types it contains, including text fields, drop down lists, checkboxes, radio buttons, and text areas.
Once all the input types have been detected, it then performs some validation tests that ensures that enough information is contained within the HTML form to allow the program to bind the inputs properly. It then generates the required backend PHP code and returns the form back to the you in a zip file.
Enhancements:
- Form Validation Capabilities were added.
- The user can easily specify which fields are mandatory, and the location and appearance of error messages can be configured.
- A new Tag engine was added.
- Tags can be used to make form generation even simpler and faster by eliminating repetitive form coding tasks.
<<lessOnce all the input types have been detected, it then performs some validation tests that ensures that enough information is contained within the HTML form to allow the program to bind the inputs properly. It then generates the required backend PHP code and returns the form back to the you in a zip file.
Enhancements:
- Form Validation Capabilities were added.
- The user can easily specify which fields are mandatory, and the location and appearance of error messages can be configured.
- A new Tag engine was added.
- Tags can be used to make form generation even simpler and faster by eliminating repetitive form coding tasks.
Download (0.16MB)
Added: 2006-08-25 License: BSD License Price:
1157 downloads
Bio::Tools::AlignFactory 1.4
Bio::Tools::AlignFactory is a base object for alignment factories. more>>
Bio::Tools::AlignFactory is a base object for alignment factories.
SYNOPSIS
You wont be using this as an object, but using a dervied class like Bio::Tools::pSW
Holds common Alignment Factory attributes in place
<<lessSYNOPSIS
You wont be using this as an object, but using a dervied class like Bio::Tools::pSW
Holds common Alignment Factory attributes in place
Download (4.7MB)
Added: 2006-10-10 License: Perl Artistic License Price:
1111 downloads
Virt-Factory 0.0.2
Virt-Factory project manages virtualized infrastructure. more>>
Virt-Factory project manages virtualized infrastructure:
Virt-Factory focuses on interacting with large numbers of virtual systems and on addressing some of the interaction problems that brings with it
Virt-Factory is primarily aimed at a fairly formal setting (data center), though we hope it is also useful on smaller scales
While Virt-Factory has some uses for bare-metal systems, it is first and foremost a tool for managing virtual systems. Future development will be much more focused on virtual systems management than bare-metal.
Virt-Factory provides both a web UI, for ease of use, and an XMLRPC API, for scripting of admin actions.
Virt-Factory is built on open-source projects including Cobbler, libvirt, and Puppet.
Today, Virt-Factory provisions and manages hosts and guests. It also addresses some of the problems specific to virtual systems. It creates complete host and guest images from metadata descriptions and centrally manages existing images.
Future work will make it possible to abstract away individual hosts and place guests into a pool of equivalent hosts, simplifying the administrators view of the data center for many tasks.
Whats It Run On?
It is being developed on FC-6. Well add support for FC-7 and RHEL-5 shortly.
How Stable Is It?
At this point, virt-factory an alpha level project that will probably eat your brane. However its getting better every day.
Whats the architecture look like?
Virt-factory provides a central server for managing virtual hosts and guests. The server exposes an XMLRPC API that is used by the Web UI, and can also be used by custom scripts. On Managed systems, a special "node daemon" is installed, which the central server communicates with over secure XMLRPC.
Who is the target user?
Developers who want to be involved in new systems management technology. Users wishing to run a large number of virtual systems that have a key interest in virtualization and system recipes / appliance concepts.
How is Virtualization used?
Virtualization plays a core role in virt-factory and is heavily integrated. The software takes care of the nuts and bolts and can entirely manage your virtualization, though logging into virtualization via xm and virsh is still supported. Virt-factory is about enablement of virtualization as a core systems-management strategy.
How do you treat appliances?
Appliances can be defined purely as metadata ("profiles") rather than binary blobs. The metadata describes the required virtual machines attributes (number of processors, memory etc), the base system installation (as a template data for the kickstart file), and the appliances "personality" as a puppet manifest. This makes it possible to distribute appliances easily, and allows end-users to adapt appliances to their needs while still being able to consume appliance updates.
Enhancements:
- This release concentrates on making the code more stable and easier to install/deploy.
<<lessVirt-Factory focuses on interacting with large numbers of virtual systems and on addressing some of the interaction problems that brings with it
Virt-Factory is primarily aimed at a fairly formal setting (data center), though we hope it is also useful on smaller scales
While Virt-Factory has some uses for bare-metal systems, it is first and foremost a tool for managing virtual systems. Future development will be much more focused on virtual systems management than bare-metal.
Virt-Factory provides both a web UI, for ease of use, and an XMLRPC API, for scripting of admin actions.
Virt-Factory is built on open-source projects including Cobbler, libvirt, and Puppet.
Today, Virt-Factory provisions and manages hosts and guests. It also addresses some of the problems specific to virtual systems. It creates complete host and guest images from metadata descriptions and centrally manages existing images.
Future work will make it possible to abstract away individual hosts and place guests into a pool of equivalent hosts, simplifying the administrators view of the data center for many tasks.
Whats It Run On?
It is being developed on FC-6. Well add support for FC-7 and RHEL-5 shortly.
How Stable Is It?
At this point, virt-factory an alpha level project that will probably eat your brane. However its getting better every day.
Whats the architecture look like?
Virt-factory provides a central server for managing virtual hosts and guests. The server exposes an XMLRPC API that is used by the Web UI, and can also be used by custom scripts. On Managed systems, a special "node daemon" is installed, which the central server communicates with over secure XMLRPC.
Who is the target user?
Developers who want to be involved in new systems management technology. Users wishing to run a large number of virtual systems that have a key interest in virtualization and system recipes / appliance concepts.
How is Virtualization used?
Virtualization plays a core role in virt-factory and is heavily integrated. The software takes care of the nuts and bolts and can entirely manage your virtualization, though logging into virtualization via xm and virsh is still supported. Virt-factory is about enablement of virtualization as a core systems-management strategy.
How do you treat appliances?
Appliances can be defined purely as metadata ("profiles") rather than binary blobs. The metadata describes the required virtual machines attributes (number of processors, memory etc), the base system installation (as a template data for the kickstart file), and the appliances "personality" as a puppet manifest. This makes it possible to distribute appliances easily, and allows end-users to adapt appliances to their needs while still being able to consume appliance updates.
Enhancements:
- This release concentrates on making the code more stable and easier to install/deploy.
Download (MB)
Added: 2007-05-03 License: GPL (GNU General Public License) Price:
905 downloads
Bio::Tree::DistanceFactory 1.5.2_102
Bio::Tree::DistanceFactory is a Perl module to construct a tree using distance based methods. more>>
Bio::Tree::DistanceFactory is a Perl module to construct a tree using distance based methods.
SYNOPSIS
use Bio::Tree::DistanceFactory;
use Bio::AlignIO;
use Bio::Align::DNAStatistics;
my $tfactory = Bio::Tree::DistanceFactory->new(-method => "NJ");
my $stats = Bio::Align::DNAStatistics->new();
my $alnin = Bio::AlignIO->new(-format => clustalw,
-file => file.aln);
my $aln = $alnin->next_aln;
# Of course matrix can come from a different place
# like PHYLIP if you prefer, Bio::Matrix::IO should be able
# to parse many things
my $jcmatrix = $stats->distance(-align => $aln,
-method => Jukes-Cantor);
my $tree = $tfactory->make_tree($jcmatrix);
This is a factory which will construct a phylogenetic tree based on the pairwise sequence distances for a set of sequences. Currently UPGMA (Sokal and Michener 1958) and NJ (Saitou and Nei 1987) tree construction methods are implemented.
<<lessSYNOPSIS
use Bio::Tree::DistanceFactory;
use Bio::AlignIO;
use Bio::Align::DNAStatistics;
my $tfactory = Bio::Tree::DistanceFactory->new(-method => "NJ");
my $stats = Bio::Align::DNAStatistics->new();
my $alnin = Bio::AlignIO->new(-format => clustalw,
-file => file.aln);
my $aln = $alnin->next_aln;
# Of course matrix can come from a different place
# like PHYLIP if you prefer, Bio::Matrix::IO should be able
# to parse many things
my $jcmatrix = $stats->distance(-align => $aln,
-method => Jukes-Cantor);
my $tree = $tfactory->make_tree($jcmatrix);
This is a factory which will construct a phylogenetic tree based on the pairwise sequence distances for a set of sequences. Currently UPGMA (Sokal and Michener 1958) and NJ (Saitou and Nei 1987) tree construction methods are implemented.
Download (5.6MB)
Added: 2007-06-20 License: Perl Artistic License Price:
856 downloads
Database Bean Generator 2.1.3
Generator is a command line application to facilitate the construction of small applications that need some database objects. more>>
Generator is an command line application written in java that have the goal to make easy the construction of little applications that needs some database objects stuff.
Database Bean Generator isnt a replacement of complex object persistence solutions, like hibernate or TopLink but it covers a different target. The little java web applications that dont use sofisticated persistence options.
Generator invocation is simple, just type:
java -jar generator.jar -xml (config-file.xml)
where config-file is a xml config file with the definitions to connect to the database and generate the bean classes.
Main features:
- Generates classes to access via custom connection resources to database tables.
- Configuration files are in clear xml format and can be embedded or separate.
- Supports individual or global field updates.
- Supports custom set of Exceptions.
- Provides toXML function for each entity generated.
- Provides automatic generation of finders coonfigured in the xml configuration file.
- Provides some utility static methods via the BdUtils.java class generation.
- Generates an xml file with the database structure.
- Supports configuration of the methods that produces XML (String as CDATA, data as attributes or values, ...)
- Initial support for MySQL and Oracle (Oracle support is in initial stage at this moment).
- Provides an ant task for automatic integration builds.
- Supports transparent renaming of the generated class individual fields.
- Supports normal or CDATA output in individual fields.
- Supports utilization in all database methods with your own external connection.
- Preliminar support of a pluggable logging system (The goal is use log4j integration)
- Support for SEQUENCES in Oracle and AUTOINCREMENT in MySQL
- Support arbitrary raw code and imports from configuration file
- Correct treatment for NULL values of the fields in the generated class
Enhancements:
- Optionally, you may include the extra jars to get JSON support.
- JSON output for finders and generic JSON output for general have been added.
<<lessDatabase Bean Generator isnt a replacement of complex object persistence solutions, like hibernate or TopLink but it covers a different target. The little java web applications that dont use sofisticated persistence options.
Generator invocation is simple, just type:
java -jar generator.jar -xml (config-file.xml)
where config-file is a xml config file with the definitions to connect to the database and generate the bean classes.
Main features:
- Generates classes to access via custom connection resources to database tables.
- Configuration files are in clear xml format and can be embedded or separate.
- Supports individual or global field updates.
- Supports custom set of Exceptions.
- Provides toXML function for each entity generated.
- Provides automatic generation of finders coonfigured in the xml configuration file.
- Provides some utility static methods via the BdUtils.java class generation.
- Generates an xml file with the database structure.
- Supports configuration of the methods that produces XML (String as CDATA, data as attributes or values, ...)
- Initial support for MySQL and Oracle (Oracle support is in initial stage at this moment).
- Provides an ant task for automatic integration builds.
- Supports transparent renaming of the generated class individual fields.
- Supports normal or CDATA output in individual fields.
- Supports utilization in all database methods with your own external connection.
- Preliminar support of a pluggable logging system (The goal is use log4j integration)
- Support for SEQUENCES in Oracle and AUTOINCREMENT in MySQL
- Support arbitrary raw code and imports from configuration file
- Correct treatment for NULL values of the fields in the generated class
Enhancements:
- Optionally, you may include the extra jars to get JSON support.
- JSON output for finders and generic JSON output for general have been added.
Download (1.9MB)
Added: 2007-07-25 License: LGPL (GNU Lesser General Public License) Price:
503 downloads
CSS::SAC::ConditionFactory 0.06
CSS::SAC::ConditionFactory Perl module contains the default ConditionFactory. more>>
CSS::SAC::ConditionFactory Perl module contains the default ConditionFactory.
SYNOPSIS
my $cf = CSS::SAC::ConditionFactory->new;
my $cond1 = $cf->create_foo_condition;
my $cond2 = $cf->create_bar_condition;
This is the default ConditionFactory for CSS::SAC. It creates conditions of all types defined in SAC. You may wish to subclass or replace the default ConditionFactory in order to get your own condition objects.
I plan on adding more flexibility to this factory so that one could tell it the classes to use for various conditions, that would avoid enforcing subclassing/recoding for people that only want to replace a family of factory methods.
I know that some of the method names are quite lengthy, but given the great number of possible conditions it helps to have descriptive names.
METHODS
These define the interface that must be adhered to by ConditionFactories. The Java names (given in parens) work too, though the Perl ones are recommended.
CSS::SAC::ConditionFactory->new or $cf->new
Creates a new condition factory object.
$cf->create_and_condition($first,$second) (createAndCondition)
creates a combinator condition of type and
$cf->create_attribute_condition($lname,$ns,$specified,$value) (createAttributeCondition)
creates an attr condition
$cf->create_begin_hyphen_attribute_condition($lname,$ns,$specified,$value) (createBeginHyphenAttributeCondition)
creates a attr condition of type bh
$cf->create_class_condition($ns,$value) (createClassCondition)
creates a attr condition of type class
$cf->create_content_condition($data) (createContentCondition)
creates a content condition
$cf->create_id_condition($value) (createIdCondition)
creates a attr condition of type id
$cf->create_lang_condition($lang) (createLangCondition)
creates a lang condition
$cf->create_negative_condition($cond) (createNegativeCondition)
creates a negative condition
$cf->create_one_of_attribute_condition($lname,$ns,$specified,$value) (createOneOfAttributeCondition)
creates a attr condition of type id
$cf->create_only_child_condition() (createOnlyChildCondition)
creates a only-child condition
$cf->create_only_type_condition() (createOnlyTypeCondition)
creates a only-type condition
$cf->create_or_condition($first,$second) (createOrCondition)
creates a combinator condition of type or
$cf->create_positional_condition($position,$type_node,$same_type) (createPositionalCondition)
creates a positional condition
$cf->create_pseudo_class_condition($ns,$value) (createPseudoClassCondition)
creates a attr condition of type pseudo class
<<lessSYNOPSIS
my $cf = CSS::SAC::ConditionFactory->new;
my $cond1 = $cf->create_foo_condition;
my $cond2 = $cf->create_bar_condition;
This is the default ConditionFactory for CSS::SAC. It creates conditions of all types defined in SAC. You may wish to subclass or replace the default ConditionFactory in order to get your own condition objects.
I plan on adding more flexibility to this factory so that one could tell it the classes to use for various conditions, that would avoid enforcing subclassing/recoding for people that only want to replace a family of factory methods.
I know that some of the method names are quite lengthy, but given the great number of possible conditions it helps to have descriptive names.
METHODS
These define the interface that must be adhered to by ConditionFactories. The Java names (given in parens) work too, though the Perl ones are recommended.
CSS::SAC::ConditionFactory->new or $cf->new
Creates a new condition factory object.
$cf->create_and_condition($first,$second) (createAndCondition)
creates a combinator condition of type and
$cf->create_attribute_condition($lname,$ns,$specified,$value) (createAttributeCondition)
creates an attr condition
$cf->create_begin_hyphen_attribute_condition($lname,$ns,$specified,$value) (createBeginHyphenAttributeCondition)
creates a attr condition of type bh
$cf->create_class_condition($ns,$value) (createClassCondition)
creates a attr condition of type class
$cf->create_content_condition($data) (createContentCondition)
creates a content condition
$cf->create_id_condition($value) (createIdCondition)
creates a attr condition of type id
$cf->create_lang_condition($lang) (createLangCondition)
creates a lang condition
$cf->create_negative_condition($cond) (createNegativeCondition)
creates a negative condition
$cf->create_one_of_attribute_condition($lname,$ns,$specified,$value) (createOneOfAttributeCondition)
creates a attr condition of type id
$cf->create_only_child_condition() (createOnlyChildCondition)
creates a only-child condition
$cf->create_only_type_condition() (createOnlyTypeCondition)
creates a only-type condition
$cf->create_or_condition($first,$second) (createOrCondition)
creates a combinator condition of type or
$cf->create_positional_condition($position,$type_node,$same_type) (createPositionalCondition)
creates a positional condition
$cf->create_pseudo_class_condition($ns,$value) (createPseudoClassCondition)
creates a attr condition of type pseudo class
Download (0.037MB)
Added: 2007-06-20 License: Perl Artistic License Price:
856 downloads
Flatworm 1.2
Flatworm is a Java library intended to allow a developer to describe the format of a flat file using an XML definition file. more>>
Flatworm project is a Java library intended to allow a developer to describe the format of a flat file using an XML definition file, and then to be able to automatically read lines from that file, and have one or more beans be instantiated for each logical record.
There are a few powerful features in Flatworm worth mentioning. For one thing, a record may consist of one or more physical lines in the file. A record may contain more than one bean once decoded. A flat file may contain more than one type of record, and Flatworm can use line length and substring matching to determine which type of record a line begins.
Besides fielded buffer flat files, Flatworm also supports text files where the different fields are separated by a separator character, e.g. CSV (comma separated values) files.
Last but not least, Flatworm is able to produce flat files from beans and the same definition file.
<<lessThere are a few powerful features in Flatworm worth mentioning. For one thing, a record may consist of one or more physical lines in the file. A record may contain more than one bean once decoded. A flat file may contain more than one type of record, and Flatworm can use line length and substring matching to determine which type of record a line begins.
Besides fielded buffer flat files, Flatworm also supports text files where the different fields are separated by a separator character, e.g. CSV (comma separated values) files.
Last but not least, Flatworm is able to produce flat files from beans and the same definition file.
Download (0.044MB)
Added: 2007-08-07 License: LGPL (GNU Lesser General Public License) Price:
808 downloads
pBeans 2.0.2
pBeans project is a Object/Relational (O/R) database mapping layer. more>>
pBeans project is a Object/Relational (O/R) database mapping layer. It is designed to be simple to use and automated.
The idea is that you save time and effort by simply focusing on writing Java classes, and not worrying about maintenance of matching SQL scripts, schema evolution, XML based schemas, or generating code. The pBeans framework takes care of persisting JavaBeans with little assistance from the developer.
Main features:
- Automatic Table Creation and Schema Evolution- Tables corresponding to JavaBean classes are created on demand. Field types are based, by default, on JavaBean compile-time types. Field type changes and new fields are detected. Manually changing tables (user-managed mode) is also supported.
- Based on Annotated JavaBeans- You define a getter and setter for each bean property. Persisent bean classes only need to be tagged with a @PersistentClass annotation.
- Transitive Persistence- If object A is persisted and it refers to Persistent object B, then object B is automatically persisted. If Persistent object C also refers to B, and C is also persisted, the record for object B in the database is not duplicated.
- Instance Consistency- If you retrieve an object from persistent storage that is already known to exist in main memory, you get a reference to the object in main memory. (Garbage collection is allowed to happen via weak references.)
- Near-Zero Configuration- There is no need to define schemas or anything of the sort in a language other than Java, and there are no code generation steps of any kind. No XML or SQL need to be written, except the necessary to create a database and grant user permissions. However, you can instruct pBeans to let you manage database modifications manually.
- Database features- Transactions and auto-increment IDs (MySQL only) are now supported.
- Flexibility- Via annotations users are allowed to define their own table and field names, the name of the primary key, whether fields are nullable, whether tables are user-managed (not automatically modified), table indexes, unique or otherwise, whether unused fields should be deleted, whether a field is nullable, whether it is renamed from another field (to prevent loss of data when a property is renamed), etc.
- Servlet support- A pBeans store may be easily configured using servlet context parameters (see ServletAccess.)
<<lessThe idea is that you save time and effort by simply focusing on writing Java classes, and not worrying about maintenance of matching SQL scripts, schema evolution, XML based schemas, or generating code. The pBeans framework takes care of persisting JavaBeans with little assistance from the developer.
Main features:
- Automatic Table Creation and Schema Evolution- Tables corresponding to JavaBean classes are created on demand. Field types are based, by default, on JavaBean compile-time types. Field type changes and new fields are detected. Manually changing tables (user-managed mode) is also supported.
- Based on Annotated JavaBeans- You define a getter and setter for each bean property. Persisent bean classes only need to be tagged with a @PersistentClass annotation.
- Transitive Persistence- If object A is persisted and it refers to Persistent object B, then object B is automatically persisted. If Persistent object C also refers to B, and C is also persisted, the record for object B in the database is not duplicated.
- Instance Consistency- If you retrieve an object from persistent storage that is already known to exist in main memory, you get a reference to the object in main memory. (Garbage collection is allowed to happen via weak references.)
- Near-Zero Configuration- There is no need to define schemas or anything of the sort in a language other than Java, and there are no code generation steps of any kind. No XML or SQL need to be written, except the necessary to create a database and grant user permissions. However, you can instruct pBeans to let you manage database modifications manually.
- Database features- Transactions and auto-increment IDs (MySQL only) are now supported.
- Flexibility- Via annotations users are allowed to define their own table and field names, the name of the primary key, whether fields are nullable, whether tables are user-managed (not automatically modified), table indexes, unique or otherwise, whether unused fields should be deleted, whether a field is nullable, whether it is renamed from another field (to prevent loss of data when a property is renamed), etc.
- Servlet support- A pBeans store may be easily configured using servlet context parameters (see ServletAccess.)
Download (1.3MB)
Added: 2007-04-25 License: GPL (GNU General Public License) Price:
912 downloads
Workflow::Factory 0.28
Workflow::Factory is a Perl module that generates new workflow and supporting objects. more>>
Workflow::Factory is a Perl module that generates new workflow and supporting objects.
SYNOPSIS
# Import the singleton for easy access
use Workflow::Factory qw( FACTORY );
# Add XML configurations to the factory
FACTORY->add_config_from_file( workflow => workflow.xml,
action => [ myactions.xml, otheractions.xml ],
validator => [ validator.xml, myvalidators.xml ],
condition => condition.xml,
persister => persister.xml );
# Create a new workflow of type MyWorkflow
my $wf = FACTORY->create_workflow( MyWorkflow );
# Fetch an existing workflow with ID 25
my $wf = FACTORY->fetch_workflow( MyWorkflow, 25 );
Public
The Workflow Factory is your primary interface to the workflow system. You give it the configuration files and/or data structures for the Workflow, Workflow::Action, Workflow::Condition, Workflow::Persister, and Workflow::Validator objects and then you ask it for new and existing Workflow objects.
Internal
Developers using the workflow system should be familiar with how the factory processes configurations and how it makes the various components of the system are instantiated and stored in the factory.
<<lessSYNOPSIS
# Import the singleton for easy access
use Workflow::Factory qw( FACTORY );
# Add XML configurations to the factory
FACTORY->add_config_from_file( workflow => workflow.xml,
action => [ myactions.xml, otheractions.xml ],
validator => [ validator.xml, myvalidators.xml ],
condition => condition.xml,
persister => persister.xml );
# Create a new workflow of type MyWorkflow
my $wf = FACTORY->create_workflow( MyWorkflow );
# Fetch an existing workflow with ID 25
my $wf = FACTORY->fetch_workflow( MyWorkflow, 25 );
Public
The Workflow Factory is your primary interface to the workflow system. You give it the configuration files and/or data structures for the Workflow, Workflow::Action, Workflow::Condition, Workflow::Persister, and Workflow::Validator objects and then you ask it for new and existing Workflow objects.
Internal
Developers using the workflow system should be familiar with how the factory processes configurations and how it makes the various components of the system are instantiated and stored in the factory.
Download (0.10MB)
Added: 2007-07-10 License: Perl Artistic License Price:
839 downloads
PerlBean::Collection 1.0
PerlBean::Collection is a Perl module that contains a collection of PerlBean objects. more>>
PerlBean::Collection is a Perl module that contains a collection of PerlBean objects.
SYNOPSIS
use strict;
use PerlBean;
use PerlBean::Collection;
use PerlBean::Attribute::Factory;
my $bean = PerlBean->new( {
package => Athlete,
} );
my $factory = PerlBean::Attribute::Factory->new();
my $attr = $factory->create_attribute( {
method_factory_name => name,
short_description => the name of the athlete,
} );
$bean->add_method_factory($attr);
my $bean2 = PerlBean->new( {
package => Cyclist,
base => [ qw(Athlete)],
} );
my $factory = PerlBean::Attribute::Factory->new();
my $attr2 = $factory->create_attribute( {
method_factory_name => cycle,
short_description => the cyclists cycle,
} );
$bean2->add_method_factory($attr2);
my $collection = PerlBean::Collection->new();
$collection->add_perl_bean($bean);
$collection->add_perl_bean($bean2);
$collection->write(tmp);
ABSTRACT
Code hierarchy generation for bean like Perl modules
PerlBean::Collection contains a collection of PerlBean objects in order to generate an hierarchy of Perl modules.
<<lessSYNOPSIS
use strict;
use PerlBean;
use PerlBean::Collection;
use PerlBean::Attribute::Factory;
my $bean = PerlBean->new( {
package => Athlete,
} );
my $factory = PerlBean::Attribute::Factory->new();
my $attr = $factory->create_attribute( {
method_factory_name => name,
short_description => the name of the athlete,
} );
$bean->add_method_factory($attr);
my $bean2 = PerlBean->new( {
package => Cyclist,
base => [ qw(Athlete)],
} );
my $factory = PerlBean::Attribute::Factory->new();
my $attr2 = $factory->create_attribute( {
method_factory_name => cycle,
short_description => the cyclists cycle,
} );
$bean2->add_method_factory($attr2);
my $collection = PerlBean::Collection->new();
$collection->add_perl_bean($bean);
$collection->add_perl_bean($bean2);
$collection->write(tmp);
ABSTRACT
Code hierarchy generation for bean like Perl modules
PerlBean::Collection contains a collection of PerlBean objects in order to generate an hierarchy of Perl modules.
Download (0.089MB)
Added: 2007-02-22 License: Perl Artistic License Price:
977 downloads
Azuki Framework 1.0.1
Azuki Framework is a Java application framework designed to resolve various problems in the software development lifecycle. more>>
Azuki Framework project is a Java application framework designed to resolve various problems in the software development lifecycle. These goals are achieved by splitting the software conception into two main stages: creation of independent components and definition of component dependencies (weaving).
The latter is performed with a graphical tool named "the weaver". By representing component interactions using different perspectives, the weaver provides a straightforward way to analyze an applications architecture, allowing deep and easy customization of its behavior.
Whats New in This Release:
azuki-ant
(ADD) Copy $beanproject/tools into $dist/tools directory when deploying
bean.
(ADD) Additional sources files could be specified into checkbuildXXX
macros.
azuki-common
(FIX) Missing characters into StringUtil.splitQuote().
(ADD) SQL_MAX_ROWS global variable for sql query limitation.
(ADD) SQL utility class.
(ADD) Possibility to enable/disable filters on document and text fields.
azuki-framework
(FIX) New method to retrieve framework version.
azuki-weaver
(FIX) Dont show Definition menu entry in pointcut popup menu.
(FIX) Enable status was not displayed correctly into schemas.
(FIX) Check if bean instance is duplicated before renaming.
(FIX) Automatically set a new label when pasting a bean instance.
dist
(FIX) Do not start azuki shell server by default (kernel.xml).
(FIX) Invalid commons-codec library name in CLASSPATH.
(FIX) Set up JNDI and SOAP implementation in shell script .sh and .bat.
(ADD) Create directory $dist/tools.
bean-apportal
(FIX) Display framework version.
(FIX) Bean indentifier retrieval doesnt take care of root context.
bean-gwt
(DEL) Removed, will be included from future 1.1 branch releases.
bean-injection
(FIX) Add some comments.
(FIX) Include arrays in method parameters conversion.
(FIX) Include primitive types in method parameters conversion.
bean-logger
(FIX) Take care to not close the System.err stream when using the
java.util.logging API.
(FIX) Move SQL sources into tools directory.
bean-requesthandler
(FIX) Use the servlet context path for set up the base URI.
(FIX) Throws exception when trying to bind an already binded URI.
bean-shell
(FIX) Null pointer while searching bean metadata in TCP request processing.
(FIX) Move C program sources into tools directory.
<<lessThe latter is performed with a graphical tool named "the weaver". By representing component interactions using different perspectives, the weaver provides a straightforward way to analyze an applications architecture, allowing deep and easy customization of its behavior.
Whats New in This Release:
azuki-ant
(ADD) Copy $beanproject/tools into $dist/tools directory when deploying
bean.
(ADD) Additional sources files could be specified into checkbuildXXX
macros.
azuki-common
(FIX) Missing characters into StringUtil.splitQuote().
(ADD) SQL_MAX_ROWS global variable for sql query limitation.
(ADD) SQL utility class.
(ADD) Possibility to enable/disable filters on document and text fields.
azuki-framework
(FIX) New method to retrieve framework version.
azuki-weaver
(FIX) Dont show Definition menu entry in pointcut popup menu.
(FIX) Enable status was not displayed correctly into schemas.
(FIX) Check if bean instance is duplicated before renaming.
(FIX) Automatically set a new label when pasting a bean instance.
dist
(FIX) Do not start azuki shell server by default (kernel.xml).
(FIX) Invalid commons-codec library name in CLASSPATH.
(FIX) Set up JNDI and SOAP implementation in shell script .sh and .bat.
(ADD) Create directory $dist/tools.
bean-apportal
(FIX) Display framework version.
(FIX) Bean indentifier retrieval doesnt take care of root context.
bean-gwt
(DEL) Removed, will be included from future 1.1 branch releases.
bean-injection
(FIX) Add some comments.
(FIX) Include arrays in method parameters conversion.
(FIX) Include primitive types in method parameters conversion.
bean-logger
(FIX) Take care to not close the System.err stream when using the
java.util.logging API.
(FIX) Move SQL sources into tools directory.
bean-requesthandler
(FIX) Use the servlet context path for set up the base URI.
(FIX) Throws exception when trying to bind an already binded URI.
bean-shell
(FIX) Null pointer while searching bean metadata in TCP request processing.
(FIX) Move C program sources into tools directory.
Download (11.5MB)
Added: 2007-08-08 License: LGPL (GNU Lesser General Public License) Price:
809 downloads
Bio::Factory::SequenceFactoryI 1.4
Bio::Factory::SequenceFactoryI is a Perl interface that allows for generic building of sequences in factories. more>>
Bio::Factory::SequenceFactoryI is a Perl interface that allows for generic building of sequences in factories which create sequences (like SeqIO).
SYNOPSIS
# do not use this object directly it is an interface # get a Bio::Factory::SequenceFactoryI object like
use Bio::Seq::SeqFactory;
my $seqbuilder = new Bio::Seq::SeqFactory(type => Bio::PrimarySeq);
my $seq = $seqbuilder->create(-seq => ACTGAT,
-display_id => exampleseq);
print "seq is a ", ref($seq), "n";
A generic way to build Sequence objects via a pluggable factory. This reduces the amount of code that looks like
if( $type eq Bio::PrimarySeq ) { ... }
elsif( $type eq Bio::Seq::RichSeq ) { ... }
<<lessSYNOPSIS
# do not use this object directly it is an interface # get a Bio::Factory::SequenceFactoryI object like
use Bio::Seq::SeqFactory;
my $seqbuilder = new Bio::Seq::SeqFactory(type => Bio::PrimarySeq);
my $seq = $seqbuilder->create(-seq => ACTGAT,
-display_id => exampleseq);
print "seq is a ", ref($seq), "n";
A generic way to build Sequence objects via a pluggable factory. This reduces the amount of code that looks like
if( $type eq Bio::PrimarySeq ) { ... }
elsif( $type eq Bio::Seq::RichSeq ) { ... }
Download (4.7MB)
Added: 2006-09-02 License: Perl Artistic License Price:
1147 downloads
ObjectScript 2.10.1
ObjectScript is an object oriented scripting language. more>>
ObjectScript is a general purpose object-oriented programming language. ObjectScript is designed to be simple to learn, easy to use, yet still powerful, combining the convenience of an interactive interpreter with many of the features of Java:
Main features:
- a simple java-like syntax
- class system, with single inheritance and mixins
- private/protected/public fields and methods
- exceptions for error handling
- synchronization and threading
- compiles to bytecode for higher performance
- osdoc: a javadoc-like tool to extract API documents
- from src code, plus API docs accessible reflectively
- XML-RPC support
- Windows COM support
- regular expressions (requires java v1.4 or later)
Plus, its free! And since it is written in Java, programs written in ObjectScript can take advantage of existing Java code and libraries, like Swing. ObjectScript programs can not only create instances of Java objects, call Java methods, access public fields, access java bean properties, but can also extend Java classes, and implement Java interfaces.
Since it can be interactively interpreted, ObjectScript is the perfect way to debug or learn Java systems. And since it supports extending Java classes and interfaces, it can add sophisticated scripting to an existing Java application.
<<lessMain features:
- a simple java-like syntax
- class system, with single inheritance and mixins
- private/protected/public fields and methods
- exceptions for error handling
- synchronization and threading
- compiles to bytecode for higher performance
- osdoc: a javadoc-like tool to extract API documents
- from src code, plus API docs accessible reflectively
- XML-RPC support
- Windows COM support
- regular expressions (requires java v1.4 or later)
Plus, its free! And since it is written in Java, programs written in ObjectScript can take advantage of existing Java code and libraries, like Swing. ObjectScript programs can not only create instances of Java objects, call Java methods, access public fields, access java bean properties, but can also extend Java classes, and implement Java interfaces.
Since it can be interactively interpreted, ObjectScript is the perfect way to debug or learn Java systems. And since it supports extending Java classes and interfaces, it can add sophisticated scripting to an existing Java application.
Download (11MB)
Added: 2006-05-11 License: LGPL (GNU Lesser General Public License) Price:
1261 downloads
SWIFT::Factory::BasicHeader 0.03
SWIFT::Factory::BasicHeader is a Perl module that provides a Basic Header Block (Block 1) for a SWIFT message. more>>
SWIFT::Factory::BasicHeader is a Perl module that provides a Basic Header Block (Block 1) for a SWIFT message.
SYNOPSIS
use SWIFT::Factory::BasicHeader;
my $hdr1=SWIFT::Factory::BasicHeader->new();
This module is primarily intended to be used by the different SWIFT::Factory::MTnnn modules to provide full SWIFT messages for input to the SWIFT network.
Nevertheless, there is nothing prohibiting an application to directly use this module for whatever purpose.
Given reasonable parameter values in the constructor, the string method in this module will return a Basic Header Block (Block nbr 1) that can be used in a SWIFT message sent to the SWIFT network.
CONSTRUCTOR
new( APPLICATION_ID=>F, SERVICE_ID=>1, BIC=>VALIDBIC, TERMINAL=>X, BRANCH_CODE=>XXX, SESSION_NBR=>0, INPUT_SEQUENCE_NBR=>0)
The parameters may be given in arbitrary order. Many parameters have builtin default values. If the calling application doesnt provide the parameter at all, the object will apply the default value.
APPLICATION_ID=>
Optional. A one character value that indicates the application within which the message is being sent.
Valid values are:
F (FIN = All user-to-user, FIN system and FIN system msgs),
A (GPA = Most GPA system mesgs)
and
L (Certain GPA msgs, for ex. LOGIN).
Default value: F, which is the most commonly used application.
To set this value, use one of:
SWIFT::Factory::BasicHeader->APP_ID_FIN,
SWIFT::Factory::BasicHeader->APP_ID_GPA,
and
SWIFT::Factory::BasicHeader->APP_ID_GPA_LOG.
Yes, these are constants, and yes, since they are class methods they are available before calling the constructor.
Opposit of the object methods that are functional only after having called the new() constructor.
SERVICE_ID=>
Optional. A numeric value that identifies the type of data that is being sent. Maximum two characters long. See the relevant SWIFT handbook for details.
Default value: 1, which will output as 01.
BIC=>
Technically optional, but it will probably quite rarely make sense to instantiate an object of this class without specifying a BIC. An eight character value that contains a valid receiver BIC.
TERMINAL=>
Optional. A one character value that identifies the receiving terminal.
Default value: X.
BRANCH_CODE=>
Optional. A three character value that identifies the branch code at the receiver.
Default value: XXX.
SESSION_NBR=>
Optional. A numeric value. Maximum four characters long. See the relevant SWIFT handbook for details.
Default value: 0, which will output as 0000.
INPUT_SEQUENCE_NBR=>
Optional. A numeric value. Maximum six characters long. See the relevant SWIFT handbook for details.
Default value: 0, which will output as 000000.
<<lessSYNOPSIS
use SWIFT::Factory::BasicHeader;
my $hdr1=SWIFT::Factory::BasicHeader->new();
This module is primarily intended to be used by the different SWIFT::Factory::MTnnn modules to provide full SWIFT messages for input to the SWIFT network.
Nevertheless, there is nothing prohibiting an application to directly use this module for whatever purpose.
Given reasonable parameter values in the constructor, the string method in this module will return a Basic Header Block (Block nbr 1) that can be used in a SWIFT message sent to the SWIFT network.
CONSTRUCTOR
new( APPLICATION_ID=>F, SERVICE_ID=>1, BIC=>VALIDBIC, TERMINAL=>X, BRANCH_CODE=>XXX, SESSION_NBR=>0, INPUT_SEQUENCE_NBR=>0)
The parameters may be given in arbitrary order. Many parameters have builtin default values. If the calling application doesnt provide the parameter at all, the object will apply the default value.
APPLICATION_ID=>
Optional. A one character value that indicates the application within which the message is being sent.
Valid values are:
F (FIN = All user-to-user, FIN system and FIN system msgs),
A (GPA = Most GPA system mesgs)
and
L (Certain GPA msgs, for ex. LOGIN).
Default value: F, which is the most commonly used application.
To set this value, use one of:
SWIFT::Factory::BasicHeader->APP_ID_FIN,
SWIFT::Factory::BasicHeader->APP_ID_GPA,
and
SWIFT::Factory::BasicHeader->APP_ID_GPA_LOG.
Yes, these are constants, and yes, since they are class methods they are available before calling the constructor.
Opposit of the object methods that are functional only after having called the new() constructor.
SERVICE_ID=>
Optional. A numeric value that identifies the type of data that is being sent. Maximum two characters long. See the relevant SWIFT handbook for details.
Default value: 1, which will output as 01.
BIC=>
Technically optional, but it will probably quite rarely make sense to instantiate an object of this class without specifying a BIC. An eight character value that contains a valid receiver BIC.
TERMINAL=>
Optional. A one character value that identifies the receiving terminal.
Default value: X.
BRANCH_CODE=>
Optional. A three character value that identifies the branch code at the receiver.
Default value: XXX.
SESSION_NBR=>
Optional. A numeric value. Maximum four characters long. See the relevant SWIFT handbook for details.
Default value: 0, which will output as 0000.
INPUT_SEQUENCE_NBR=>
Optional. A numeric value. Maximum six characters long. See the relevant SWIFT handbook for details.
Default value: 0, which will output as 000000.
Download (0.004MB)
Added: 2007-05-25 License: Perl Artistic License Price:
882 downloads
Learn HTML By Example 1.03
Learn HTML By Example is a sweet little JavaScript / HTML program. more>>
Learn HTML By Example is a sweet little JavaScript / HTML program that allows you to see the HTML you input into on side displayed as a web page on the other.
To install the program, just download it from Web Design Factory, and upload it to your web site.
Main features:
- Easy installation. Just upload to your web site and youre done!
- Immediate feedback on testing HTML and CSS code
- Several examples of commonly used HTML and CSS elements
- No page refreshing required
- Easy to expand by adding new examples
<<lessTo install the program, just download it from Web Design Factory, and upload it to your web site.
Main features:
- Easy installation. Just upload to your web site and youre done!
- Immediate feedback on testing HTML and CSS code
- Several examples of commonly used HTML and CSS elements
- No page refreshing required
- Easy to expand by adding new examples
Download (0.008MB)
Added: 2005-12-19 License: Freeware Price:
1406 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above bean factory search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
