jsr 170
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 25
snescom 1.7.0
snescom is a 65c816 (SNES, etc.) assembler. more>>
This program reads symbolic 65816 or 65c816 machine code and compiles (assembles) it into a relocatable object file.
The produced object file is binary-compatible with those made with XA65.
This program was born when Bisqwit needed a relocatable object -producing snes assembler and XA65 had too many bugs in it.
He was unable to fix the XA65 source so he started his own project, aiming for enough compatibility to be able to use the assembly files already written in the XAxa65 syntax.
Since that, this program has been growing to meet the needs in SNES game and patch development.
The following mnemonics are supported:
adc, and, asl, bcc, bcs, beq, bit, bmi, bne, bpl, bra, brk, brl, bvc, bvs, clc, cld, cli, clv, cmp, cop, cpx, cpy, db , dec, dex, dey, eor, inc, inx, iny, jml, jmp, jsl, jsr, lda, ldx, ldy, lsr, mvn, mvp, nop, ora, pea, pei, per, pha, phb, phd, phk, php, phx, phy, pla, plb, pld, plp, plx, ply, rep, rol, ror, rti, rtl, rts, sbc, sec, sed, sei, sep, sta, stp, stx, sty, stz, tax, tay, tcd, tcs, tdc, trb, tsb, tsc, tsx, txa, txs, txy, tya, tyx, wai, xba, xce
All the standard addressing modes of the 65816 cpu are supported.
Syntax:
- Implied: nop; clc
- Immediate: lda #value; rep #value etc (size may depend on an operand size setting)
- Short relative: bra end
- Long relative: brl end; per end+2
- Direct: lda $12
- Direct indexed: lda $12,x; lda $12,y
- Direct indirect: lda ($12); pei ($12)
- Direct indexed indirect: lda ($12,x)
- Direct indirect indexed: lda ($12),y
- Direct indirect long: lda [$12]
- Direct indirect indexed long: lda [$12],y
- Absolute: lda $1234
- Absolute indexed: lda $1234,x; lda $1234,y
- Absolute long: lda $123456
- Absolute indexed long: lda $123456,x
- Stack-relative: lda $12,s
- Stack-relative indirect indexed: lda ($12,s),y
- Absolute indirect: lda ($1234)
- Absolute indirect long: lda [$1234]
- Absolute indexed indirect: lda ($1234,x)
- MVN/MVP: mvn $7E,$7F
For reference, in Intel syntax it would be something like this (not supported by snescom):
- Implied: nop; clc
- Immediate: lda value; rep value etc (size may depend on an operand size setting)
- Short relative: bra end
- Long relative: brl end; per end+2
- Direct: lda [$00:d+$12]
- Direct indexed: lda [$00:d+$12+x]; lda [$00:d+$12+y]
- Direct indirect: lda [db:[$00:d+$12]]; pei [db:[$00:d+$12]]
- Direct indexed indirect: lda [db:[$00:d+$12+x]]
- Direct indirect indexed: lda [db:[$00:d+$12]+y]
- Direct indirect long: lda [long[$00:d+$12]]
- Direct indirect indexed long: lda [long[$00:d+$12]+y]
- Absolute: lda [db:$1234]
- Absolute indexed: lda [db:$1234+x]; lda [db:$1234+y]
- Absolute long: lda [$12:$3456]
- Absolute indexed long: lda [$12:$3456+x]
- Stack-relative: lda [$00:$12+s]
- Stack-relative indirect indexed: lda [db:[$00:$12+s]+y]
- Absolute indirect: lda [db:[$1234]]
- Absolute indirect long: lda [long[db:$1234]]
- Absolute indexed indirect: lda [db:[db:$1234+x]]
- MVN/MVP: mvn $7E,$7F
Enhancements:
- This release updates the linker program, adding a feature to output raw files, or even ROM files directly in the SMC format, with proper checksums.
- The error handling of the assembler was improved somewhat.
<<lessThe produced object file is binary-compatible with those made with XA65.
This program was born when Bisqwit needed a relocatable object -producing snes assembler and XA65 had too many bugs in it.
He was unable to fix the XA65 source so he started his own project, aiming for enough compatibility to be able to use the assembly files already written in the XAxa65 syntax.
Since that, this program has been growing to meet the needs in SNES game and patch development.
The following mnemonics are supported:
adc, and, asl, bcc, bcs, beq, bit, bmi, bne, bpl, bra, brk, brl, bvc, bvs, clc, cld, cli, clv, cmp, cop, cpx, cpy, db , dec, dex, dey, eor, inc, inx, iny, jml, jmp, jsl, jsr, lda, ldx, ldy, lsr, mvn, mvp, nop, ora, pea, pei, per, pha, phb, phd, phk, php, phx, phy, pla, plb, pld, plp, plx, ply, rep, rol, ror, rti, rtl, rts, sbc, sec, sed, sei, sep, sta, stp, stx, sty, stz, tax, tay, tcd, tcs, tdc, trb, tsb, tsc, tsx, txa, txs, txy, tya, tyx, wai, xba, xce
All the standard addressing modes of the 65816 cpu are supported.
Syntax:
- Implied: nop; clc
- Immediate: lda #value; rep #value etc (size may depend on an operand size setting)
- Short relative: bra end
- Long relative: brl end; per end+2
- Direct: lda $12
- Direct indexed: lda $12,x; lda $12,y
- Direct indirect: lda ($12); pei ($12)
- Direct indexed indirect: lda ($12,x)
- Direct indirect indexed: lda ($12),y
- Direct indirect long: lda [$12]
- Direct indirect indexed long: lda [$12],y
- Absolute: lda $1234
- Absolute indexed: lda $1234,x; lda $1234,y
- Absolute long: lda $123456
- Absolute indexed long: lda $123456,x
- Stack-relative: lda $12,s
- Stack-relative indirect indexed: lda ($12,s),y
- Absolute indirect: lda ($1234)
- Absolute indirect long: lda [$1234]
- Absolute indexed indirect: lda ($1234,x)
- MVN/MVP: mvn $7E,$7F
For reference, in Intel syntax it would be something like this (not supported by snescom):
- Implied: nop; clc
- Immediate: lda value; rep value etc (size may depend on an operand size setting)
- Short relative: bra end
- Long relative: brl end; per end+2
- Direct: lda [$00:d+$12]
- Direct indexed: lda [$00:d+$12+x]; lda [$00:d+$12+y]
- Direct indirect: lda [db:[$00:d+$12]]; pei [db:[$00:d+$12]]
- Direct indexed indirect: lda [db:[$00:d+$12+x]]
- Direct indirect indexed: lda [db:[$00:d+$12]+y]
- Direct indirect long: lda [long[$00:d+$12]]
- Direct indirect indexed long: lda [long[$00:d+$12]+y]
- Absolute: lda [db:$1234]
- Absolute indexed: lda [db:$1234+x]; lda [db:$1234+y]
- Absolute long: lda [$12:$3456]
- Absolute indexed long: lda [$12:$3456+x]
- Stack-relative: lda [$00:$12+s]
- Stack-relative indirect indexed: lda [db:[$00:$12+s]+y]
- Absolute indirect: lda [db:[$1234]]
- Absolute indirect long: lda [long[db:$1234]]
- Absolute indexed indirect: lda [db:[db:$1234+x]]
- MVN/MVP: mvn $7E,$7F
Enhancements:
- This release updates the linker program, adding a feature to output raw files, or even ROM files directly in the SMC format, with proper checksums.
- The error handling of the assembler was improved somewhat.
Download (0.09MB)
Added: 2006-07-27 License: GPL (GNU General Public License) Price:
1189 downloads
Jeceira 0.1.4
Jeceira provides an implementation of JCR (JSR 170). more>>
Jeceira provides an implementation of JCR (JSR 170).
Jeceira is an implementation of JCR, the Content Repository for Java Technology Specification (JSR 170).
Its goal is to create a freely available, fast, and extensible layer for various content dependent applications to build upon.
Enhancements:
- Observation implemented
- Configuration of UUID generator simplified (no jug-native directory required)
- Node.orderBefore revised (including changes in the database schema)
- Bugfix in saving items (new items could be saved by calling save on them)
- Bugfix in counting of changes pending in a session
- Package item refactored
- Dependency on commons-0.1 changed to commons-0.2 due to a bugfix in the
- commons module
<<lessJeceira is an implementation of JCR, the Content Repository for Java Technology Specification (JSR 170).
Its goal is to create a freely available, fast, and extensible layer for various content dependent applications to build upon.
Enhancements:
- Observation implemented
- Configuration of UUID generator simplified (no jug-native directory required)
- Node.orderBefore revised (including changes in the database schema)
- Bugfix in saving items (new items could be saved by calling save on them)
- Bugfix in counting of changes pending in a session
- Package item refactored
- Dependency on commons-0.1 changed to commons-0.2 due to a bugfix in the
- commons module
Download (4.1MB)
Added: 2007-02-09 License: The Apache License Price:
988 downloads
Jetspeed 2.0
Jetspeed provides a JSR-168 compliant enterprise portal. more>>
Jetspeed provides a JSR-168 compliant enterprise portal.
etspeed-2 is a full implementation of the Java Portlet API. It is fully compliant with the Portlet Specification 1.0 (JSR-168). It has passed the TCK (Test Compatibility Kit) suite and is fully CERTIFIED to the Java Portlet Standard.
Notable features include security components backed by LDAP and database implementations, and some robust administration interfaces. Custom portals can be built and deployed using the Jetspeed plugin for Maven.
Developers can use the Jetspeed PSML language to assemble portlets, and the Apache Portals Bridges project to bridge portals with existing technologies including Struts, JSF, PHP, and Perl.
For GUI designers, Jetspeed comes with several built-in templates used to decorate portals and portlets.
Main features:
- Fully compliant with Java Portlet API Standard 1.0 (JSR 168)
- Passed JSR-168 TCK Compatibility Test Suite
- J2EE Security based on JAAS Standard, JAAS DB Portal Security Policy
- LDAP Support for User Authentication
- Spring-based Components and Scalable Architecture
- Configurable Pipeline Request Processor
- Auto Deployment of Portlet Applications
- Jetspeed Component Java API
- Jetspeed AJAX XML API
- Declarative Security Constraints and JAAS Database Security Policy
- Runtime Portlet API Standard Role-based Security
- Portal Content Management and Navigations: Pages, Menus, Folders, Links
- Multithreaded Aggregation Engine
- PSML Folder CMS Navigations, Menus, Links
- Jetspeed SSO (Single Sign-on)
- Rules-based Profiler for page and resource location
- Integrates with most popular databases including Derby, MySQL, MS SQL, Postgres, Oracle, DB2, Hypersonic
- Client independent capability engine (html, xhtml, wml,vml)
- Internationalization: Localized Portal Resources in 12 Languages
- Statistics Logging Engine
- Portlet Registry
- Full Text Search of Portlet Resources with Lucene
- User Registration
- Forgotten Password
- Rich Login and Password Configuration Management
<<lessetspeed-2 is a full implementation of the Java Portlet API. It is fully compliant with the Portlet Specification 1.0 (JSR-168). It has passed the TCK (Test Compatibility Kit) suite and is fully CERTIFIED to the Java Portlet Standard.
Notable features include security components backed by LDAP and database implementations, and some robust administration interfaces. Custom portals can be built and deployed using the Jetspeed plugin for Maven.
Developers can use the Jetspeed PSML language to assemble portlets, and the Apache Portals Bridges project to bridge portals with existing technologies including Struts, JSF, PHP, and Perl.
For GUI designers, Jetspeed comes with several built-in templates used to decorate portals and portlets.
Main features:
- Fully compliant with Java Portlet API Standard 1.0 (JSR 168)
- Passed JSR-168 TCK Compatibility Test Suite
- J2EE Security based on JAAS Standard, JAAS DB Portal Security Policy
- LDAP Support for User Authentication
- Spring-based Components and Scalable Architecture
- Configurable Pipeline Request Processor
- Auto Deployment of Portlet Applications
- Jetspeed Component Java API
- Jetspeed AJAX XML API
- Declarative Security Constraints and JAAS Database Security Policy
- Runtime Portlet API Standard Role-based Security
- Portal Content Management and Navigations: Pages, Menus, Folders, Links
- Multithreaded Aggregation Engine
- PSML Folder CMS Navigations, Menus, Links
- Jetspeed SSO (Single Sign-on)
- Rules-based Profiler for page and resource location
- Integrates with most popular databases including Derby, MySQL, MS SQL, Postgres, Oracle, DB2, Hypersonic
- Client independent capability engine (html, xhtml, wml,vml)
- Internationalization: Localized Portal Resources in 12 Languages
- Statistics Logging Engine
- Portlet Registry
- Full Text Search of Portlet Resources with Lucene
- User Registration
- Forgotten Password
- Rich Login and Password Configuration Management
Download (66.5MB)
Added: 2007-02-06 License: The Apache License Price:
991 downloads
Java::JCR 0.08
Java::JCR is a module to use JSR 170 (JCR) repositories from Perl. more>>
Java::JCR is a module to use JSR 170 (JCR) repositories from Perl.
SYNOPSIS
use Java::JCR;
use Java::JCR::Jackrabbit;
my $repository = Java::JCR::Jackrabbit->new;
my $session = $repository->login(
Java::JCR::SimpleCredentials->new(username, password)
);
my $root = $session->get_root_node;
my $node = $root->add_node(foo, nt:unstructured);
$node->set_property(bar, 10);
$node->set_property(baz, blah);
$node->set_property(qux, 4.8);
$session->save;
The JSR 170 specification describes a Java-based API for access hierarchical databases. This is generally referred to by the abbreviation JCR, which is an abbreviation for Content Repository API for Java Technology Specification.
The biggest OSS implementation, as of this writing, is Jackrabbit, which is a project at the Apache Software Foundation, http://jackrabbit.apache.org/. Currently, this library allows Perl programmers to develop using the JCR and Jackrabbit, though, theres no reason why connectors cant be written for other implementations, such as Jaceira, CRX, eXoplatform, etc. The JCR library wrappers included are not at all specific to Jackrabbit.
<<lessSYNOPSIS
use Java::JCR;
use Java::JCR::Jackrabbit;
my $repository = Java::JCR::Jackrabbit->new;
my $session = $repository->login(
Java::JCR::SimpleCredentials->new(username, password)
);
my $root = $session->get_root_node;
my $node = $root->add_node(foo, nt:unstructured);
$node->set_property(bar, 10);
$node->set_property(baz, blah);
$node->set_property(qux, 4.8);
$session->save;
The JSR 170 specification describes a Java-based API for access hierarchical databases. This is generally referred to by the abbreviation JCR, which is an abbreviation for Content Repository API for Java Technology Specification.
The biggest OSS implementation, as of this writing, is Jackrabbit, which is a project at the Apache Software Foundation, http://jackrabbit.apache.org/. Currently, this library allows Perl programmers to develop using the JCR and Jackrabbit, though, theres no reason why connectors cant be written for other implementations, such as Jaceira, CRX, eXoplatform, etc. The JCR library wrappers included are not at all specific to Jackrabbit.
Download (0.047MB)
Added: 2007-06-04 License: Perl Artistic License Price:
875 downloads
SecureJSH 1.0b0726
SecureJSH makes it possible for server-side Java applications to provide secure shell access to their administrators, users, etc more>>
SecureJSH project enables server side applications written in the Java programming language to provide secure shell access to their administrators, users, developers and service clients, where verbatim syntax of the latest Java programming language can be used - interactively.
SecureJSH needs JDK 6.0 (or later) or JRE 6.0 (or later) with JAVAC on classpath to function.
Security:
SecureJSH implements RFC-4251 SSH 2.0 protocol at the server side, with support of publickey authentication, which is more secure and convenient (no need to enter password every time).
Interactive Execution:
You must first compile traditional Java source code to bytecode before
executing them. But with SecureJSH, the compilation is done transparently so
you just type in arbitrary length of Java statements, then see them get
executed immediately, in context. Context objects are all well kept across
executions, this way you interactively control a live Java application with
the programming language it was writen in.
Verbatim Java Syntax:
Unlike other Java shell supporting tools, SecureJSH leverages JSR-199 Java
compiler API to dynamically compile interactive Java statements. This means you use the EXACTLY same syntax with whatever your applications are writen in, up to the latest Java Language Specification. You can copy & paste code between SecureJSH terminal and your Java project source without problem.
Smart Command Recognization, UNIX Shell Style
Unlike JSR-223 scripting support for the Java language, with which you must
enter the full source of a Java class to execute, SecureJSH is much smarter and
humanized, it prompts you for multi-line input when youve entered incomplete
Java statements, and wraps the statements inside a predefined class structure
for execution. It is a REAL shell.
Non-Interference, Minimum Resource Consumption
SecureJSH has no static resource has to be stored JVM wide, and consume very small amount of resources per instance (with NIO based implementation, all SSH traffics are handled by a single thread). You can run as many shell servers as you wish inside a single JVM, including JVMs of Java application servers.
Commercial Friendly License
SecureJSH is released under a BSD style license. Please read the included
LICENCE.txt for SJSH and third-party license terms.
Enhancements:
- The Java completion algorithm was refined and is more accurate and to the point.
- Rarely used methods like Object.wait() and Object.notify() are filtered out.
- Completion for built-in command options was added - press Tab to complete a command, then Tab again to prompt for common options.
- This works fine with dynamic options (like unimport java.awt.*
- can be entered by uni-[Tab]-j-[Tab], when such an import is in the list).
- The field definition command now takes a type name before a field name, to match the Java variable definition style.
<<lessSecureJSH needs JDK 6.0 (or later) or JRE 6.0 (or later) with JAVAC on classpath to function.
Security:
SecureJSH implements RFC-4251 SSH 2.0 protocol at the server side, with support of publickey authentication, which is more secure and convenient (no need to enter password every time).
Interactive Execution:
You must first compile traditional Java source code to bytecode before
executing them. But with SecureJSH, the compilation is done transparently so
you just type in arbitrary length of Java statements, then see them get
executed immediately, in context. Context objects are all well kept across
executions, this way you interactively control a live Java application with
the programming language it was writen in.
Verbatim Java Syntax:
Unlike other Java shell supporting tools, SecureJSH leverages JSR-199 Java
compiler API to dynamically compile interactive Java statements. This means you use the EXACTLY same syntax with whatever your applications are writen in, up to the latest Java Language Specification. You can copy & paste code between SecureJSH terminal and your Java project source without problem.
Smart Command Recognization, UNIX Shell Style
Unlike JSR-223 scripting support for the Java language, with which you must
enter the full source of a Java class to execute, SecureJSH is much smarter and
humanized, it prompts you for multi-line input when youve entered incomplete
Java statements, and wraps the statements inside a predefined class structure
for execution. It is a REAL shell.
Non-Interference, Minimum Resource Consumption
SecureJSH has no static resource has to be stored JVM wide, and consume very small amount of resources per instance (with NIO based implementation, all SSH traffics are handled by a single thread). You can run as many shell servers as you wish inside a single JVM, including JVMs of Java application servers.
Commercial Friendly License
SecureJSH is released under a BSD style license. Please read the included
LICENCE.txt for SJSH and third-party license terms.
Enhancements:
- The Java completion algorithm was refined and is more accurate and to the point.
- Rarely used methods like Object.wait() and Object.notify() are filtered out.
- Completion for built-in command options was added - press Tab to complete a command, then Tab again to prompt for common options.
- This works fine with dynamic options (like unimport java.awt.*
- can be entered by uni-[Tab]-j-[Tab], when such an import is in the list).
- The field definition command now takes a type name before a field name, to match the Java variable definition style.
Download (MB)
Added: 2007-07-29 License: BSD License Price:
820 downloads
PETALS 1.3
PETALS is an ObjectWeb Java Business Integration (JBI) platform. more>>
PETALS is an ObjectWeb Java Business Integration (JBI) platform. PETALS provides lightweight and packaged integration solutions, based on JSR-208 specifications, with a high focus on distribution and clustering.
PETALS is part of ObjectWeb ESB initiative, and was launched in June 2005 by EBM WebSourcing and Fossil E-Commerce.
The project leverages ObjectWeb architecture and projects like Fractal, JORAM, JOnAS to provide a JBI container with a focus on :
- JBI specification conformance
- Integrate JBI in JOnAS
- Multi JVM, distributed and clustered platform for JBI components with native transport based on existing ObjectWeb middleware : JORAM and Dream
- Propose packaged solutions for process orchestration (with focus on BPEL engine, Transformation engine, Web Services and JMS binding components) and B2B integration (with focus on Transformation and B2B bindng components like EDI, ...)
Enhancements:
- This release contains all the PETALS elements that are useful for integration solutions.
- New features include static definition of the distributed environment (avoiding multicast auto-discovering), an improvement to the Web Administrative console, IBM JVM compatibility, and more Binding components.
<<lessPETALS is part of ObjectWeb ESB initiative, and was launched in June 2005 by EBM WebSourcing and Fossil E-Commerce.
The project leverages ObjectWeb architecture and projects like Fractal, JORAM, JOnAS to provide a JBI container with a focus on :
- JBI specification conformance
- Integrate JBI in JOnAS
- Multi JVM, distributed and clustered platform for JBI components with native transport based on existing ObjectWeb middleware : JORAM and Dream
- Propose packaged solutions for process orchestration (with focus on BPEL engine, Transformation engine, Web Services and JMS binding components) and B2B integration (with focus on Transformation and B2B bindng components like EDI, ...)
Enhancements:
- This release contains all the PETALS elements that are useful for integration solutions.
- New features include static definition of the distributed environment (avoiding multicast auto-discovering), an improvement to the Web Administrative console, IBM JVM compatibility, and more Binding components.
Download (10.5MB)
Added: 2007-06-04 License: LGPL (GNU Lesser General Public License) Price:
874 downloads
Drools 2.1
Drools is a Rules Engine implementation based on Charles Forgys Rete algorithm tailored for the Java language. more>>
Drools is a Rules Engine implementation based on Charles Forgys Rete algorithm tailored for the Java language. Adapting Rete to an object-oriented interface allows for more natural expression of business rules with regards to business objects. Drools is written in Java, but able to run on Java and .Net.
Drools is designed to allow pluggeable language implementations. Currently rules can be written in Java, Python and Groovy. More importantly, Drools provides for Declarative Programming and is flexible enough to match the semantics of your problem domain with Domain Specific Languages (DSL) via XML using a Schema defined for your problem domain.
DSLs consist of XML elements and attributes that represent the problem domain.
Enhancements:
Bug
- DROOLS-294 - WorkingMemory synchronization is not complete (Barry Kaplan)
- DROOLS-314 - MethodMetadataSources need a stopping Class (Barry Kaplan)
- DROOLS-318 - WorkingMemoryEventListenerProcessor implements wrong interface (Barry Kaplan)
- DROOLS-347 - Maven build of drools-spring-jdk5 fails on Mac OS X (Andy Barnett)
- DROOLS-367 - Wrong rule executed when modifying object in workingmemory (Michael Neale)
- DROOLS-374 - Caching of classloaders in causes problems with hot deployment in some J2EE containers (Michael Neale)
- DROOLS-376 - Make source file (c) headers consistent with codehaus (Michael Neale)
- DROOLS-386 - Bug with the Escalation example? (Robert Laflamme)
- DROOLS-401 - Missing semaphore types in schema file (rules.xsd) (Edson Tirelli)
- DROOLS-403 - no-loop incorrectly removes all instances of a rule from the agenda (Michael Neale)
- DROOLS-409 - rename getNoLoop to isNoLoop to obey JavaBean naming convention (Mark Proctor)
- New Feature
- DROOLS-303 - Default rule-method parameter annotation (Barry Kaplan)
- DROOLS-360 - Maven goal for drools-all-src-XXX.zip (Mark Proctor)
- DROOLS-361 - Auto add RuleSet to RuleBase (Barry Kaplan)
- DROOLS-363 - Decision tables in spreadsheets (Michael Neale)
- DROOLS-383 - Integrate java:functions feature in decision tables. (Michael Neale)
- DROOLS-388 - Support for application data (variables), per rule duration, salience and names (Ricardo Rojas)
- DROOLS-408 - Xor Group so only one rule can fire for a specific group (Mark Proctor)
Improvement
- DROOLS-296 - Allow for default id value in parameter annotations (Barry Kaplan)
- DROOLS-297 - Allow multiple consequence annotations per rule (Barry Kaplan)
- DROOLS-301 - Remove Drools prefix from annotations (Barry Kaplan)
- DROOLS-309 - MethodMetadataSource to ignore certain classes (Barry Kaplan)
- DROOLS-310 - Condition sharing for POJO rules (Peter Royal)
- DROOLS-348 - JDK 1.3 no longer supported (Barry Kaplan)
- DROOLS-350 - Utilize 1.4 nested exceptions (Barry Kaplan)
- DROOLS-357 - Packaging between factory and meta needs some attention (Barry Kaplan)
- DROOLS-364 - Update spring libs and config files for 1.2 (Barry Kaplan)
- DROOLS-372 - Update Groovy to JSR-03 (Mark Proctor)
- DROOLS-381 - Add object-condition tests to RuleBuilderTest (Barry Kaplan)
- DROOLS-387 - add ability for a DSL to acces the XML namespace information in a Configuration (James Strachan)
- DROOLS-402 - Refactor maven.xml and drools:dist to make it faster and more intelligent (Mark Proctor)
- DROOLS-410 - Update Janino to 2.3.8 (Mark Proctor)
Test
- DROOLS-346 - Ant build.xml doesnt run drools-jsr94 unit tests (Andy Barnett)
- Task
- DROOLS-351 - Remove drools-annotation and derivitives from 2.1 (Barry Kaplan)
- DROOLS-370 - Add in drools-decisiontables subproject (Michael Neale)
<<lessDrools is designed to allow pluggeable language implementations. Currently rules can be written in Java, Python and Groovy. More importantly, Drools provides for Declarative Programming and is flexible enough to match the semantics of your problem domain with Domain Specific Languages (DSL) via XML using a Schema defined for your problem domain.
DSLs consist of XML elements and attributes that represent the problem domain.
Enhancements:
Bug
- DROOLS-294 - WorkingMemory synchronization is not complete (Barry Kaplan)
- DROOLS-314 - MethodMetadataSources need a stopping Class (Barry Kaplan)
- DROOLS-318 - WorkingMemoryEventListenerProcessor implements wrong interface (Barry Kaplan)
- DROOLS-347 - Maven build of drools-spring-jdk5 fails on Mac OS X (Andy Barnett)
- DROOLS-367 - Wrong rule executed when modifying object in workingmemory (Michael Neale)
- DROOLS-374 - Caching of classloaders in causes problems with hot deployment in some J2EE containers (Michael Neale)
- DROOLS-376 - Make source file (c) headers consistent with codehaus (Michael Neale)
- DROOLS-386 - Bug with the Escalation example? (Robert Laflamme)
- DROOLS-401 - Missing semaphore types in schema file (rules.xsd) (Edson Tirelli)
- DROOLS-403 - no-loop incorrectly removes all instances of a rule from the agenda (Michael Neale)
- DROOLS-409 - rename getNoLoop to isNoLoop to obey JavaBean naming convention (Mark Proctor)
- New Feature
- DROOLS-303 - Default rule-method parameter annotation (Barry Kaplan)
- DROOLS-360 - Maven goal for drools-all-src-XXX.zip (Mark Proctor)
- DROOLS-361 - Auto add RuleSet to RuleBase (Barry Kaplan)
- DROOLS-363 - Decision tables in spreadsheets (Michael Neale)
- DROOLS-383 - Integrate java:functions feature in decision tables. (Michael Neale)
- DROOLS-388 - Support for application data (variables), per rule duration, salience and names (Ricardo Rojas)
- DROOLS-408 - Xor Group so only one rule can fire for a specific group (Mark Proctor)
Improvement
- DROOLS-296 - Allow for default id value in parameter annotations (Barry Kaplan)
- DROOLS-297 - Allow multiple consequence annotations per rule (Barry Kaplan)
- DROOLS-301 - Remove Drools prefix from annotations (Barry Kaplan)
- DROOLS-309 - MethodMetadataSource to ignore certain classes (Barry Kaplan)
- DROOLS-310 - Condition sharing for POJO rules (Peter Royal)
- DROOLS-348 - JDK 1.3 no longer supported (Barry Kaplan)
- DROOLS-350 - Utilize 1.4 nested exceptions (Barry Kaplan)
- DROOLS-357 - Packaging between factory and meta needs some attention (Barry Kaplan)
- DROOLS-364 - Update spring libs and config files for 1.2 (Barry Kaplan)
- DROOLS-372 - Update Groovy to JSR-03 (Mark Proctor)
- DROOLS-381 - Add object-condition tests to RuleBuilderTest (Barry Kaplan)
- DROOLS-387 - add ability for a DSL to acces the XML namespace information in a Configuration (James Strachan)
- DROOLS-402 - Refactor maven.xml and drools:dist to make it faster and more intelligent (Mark Proctor)
- DROOLS-410 - Update Janino to 2.3.8 (Mark Proctor)
Test
- DROOLS-346 - Ant build.xml doesnt run drools-jsr94 unit tests (Andy Barnett)
- Task
- DROOLS-351 - Remove drools-annotation and derivitives from 2.1 (Barry Kaplan)
- DROOLS-370 - Add in drools-decisiontables subproject (Michael Neale)
Download (1.7MB)
Added: 2005-10-03 License: The Apache License 2.0 Price:
1492 downloads
JVending 1.3.10a
JVending is a P2P (JXTA) based mobile content provisioning system. more>>
JVending project bridges P2P networks and wireless delivery of content to mobile devices. Due to high latency of wireless connections, it is not practical to directly hook up the mobile devices to the peer network, so I have taken a different approach with JVending.
A user sets up a personal provisioning server on their PC and hooks it into the network. Through the P2P network, we create a federation of provisioning servers. The mobile devices use the federated provisioning servers as content portals.
JVending differs from P2P systems, such as Gnutella or "Project JXTA" reference implementation, in the following ways. JVending provides:
1. Catalog management
2. Device detection, which delivers the appropriate content based upon the type of browser or device
3. Web based browsing of content, so you can share with your friends on a wired or wireless network, after you have already collected the content.
4. The ability to search for and distribute packaged archives on the peer network.
5. Web links tying together the network.
6. PPG integration for pushing content to mobile devices.
For 2005 - 2006, the major goals of JVending (roughly in order of importance) are:
1. Expanding P2P support, including more in the area of wireless messaging (SMS)
2. JSR-124 compliance
3. Performance testing and monitoring capability
4. Multimedia server and J2ME support. This covers full integration between the MMS Client and the provisioning server.
Setting up the Environment
Follow these steps:
1. Make sure that you have J2SE 1.4.2 JDK installed. If not, go to http://java.sun.com/j2se/1.4.2/download.html and download and install the JDK (not JRE). I have not tested with J2SE 1.5 JDK, so it may or may not work with that version.
2. Download the jvending-standalone.zip file from the JVending project site.
3. Unzip the file into a directory of your choice, say /jvending
4. Set the JAVA_HOME environmental variable, depending on your OS. In windows, you can do this through the Control Panel/System/Advanced/Environmental Variable: JAVA_HOME =
EXAMPLE: JAVA_HOME=c:Programsj2sdk1.4.2_06
Starting JVending
1. Go to the bin directory and click on the run.bat (for windows) or run.sh for Unix.
2. The first time you start JVending, you will see a JXTA Configurator screen show up. Type in your user name and password/verify password. Click OK.
3. Wait 10 seconds for JVending to finish its startup sequence and then go to http://localhost:80/jvending/login. If you get a 404 error, wait a few more seconds and try again. Login ID/Password: admin/admin. Click "Submit Query" button. You will now see the JVending home page.
<<lessA user sets up a personal provisioning server on their PC and hooks it into the network. Through the P2P network, we create a federation of provisioning servers. The mobile devices use the federated provisioning servers as content portals.
JVending differs from P2P systems, such as Gnutella or "Project JXTA" reference implementation, in the following ways. JVending provides:
1. Catalog management
2. Device detection, which delivers the appropriate content based upon the type of browser or device
3. Web based browsing of content, so you can share with your friends on a wired or wireless network, after you have already collected the content.
4. The ability to search for and distribute packaged archives on the peer network.
5. Web links tying together the network.
6. PPG integration for pushing content to mobile devices.
For 2005 - 2006, the major goals of JVending (roughly in order of importance) are:
1. Expanding P2P support, including more in the area of wireless messaging (SMS)
2. JSR-124 compliance
3. Performance testing and monitoring capability
4. Multimedia server and J2ME support. This covers full integration between the MMS Client and the provisioning server.
Setting up the Environment
Follow these steps:
1. Make sure that you have J2SE 1.4.2 JDK installed. If not, go to http://java.sun.com/j2se/1.4.2/download.html and download and install the JDK (not JRE). I have not tested with J2SE 1.5 JDK, so it may or may not work with that version.
2. Download the jvending-standalone.zip file from the JVending project site.
3. Unzip the file into a directory of your choice, say /jvending
4. Set the JAVA_HOME environmental variable, depending on your OS. In windows, you can do this through the Control Panel/System/Advanced/Environmental Variable: JAVA_HOME =
EXAMPLE: JAVA_HOME=c:Programsj2sdk1.4.2_06
Starting JVending
1. Go to the bin directory and click on the run.bat (for windows) or run.sh for Unix.
2. The first time you start JVending, you will see a JXTA Configurator screen show up. Type in your user name and password/verify password. Click OK.
3. Wait 10 seconds for JVending to finish its startup sequence and then go to http://localhost:80/jvending/login. If you get a 404 error, wait a few more seconds and try again. Login ID/Password: admin/admin. Click "Submit Query" button. You will now see the JVending home page.
Download (18.4MB)
Added: 2005-04-20 License: LGPL (GNU Lesser General Public License) Price:
1649 downloads
JNode 0.2.4
JNode is a simple to use and install Java operating system for personal use. more>>
JNode is a simple to use and install Java operating system for personal use.
It runs on modern devices.
Any java application will run on it, fast & secure! JNode is open source and uses the LGPL license.
This release has taken way too much time, but is finally here!
It contains lots of changes on many areas of JNode. Most important changes are about the massive improvements of the GUI and the Classpath runtime library.
Besides these changes, a lot of changes have to to with the inner workings of the JNode virtual machine.
To make it easier to try JNode, this release comes with a VMWare player configuration file. Install VMWare player, download the compressed iso image, uncompress it, download the VMX file and run it.
Enhancements:
- Basic support for development under JNode javac command, included with the use of Eclipse JDT compiler Integrated standard java tools: jar, native2ascii, serialver etc. from GNU Classpath Text console improvements Swing based console New textconsole based editor JFat - a FAT32 file system implementation RamFS - a simple in-memory file system FTPFS - a read-only FTP based file system Many classpath patches ImageIO support for PNG, GIF and BMP images from GNU Classpath BDF font support Changable desktop Look & Feel Isolate (JSR 121), not fully supported Simple webserver under JNode Various bugfixes in the resource loading, ISO9660, socket writing Download of JNode can be done at www.jnode.org/node/### More information can be found at www.jnode.org or http://sourceforge.net/projects/jnode
<<lessIt runs on modern devices.
Any java application will run on it, fast & secure! JNode is open source and uses the LGPL license.
This release has taken way too much time, but is finally here!
It contains lots of changes on many areas of JNode. Most important changes are about the massive improvements of the GUI and the Classpath runtime library.
Besides these changes, a lot of changes have to to with the inner workings of the JNode virtual machine.
To make it easier to try JNode, this release comes with a VMWare player configuration file. Install VMWare player, download the compressed iso image, uncompress it, download the VMX file and run it.
Enhancements:
- Basic support for development under JNode javac command, included with the use of Eclipse JDT compiler Integrated standard java tools: jar, native2ascii, serialver etc. from GNU Classpath Text console improvements Swing based console New textconsole based editor JFat - a FAT32 file system implementation RamFS - a simple in-memory file system FTPFS - a read-only FTP based file system Many classpath patches ImageIO support for PNG, GIF and BMP images from GNU Classpath BDF font support Changable desktop Look & Feel Isolate (JSR 121), not fully supported Simple webserver under JNode Various bugfixes in the resource loading, ISO9660, socket writing Download of JNode can be done at www.jnode.org/node/### More information can be found at www.jnode.org or http://sourceforge.net/projects/jnode
Download (92MB)
Added: 2006-10-07 License: LGPL (GNU Lesser General Public License) Price:
1114 downloads
Shotoku 1.0 Alpha3
Shotoku is designed to provide easy access to content repositories. more>>
Shotoku is designed to provide easy access to content repositories in which you can store data, revision content, bind metadata, and provide branching and merging strategies.
This means Shotoku can interface with repositories such as the Java Content Repository (JSR 170: JCR), Subversion, and file-system based repository implementations that aim to support basic revisioning mechanisms.
Main features:
- Three content managers: the first and default SVN-based, JCR-based and a local file system repository.
- Because a local working copy is present, data reading is very fast (SVN repository implementation).
- Data writing is reliable, because data is sent straight to the repository, without touching the working copy (SVN repository implementation).
- Shotoku can work in "embedded" mode in stand-alone applications, as well as a component in an application server.
- Shotoku allows you to "inject" content into any POJO using annotations (currently supported only in app server mode). POJOs which are Shotoku aware are automatically updated when a user updates a node in a Subversion repository Shotoku is configured to reference. Content can be anything and there are no structural requirements placed on the repository - even existing Subversion repositories can be referenced by Shotoku without modification.
- A simple search mechanism.
- Integeration with Apache Velocity - you can easily store templates in Shotoku to create higher level application features such as content and blog engines.
- Feeds component - automatic generation of rss, atom and rdf feeds/ podcasts, configured through a xml file, together with arbitrary feeds aggregation. You can see feeds already at work on JBoss Labs - just click the "Feeds" link in navigation or simply here.
- Blog component.
- A simple cache with "renewable" values - a value can be updated on regular intervals of time or when some of watched resources in a content manager change (see wiki for details).
<<lessThis means Shotoku can interface with repositories such as the Java Content Repository (JSR 170: JCR), Subversion, and file-system based repository implementations that aim to support basic revisioning mechanisms.
Main features:
- Three content managers: the first and default SVN-based, JCR-based and a local file system repository.
- Because a local working copy is present, data reading is very fast (SVN repository implementation).
- Data writing is reliable, because data is sent straight to the repository, without touching the working copy (SVN repository implementation).
- Shotoku can work in "embedded" mode in stand-alone applications, as well as a component in an application server.
- Shotoku allows you to "inject" content into any POJO using annotations (currently supported only in app server mode). POJOs which are Shotoku aware are automatically updated when a user updates a node in a Subversion repository Shotoku is configured to reference. Content can be anything and there are no structural requirements placed on the repository - even existing Subversion repositories can be referenced by Shotoku without modification.
- A simple search mechanism.
- Integeration with Apache Velocity - you can easily store templates in Shotoku to create higher level application features such as content and blog engines.
- Feeds component - automatic generation of rss, atom and rdf feeds/ podcasts, configured through a xml file, together with arbitrary feeds aggregation. You can see feeds already at work on JBoss Labs - just click the "Feeds" link in navigation or simply here.
- Blog component.
- A simple cache with "renewable" values - a value can be updated on regular intervals of time or when some of watched resources in a content manager change (see wiki for details).
Download (5.7MB)
Added: 2006-05-31 License: GPL (GNU General Public License) Price:
1241 downloads
GvTags 0.3.0
GvTags is a lightweight yet powerful tag library and template engine for the dynamic programming language Groovy. more>>
GvTags is a lightweight yet powerful tag library and template engine for the dynamic programming language Groovy.
The tag library can be used to generate Web pages with powerful tag support. GvTags can be used with the template servlet of GvTags (TagTemplateServlet) or with JavaServer Pages (JSP).
The template engine can be used to generate any kind of text documents. Since it is written in Groovy and compiled to a Java class file, it can be used from Groovy as well as from Java.
Enhancements:
- GvTags now has a command line script to start GvTags.
- It contains an ant task to include the TagTemplateEngine in ant scripts.
- An HTTP server based on jetty is embedded.
- You can download an all-in-one distribution, which contains everything to run GvTags.
- Migration to Groovy 1.0 JSR 06, performance improvements, and the case tag now uses the isCase() method.
<<lessThe tag library can be used to generate Web pages with powerful tag support. GvTags can be used with the template servlet of GvTags (TagTemplateServlet) or with JavaServer Pages (JSP).
The template engine can be used to generate any kind of text documents. Since it is written in Groovy and compiled to a Java class file, it can be used from Groovy as well as from Java.
Enhancements:
- GvTags now has a command line script to start GvTags.
- It contains an ant task to include the TagTemplateEngine in ant scripts.
- An HTTP server based on jetty is embedded.
- You can download an all-in-one distribution, which contains everything to run GvTags.
- Migration to Groovy 1.0 JSR 06, performance improvements, and the case tag now uses the isCase() method.
Download (1.9MB)
Added: 2006-07-17 License: The Apache License 2.0 Price:
1194 downloads
jo! 1.1 beta1
jo! is a pure Java Web server that implements the Servlet API, JSP, and HTTP/1.1. more>>
jo! is a pure Java Web server that implements the Servlet API, JSP, and HTTP/1.1. It features advanced thread management, virtual hosts, memory-sensitive file cache, authentication using a role abstraction, automatic compressed transfer of text or HTML files, auto internationalization, auto servlet and JSP reloading, auto reload of WARs, hot deployment of WARs, JSR-45 support, and an easy-to-use Swing console.
Main features:
- HTTP/1.1 including byte-ranges, auto-chunking, pipelining, etc.
- Servlet API 2.2 (2.3 starting with jo! 1.1)
- JSP 1.1 (1.2 starting with jo! 1.1)
- Auto reload of WARs
- Hot deployment of WARs
- Drag and drop deployment of WARs
- Auto internationalization
- Auto servlet and jsp reloading
- Easy to use Swing console
- Advanced thread management
- Memory sensitive file cache
- Automatic compressed transfer of text or html files
- Virtual hosts
- Mac OS X support
- Embeddable
<<lessMain features:
- HTTP/1.1 including byte-ranges, auto-chunking, pipelining, etc.
- Servlet API 2.2 (2.3 starting with jo! 1.1)
- JSP 1.1 (1.2 starting with jo! 1.1)
- Auto reload of WARs
- Hot deployment of WARs
- Drag and drop deployment of WARs
- Auto internationalization
- Auto servlet and jsp reloading
- Easy to use Swing console
- Advanced thread management
- Memory sensitive file cache
- Automatic compressed transfer of text or html files
- Virtual hosts
- Mac OS X support
- Embeddable
Download (3.8MB)
Added: 2005-07-07 License: GPL (GNU General Public License) Price:
1569 downloads
Apache Jackrabbit 1.1.1
Apache Jackrabbit project is a fully conforming implementation of the Content Repository for Java Technology API (JCR). more>>
Apache Jackrabbit project is a fully conforming implementation of the Content Repository for Java Technology API (JCR).
A content repository is a hierarchical content store with support for structured and unstructured content, full text search, versioning, transactions, observation, and more.
Typical applications that use content repositories include content management, document management, and records management systems.
Version 1.0 of the JCR API was specified by the Java Specification Request 170 (JSR 170) and work on the JCR version 2.0 has begun in JSR 283.
Apache Jackrabbit is a project of the Apache Software Foundation.
Enhancements:
- Apache Jackrabbit 1.1.1 is a patch release that fixes a number of issues, see the included change history for details.
- No new features or configuration changes have been introduced since the 1.1 release.
<<lessA content repository is a hierarchical content store with support for structured and unstructured content, full text search, versioning, transactions, observation, and more.
Typical applications that use content repositories include content management, document management, and records management systems.
Version 1.0 of the JCR API was specified by the Java Specification Request 170 (JSR 170) and work on the JCR version 2.0 has begun in JSR 283.
Apache Jackrabbit is a project of the Apache Software Foundation.
Enhancements:
- Apache Jackrabbit 1.1.1 is a patch release that fixes a number of issues, see the included change history for details.
- No new features or configuration changes have been introduced since the 1.1 release.
Download (MB)
Added: 2007-01-10 License: The Apache License 2.0 Price:
1026 downloads
Jiplet Container 0.1.0b
Jiplet is short for Java SIP Servlet. more>>
Jiplet is short for Java SIP Servlet. Jiplet Container project is an open-source container for server-side SIP applications. An application developer can create a SIP application written in Java using the Jiplet API and deploy the application in the container.
The container provides a number of framework services including support for SIP message parsing and formatting, scoped variables, authentication and authroization, thread-pooling, logging, custom class loading, management interface, etc. It enables application developer to create server-side SIP applications using a component-based model similar to that envisioned by the J2EE architecture.
In fact, it fits very well with the J2EE paradigm for software development and deployment. The jiplet container software can either be run as a standalone Java application or deployed as a service residing in a J2EE server. When running as a J2EE service, the jiplet container can access many of the features offered by the J2EE server.
In addition, The jiplet container is built with the service provider model in mind. In this model, a service provider can host customized SIP applications from their customers in a secure manner similar to the servlet hosting offered by many service providers.
The jiplet container is very similar to a Java HTTP servlet container in concept. A Java HTTP servlet is a Java class that handles HTTP messages from web browsers. Similarly, a jiplet is a Java class that handles SIP messages from SIP user agents (SIP phones and SIP servers).
A servlet container like Apache Tomcat can host one or more web applications (contexts), each consisting of one or more servlets. Similarly, the jiplet container can host one or more SIP applications (contexts) consisting of one or more jiplets.
Similar to the servlet API authored by Sun Microsystems, the jiplet container provides a set of Java classes that jiplet applications extend or use. The services provided by these classes are very similar to those of the servlet API including scoped variables, request forwarding from one jiplet to another, etc.
As in a servlet container, new jiplet applications, or contexts, can be deployed using a zipped file called spr (war is the Java servlet terminology). Since there are differences between the HTTP and SIP protocols, the servlet and the jiplet containers have some notable differences.
However, the jiplet is not a formal specification like the servlet specification. It is also not an implementation of the SIP servlet specification (JSR 116) authored by Sun and its community of users. There are many similarities between the jiplet and the SIP servlet in terms of features. If you are familiar with SIP servlets, you will feel right at home with the jiplet container.
We are planning to continue developing the jiplet container based on feedback provided by that the open-source community. We are hoping that open-source developers will extend this tool and the specification instead of a committee.
Main features:
- Open-source API for developing server-side SIP applications. Based on the JAIN-SIP API.
- Offers component-based development model.
- Servlet-like development and runtime environment.
- Access to powerful JAIN-API from SIP applications.
- JMX management interface for interfacing with management systems.
- Web-based user interface for managing jiplet applications.
- Support for scoped variables including application, session, request, transaction and dialog-scoped variables.
- Support for forwarding SIP messages from one jiplet to another.
- Container-managed authentication and authorization.
- Support for application timers.
- Can run as a standalone application or it can be integrated with JBOSS as a J2EE service.
- Comprehensive support for the service-provider model.
Enhancements:
- The final release (version 1.2) of the NIST SIP stack Reference Implementation has been incorporated into the Jiplet Container and reference applications.
- The new listening point architecture has been integrated into the Jiplet Container SIP connector.
- One connector can now use more than one IP address for SIP messaging.
- Convenience methods have been added to the Jiplet class for jiplet developers to handle additional listening points and SIP providers.
- The Jiplet Container message proxying has been updated to work in a multi-homed environment.
- The software has been tested with Jboss 4.0.5.GA.
<<lessThe container provides a number of framework services including support for SIP message parsing and formatting, scoped variables, authentication and authroization, thread-pooling, logging, custom class loading, management interface, etc. It enables application developer to create server-side SIP applications using a component-based model similar to that envisioned by the J2EE architecture.
In fact, it fits very well with the J2EE paradigm for software development and deployment. The jiplet container software can either be run as a standalone Java application or deployed as a service residing in a J2EE server. When running as a J2EE service, the jiplet container can access many of the features offered by the J2EE server.
In addition, The jiplet container is built with the service provider model in mind. In this model, a service provider can host customized SIP applications from their customers in a secure manner similar to the servlet hosting offered by many service providers.
The jiplet container is very similar to a Java HTTP servlet container in concept. A Java HTTP servlet is a Java class that handles HTTP messages from web browsers. Similarly, a jiplet is a Java class that handles SIP messages from SIP user agents (SIP phones and SIP servers).
A servlet container like Apache Tomcat can host one or more web applications (contexts), each consisting of one or more servlets. Similarly, the jiplet container can host one or more SIP applications (contexts) consisting of one or more jiplets.
Similar to the servlet API authored by Sun Microsystems, the jiplet container provides a set of Java classes that jiplet applications extend or use. The services provided by these classes are very similar to those of the servlet API including scoped variables, request forwarding from one jiplet to another, etc.
As in a servlet container, new jiplet applications, or contexts, can be deployed using a zipped file called spr (war is the Java servlet terminology). Since there are differences between the HTTP and SIP protocols, the servlet and the jiplet containers have some notable differences.
However, the jiplet is not a formal specification like the servlet specification. It is also not an implementation of the SIP servlet specification (JSR 116) authored by Sun and its community of users. There are many similarities between the jiplet and the SIP servlet in terms of features. If you are familiar with SIP servlets, you will feel right at home with the jiplet container.
We are planning to continue developing the jiplet container based on feedback provided by that the open-source community. We are hoping that open-source developers will extend this tool and the specification instead of a committee.
Main features:
- Open-source API for developing server-side SIP applications. Based on the JAIN-SIP API.
- Offers component-based development model.
- Servlet-like development and runtime environment.
- Access to powerful JAIN-API from SIP applications.
- JMX management interface for interfacing with management systems.
- Web-based user interface for managing jiplet applications.
- Support for scoped variables including application, session, request, transaction and dialog-scoped variables.
- Support for forwarding SIP messages from one jiplet to another.
- Container-managed authentication and authorization.
- Support for application timers.
- Can run as a standalone application or it can be integrated with JBOSS as a J2EE service.
- Comprehensive support for the service-provider model.
Enhancements:
- The final release (version 1.2) of the NIST SIP stack Reference Implementation has been incorporated into the Jiplet Container and reference applications.
- The new listening point architecture has been integrated into the Jiplet Container SIP connector.
- One connector can now use more than one IP address for SIP messaging.
- Convenience methods have been added to the Jiplet class for jiplet developers to handle additional listening points and SIP providers.
- The Jiplet Container message proxying has been updated to work in a multi-homed environment.
- The software has been tested with Jboss 4.0.5.GA.
Download (15.2MB)
Added: 2006-09-04 License: GPL (GNU General Public License) Price:
1150 downloads
Apache Pluto 1.0.1
Pluto is the reference implementation of the Java Portlet Specification (JSR-168). more>>
Pluto is the Reference Implementation of the Java Portlet Specfication. The current version of this specification is JSR 168.
Portlets are designed to run in the context of a portal. They are written to the Portlet API which are similar to the Servlet API.
In contrast to servlets, portlets may not do things like sending redirects or errors to browsers directly, forwarding requests or writing arbitrary markup to the output stream to assure that they don?t distract the portal web application which uses them.
Another difference compared to servlets is that portlets rely on portal specific infrastructure functions such as access to user profile information, standard interface for storing/retrieving persistent settings, getting client information, etc. Generally,
portlets are administrated more dynamically than servlets typically are.
A portlet container provides a runtime environment for portlets implemented according to the Portlet API. In this environment portlets can be instantiated, used and finally destroyed. The portlet container is not a stand-alone container like the servlet container; instead it is implemented as a thin layer on top of the servlet container and reuses the functionality provided by the servlet container.
Pluto serves as portlet container that implements the Portlet API and offers developers a working example platform from which they can test their portlets. However, its cumbersome to execute and test the portlet container without a driver, in this case, the portal.
Plutos simple portal component is built only on the portlet containers and the JSR 168s requirements. (In contrast, the more sophisticated, Jetspeed project concentrates on the portal itself rather than the portlet container, and considers requirements from other groups.)
Enhancements:
- Added Pluto 1.1 index page and basic documentation
- PLUTO 164: response contentType can change after getWriter()
- PLUTO 155: URL encoding in pluto 1.0.1-RC4 issue when using apache with jk2
- PLUTO 157: portlet.tld taglib is using jsp version 1.1. JSR168 spec requires JSP version 1.2
- PLUTO 152: Support maven deployment to a remote repository
- PLUTO 130: portlet:namespace fails inside JSTL c:set
- PLUTO-107: Admin portlet fails to add page. Hot deployment now supported.
- PLUTO-92: Deployer strips elements from web.xml (Deploy War Portlet)
<<lessPortlets are designed to run in the context of a portal. They are written to the Portlet API which are similar to the Servlet API.
In contrast to servlets, portlets may not do things like sending redirects or errors to browsers directly, forwarding requests or writing arbitrary markup to the output stream to assure that they don?t distract the portal web application which uses them.
Another difference compared to servlets is that portlets rely on portal specific infrastructure functions such as access to user profile information, standard interface for storing/retrieving persistent settings, getting client information, etc. Generally,
portlets are administrated more dynamically than servlets typically are.
A portlet container provides a runtime environment for portlets implemented according to the Portlet API. In this environment portlets can be instantiated, used and finally destroyed. The portlet container is not a stand-alone container like the servlet container; instead it is implemented as a thin layer on top of the servlet container and reuses the functionality provided by the servlet container.
Pluto serves as portlet container that implements the Portlet API and offers developers a working example platform from which they can test their portlets. However, its cumbersome to execute and test the portlet container without a driver, in this case, the portal.
Plutos simple portal component is built only on the portlet containers and the JSR 168s requirements. (In contrast, the more sophisticated, Jetspeed project concentrates on the portal itself rather than the portlet container, and considers requirements from other groups.)
Enhancements:
- Added Pluto 1.1 index page and basic documentation
- PLUTO 164: response contentType can change after getWriter()
- PLUTO 155: URL encoding in pluto 1.0.1-RC4 issue when using apache with jk2
- PLUTO 157: portlet.tld taglib is using jsp version 1.1. JSR168 spec requires JSP version 1.2
- PLUTO 152: Support maven deployment to a remote repository
- PLUTO 130: portlet:namespace fails inside JSTL c:set
- PLUTO-107: Admin portlet fails to add page. Hot deployment now supported.
- PLUTO-92: Deployer strips elements from web.xml (Deploy War Portlet)
Download (11.6MB)
Added: 2005-10-20 License: The Apache License 2.0 Price:
1471 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 2
- 1
- 2
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above jsr 170 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
