Coldbeans Software - your store for web components
1. Calendar-servletWAP/WML Live demo
2. ForumWAP/WML Live demo
3. NewsWAP/WML Live demo
4. wwwboardWAP/WML Live demo
5. MessageBoardWAP/WML Live demo
6. ChatServletWAP/WML Live demo
7. Co-browse Servlet
8. Community ServletWAP/WML
9. WebPop-servlet
10. WebMail-servlet
11. MailBoard-servlet
From our users: "Must commend you on a fantastic suite of servets etc.
Very very good."
12. Load balance
13. Protect servlets
14. HTTP proxy servlet
15. Error message servlet
16. File manager
17. ArcManager-servlet
18. ShellServletWAP/WML
19. WAPpingWAP/WML
20. WebTestWAP/WML
21. WAPHeadWAP/WML
From our users: "awesome support and awesome servlets!"
22. Mbox-servlet
23. WebLog-servlet Live demo
24. Slide servlet Live demo
25. TreeView-servlet
26. Classifieds
27. Portal servlet
Tuesday, January 31, 2006
Saturday, January 21, 2006
Thursday, January 19, 2006
AgileTrack - Agile/Extreme Programming Iteration and Task Tracking Tool
AgileTrack - Agile/Extreme Programming Iteration and Task Tracking Tool: "AgileTrack is an open-source Java based application for tracking software development in agile development or extreme programming (XP) teams. It includes support for managing stories and other issues, sub-tasks, tracking time, managing multiple projects, planning iterations, and providing iteration reports. It provides a unique interface that is simple to use and allows software developers to have task information always at their fingertips."
Tuesday, January 17, 2006
subclipse.tigris.org
subclipse.tigris.org
There are three projects hosted on this site:
* Subclipse is an Eclipse plugin that adds Subversion integration to the Eclipse IDE. Subclipse is licensed under the terms of the Common Public License (CPL) 1.0.
* svnClientAdapter is a high-level Java API for Subversion and is used by Subclipse. svnClientAdapter is licensed under the terms of the Apache Software License 2.0
* svnAnt is an Ant task that uses svnClientAdapter and provides access to Subversion from Ant scripts. svnAnt is licensed under the terms of the Apache Software License 1.1
There are three projects hosted on this site:
* Subclipse is an Eclipse plugin that adds Subversion integration to the Eclipse IDE. Subclipse is licensed under the terms of the Common Public License (CPL) 1.0.
* svnClientAdapter is a high-level Java API for Subversion and is used by Subclipse. svnClientAdapter is licensed under the terms of the Apache Software License 2.0
* svnAnt is an Ant task that uses svnClientAdapter and provides access to Subversion from Ant scripts. svnAnt is licensed under the terms of the Apache Software License 1.1
AntDoc web site
AntDoc web site: "AnDoc is an automatic Ant script documentation generation, in the same spirit as the must JavaDoc. This documentation enables to directly execute Ant build files. AntDoc is an Ant task.
AntDoc has now a GUI named AntDocGUI, which is a well featured Ant target runner."
AntDoc has now a GUI named AntDocGUI, which is a well featured Ant target runner."
Monday, January 16, 2006
Active JMS
Active JMS: "Activating Java Message Services!
The Java Message Service 1.0.2 API has become the standard for MOM products large and small and its implementation ranges from expensive commercial products to freeware and even open source projects. As its name suggests, however, it only provides a standard Java API. This means that:
* There are no widely accepted standardized, non-Java, non-proprietary messaging APIs.
* Support for non-Java access to many JMS systems is very limited.
These two facts often present a problem for an organization, as they often need to have non-Java clients participate in a JMS network. Until now these organizations had few choices—they could use the JMS vendor’s proprietary ActiveX client (if the vendor offered one), or they could use a general purpose 3rd party Java-ActiveX integration tool. Neither of these solutions is ideal, however, because they are contrary to the ‘open’ nature of the JMS specification itself. You get tied down to a particular vender once again!
The Active JMS open source project was created to solve this problem by offering a freely available, non-proprietary, open source ActiveX JMS client API. With it, you can access a large majority of the JMS functionality without compromise."
The Java Message Service 1.0.2 API has become the standard for MOM products large and small and its implementation ranges from expensive commercial products to freeware and even open source projects. As its name suggests, however, it only provides a standard Java API. This means that:
* There are no widely accepted standardized, non-Java, non-proprietary messaging APIs.
* Support for non-Java access to many JMS systems is very limited.
These two facts often present a problem for an organization, as they often need to have non-Java clients participate in a JMS network. Until now these organizations had few choices—they could use the JMS vendor’s proprietary ActiveX client (if the vendor offered one), or they could use a general purpose 3rd party Java-ActiveX integration tool. Neither of these solutions is ideal, however, because they are contrary to the ‘open’ nature of the JMS specification itself. You get tied down to a particular vender once again!
The Active JMS open source project was created to solve this problem by offering a freely available, non-proprietary, open source ActiveX JMS client API. With it, you can access a large majority of the JMS functionality without compromise."
OpenJMS - OpenJMS
OpenJMS - OpenJMS: "OpenJMS is an open source implementation of Sun Microsystems's Java Message Service API 1.1 Specification
Features
* Point-to-Point and publish-subscribe messaging models
* Guaranteed delivery of messages
* Synchronous and asynchronous message delivery
* Persistence using JDBC
* Local transactions
* Message filtering using SQL92-like selectors
* Authentication
* Administration GUI
* XML-based configuration files
* In-memory and database garbage collection
* Automatic client disconnection detection
* Applet support
* Integrates with Servlet containers such as Jakarta Tomcat
* Support for TCP, RMI, HTTP and SSL protocol stacks
* Support for large numbers of destinations and subscribers"
Features
* Point-to-Point and publish-subscribe messaging models
* Guaranteed delivery of messages
* Synchronous and asynchronous message delivery
* Persistence using JDBC
* Local transactions
* Message filtering using SQL92-like selectors
* Authentication
* Administration GUI
* XML-based configuration files
* In-memory and database garbage collection
* Automatic client disconnection detection
* Applet support
* Integrates with Servlet containers such as Jakarta Tomcat
* Support for TCP, RMI, HTTP and SSL protocol stacks
* Support for large numbers of destinations and subscribers"
Thursday, January 12, 2006
jManage - Web and Command Line Based JMX Client
jManage - Web and Command Line Based JMX Client: "jManage is a open source, web and command-line based JMX client, which provides a centralized console for managing application clusters and distributed-application environments. jManage goes beyond an ordinary JMX client by providing features like Alerts, Graphs, Security, SNMP support, etc. The jManage mission is to provide an open source management platform, which can be used to manage and monitor complete production environment.
jManage is successfully being used by various companies, in Development, QA, Staging and Production environments. It is very easy to setup jManage. Download now and get started. "
jManage is successfully being used by various companies, in Development, QA, Staging and Production environments. It is very easy to setup jManage. Download now and get started. "
JMX4Ant
JMX4Ant
Welcome to the JMX4Ant. JMX4Ant is a set of optional Ant tasks that allows interactions with JMX MBeans.
Like many other programmers, I find Ant to be an extremely handy tool to use in automating away the daily drudgery of routine development tasks. In J2EE development, one kind of drudgery that I have a special dislike for is the creation and management of J2EE resources that my applications depend upon.
My motivation therefore was to provide tasks for J2EE resource creation and management from Ant that I use to build/deploy application. (e.g. create my JDBC pool and JMS queues/topics before I deploy my entity and message driven beans...), but the tasks are general enough for much broader use (i.e. general purpose J2EE server and application administration).
If you have questions, comments, or suggestions for improvements please feel free to contact me directly, or post to one of the JMX4Ant lists on Sourceforge.
Version 1.2 of JMX4Ant contains a number of important new features and some bug fixes as well. One of the most requested enhancements for JMX4Ant that is now part of v1.2 is support for WebLogic's Targets property, and addTarget method. This enhancement allows JMX4Ant to deploy and undeploy the resources that are created to a particular target server. For more information on v1.2 features, refer to the Change History section of this document.
Welcome to the JMX4Ant. JMX4Ant is a set of optional Ant tasks that allows interactions with JMX MBeans.
Like many other programmers, I find Ant to be an extremely handy tool to use in automating away the daily drudgery of routine development tasks. In J2EE development, one kind of drudgery that I have a special dislike for is the creation and management of J2EE resources that my applications depend upon.
My motivation therefore was to provide tasks for J2EE resource creation and management from Ant that I use to build/deploy application. (e.g. create my JDBC pool and JMS queues/topics before I deploy my entity and message driven beans...), but the tasks are general enough for much broader use (i.e. general purpose J2EE server and application administration).
If you have questions, comments, or suggestions for improvements please feel free to contact me directly, or post to one of the JMX4Ant lists on Sourceforge.
Version 1.2 of JMX4Ant contains a number of important new features and some bug fixes as well. One of the most requested enhancements for JMX4Ant that is now part of v1.2 is support for WebLogic's Targets property, and addTarget method. This enhancement allows JMX4Ant to deploy and undeploy the resources that are created to a particular target server. For more information on v1.2 features, refer to the Change History section of this document.
jvmstat
jvmstat: "The jvmstat technology adds light weight performance and configuration instrumentation to the HotSpot JVM and provides a set of monitoring APIs and tools for monitoring the performance of the HotSpot JVM in production environments. The instrumentation is designed such that it is 'always on', yet has negligible performance impact. The monitoring interfaces added to the HotSpot JVM are proprietary and may or may not be supported in future versions of the HotSpot JVM.
* Introduction
* HotSpot™ Monitoring Tools and Utilities
* Download
* Installation
* Instrumentation
* Support (including the jvmstat FAQ)"
* Introduction
* HotSpot™ Monitoring Tools and Utilities
* Download
* Installation
* Instrumentation
* Support (including the jvmstat FAQ)"
The JTR Java Test Runner Project
The JTR Java Test Runner Project: "JTR, acronym for Java Test Runner, is a Java framework that helps developers in building stress test suites. JTR has been devised with some targets in mind:
*
ease of use
*
extendability
*
high configurability
*
modularity
*
rapid development
*
providing J2EE developers with those facilities they usually need
*
ready to use logging facilities
*
Inversion of Control: let the JTR framework inject runtime properties into your runners
*
complete control of the exceptions potentially raised during your test runs
I decided to start devising & coding JTR since I was looking for a framework that could have helped me in building a complex J2EE test environment. The need came out one day at work: I had to stress test a J2EE application and after looking around for suitable testing frameworks I simply decided to start out writing my own one. This approach does not means the JTR framework either is or will be closed with respect to other testing frameworks. Infact it is my firm willing to integrate it with the most popular ones out there nowadays in the next future.
More information covering the most interesting details of the aims sketched above is provided in the reminder of this document (Project Details)."
*
ease of use
*
extendability
*
high configurability
*
modularity
*
rapid development
*
providing J2EE developers with those facilities they usually need
*
ready to use logging facilities
*
Inversion of Control: let the JTR framework inject runtime properties into your runners
*
complete control of the exceptions potentially raised during your test runs
I decided to start devising & coding JTR since I was looking for a framework that could have helped me in building a complex J2EE test environment. The need came out one day at work: I had to stress test a J2EE application and after looking around for suitable testing frameworks I simply decided to start out writing my own one. This approach does not means the JTR framework either is or will be closed with respect to other testing frameworks. Infact it is my firm willing to integrate it with the most popular ones out there nowadays in the next future.
More information covering the most interesting details of the aims sketched above is provided in the reminder of this document (Project Details)."
Tuesday, January 10, 2006
Quartz - Quartz Overview
Quartz - Quartz Overview: "Quartz is a full-featured, open source job scheduling system that can be integrated with, or used along side virtually any J2EE or J2SE application - from the smallest stand-alone application to the largest e-commerce system. Quartz can be used to create simple or complex schedules for executing tens, hundreds, or even tens-of-thousands of jobs; jobs whose tasks are defined as standard Java components or EJBs. The Quartz Scheduler includes many enterprise-class features, such as JTA transactions and clustering.
Quartz is freely usable, licensed under the Apache 2.0 license."
Quartz is freely usable, licensed under the Apache 2.0 license."
Monday, January 09, 2006
dbdoclet Homepage
dbdoclet Homepage: "The DocBook Doclet (dbdoclet) creates DocBook code from Java source documentation. It is helpful, if you want to print reference handbooks of your API. The program can be used as javadoc doclet or as standalone application. The standalone application can be used as a converter to transform HTML documents to DocBook documents. Additionally DocBookDoclet comes with a Swing application called dbdoclet.TiDBit, which helps you to manage your documentation projects and to create PDF files."
XStream - About XStream
XStream - About XStream: "XStream is a simple library to serialize objects to XML and back again.
Features
* Ease of use. A high level facade is supplied that simplifies common use cases.
* No mappings required. Most objects can be serialized without need for specifying mappings.
* Performance. Speed and low memory footprint are a crucial part of the design, making it suitable for large object graphs or systems with high message throughput.
* Clean XML. No information is duplicated that can be obtained via reflection. This results in XML that is easier to read for humans and more compact than native Java serialization.
* Requires no modifications to objects. Serializes internal fields, including private and final. Supports non-public and inner classes. Classes are not required to have default constructor.
* Full object graph support. Duplicate references encountered in the object-model will be maintained. Supports circular references.
* Integrates with other XML APIs. By implementing an interface, XStream can serialize directly to/from any tree structure (not just XML).
* Customizable conversion stategies. Strategies can be registered allowing customization of how particular types are represented as XML.
* Error messages. When an exception occurs due to malformed XML, detailed diagnostics are provided to help isolate and fix the problem."
Features
* Ease of use. A high level facade is supplied that simplifies common use cases.
* No mappings required. Most objects can be serialized without need for specifying mappings.
* Performance. Speed and low memory footprint are a crucial part of the design, making it suitable for large object graphs or systems with high message throughput.
* Clean XML. No information is duplicated that can be obtained via reflection. This results in XML that is easier to read for humans and more compact than native Java serialization.
* Requires no modifications to objects. Serializes internal fields, including private and final. Supports non-public and inner classes. Classes are not required to have default constructor.
* Full object graph support. Duplicate references encountered in the object-model will be maintained. Supports circular references.
* Integrates with other XML APIs. By implementing an interface, XStream can serialize directly to/from any tree structure (not just XML).
* Customizable conversion stategies. Strategies can be registered allowing customization of how particular types are represented as XML.
* Error messages. When an exception occurs due to malformed XML, detailed diagnostics are provided to help isolate and fix the problem."
ClassEncrypt Software
ClassEncrypt Software: "ClassEncrypt is a program that can encrypt a developer's class files to prevent malicious users from stealing the source code. The program uses a modular design to allow the developer to create different encryption modules for the program to use. This software does not prevent the developer's software from being pirated.
The software comes with a default module that encrypts and decrypts using the Blowfish algorithm that was created by Bruce Schneier. This software is meant to be a barrier of protection for Java developers who want to market their software. It is not at all foolproof since the software enables the encrypted class files to still run using the regular JVM. It does, however, slow down any reverse engineering that someone may try on the developer's software."
The software comes with a default module that encrypts and decrypts using the Blowfish algorithm that was created by Bruce Schneier. This software is meant to be a barrier of protection for Java developers who want to market their software. It is not at all foolproof since the software enables the encrypted class files to still run using the regular JVM. It does, however, slow down any reverse engineering that someone may try on the developer's software."
Sunday, January 08, 2006
jcoverage
jcoverage
At jcoverage we are about productivity. Our suite of tools and technologies aim to reduce the 'code - test - diagnose - fix' cycle.
If you are using code coverage tools, you are also writing tests. We believe that you can improve your test development productivity at the same time.
Once you have coded, your tests and coverage analysis should run quickly so you can check outcomes and deliver changes as required from test feedback. It should also be able to easily test units in isolation rather than testing system as a whole.
You can start by downloading jcoverage/gpl, our free code coverage tool. Get started and see how much of your code is being covered by tests.
Once you have seen what our free coverage tool can do for you, why not use the fully supported jcoverage commercial edition.
Where your testing is less than adequate, you can improve your test quality and coverage through the use of our mock object technologies, included in our flagship product jcoverage+.
jcoverage+ includes our standard jcoverage technologies and introduces more rigour and finer granularity to your testing, allowing you to simulate and test for scenarios that otherwise would be impossible to test automatically.
At jcoverage we are about productivity. Our suite of tools and technologies aim to reduce the 'code - test - diagnose - fix' cycle.
If you are using code coverage tools, you are also writing tests. We believe that you can improve your test development productivity at the same time.
Once you have coded, your tests and coverage analysis should run quickly so you can check outcomes and deliver changes as required from test feedback. It should also be able to easily test units in isolation rather than testing system as a whole.
You can start by downloading jcoverage/gpl, our free code coverage tool. Get started and see how much of your code is being covered by tests.
Once you have seen what our free coverage tool can do for you, why not use the fully supported jcoverage commercial edition.
Where your testing is less than adequate, you can improve your test quality and coverage through the use of our mock object technologies, included in our flagship product jcoverage+.
jcoverage+ includes our standard jcoverage technologies and introduces more rigour and finer granularity to your testing, allowing you to simulate and test for scenarios that otherwise would be impossible to test automatically.
Enterprise Java Community: The Power of JAAS: Security System Alternatives
Enterprise Java Community: The Power of JAAS: Security System Alternatives
Purpose
I attended the CIO Forum a several months ago and sat in on a presentation on Identity Management, which is considered by C-level executives one of the hot technologies. From a C-level executive’s perspective, this presentation falls generally under the domain of Identity Management. At the Forum, the speaker briefly discussed RBAC (Role Base Access Control) and anecdotally mentioned that it is a “hard nut to crack.”
This article is an extension of a recent article I published on TheServerSide.com, Exploring J2EE Security for Applications using LDAP. That article identified key interfaces within a J2EE compliant application server that need to be configured in order to build secure applications focusing on RBAC, which is an integral part of Identity Management.
However, the article did not discuss, in detail, alternatives to using LDAP directly for Java Authentication and Authorization Service (JAAS) security, such as a Trust Association, one of the more popular system alternatives. Essentially, the power of JAAS is in its ability to use almost any underlying security system. One of those approaches is to use a Trust Association Interceptor (TAI) instead of direct LDAP access.
Purpose
I attended the CIO Forum a several months ago and sat in on a presentation on Identity Management, which is considered by C-level executives one of the hot technologies. From a C-level executive’s perspective, this presentation falls generally under the domain of Identity Management. At the Forum, the speaker briefly discussed RBAC (Role Base Access Control) and anecdotally mentioned that it is a “hard nut to crack.”
This article is an extension of a recent article I published on TheServerSide.com, Exploring J2EE Security for Applications using LDAP. That article identified key interfaces within a J2EE compliant application server that need to be configured in order to build secure applications focusing on RBAC, which is an integral part of Identity Management.
However, the article did not discuss, in detail, alternatives to using LDAP directly for Java Authentication and Authorization Service (JAAS) security, such as a Trust Association, one of the more popular system alternatives. Essentially, the power of JAAS is in its ability to use almost any underlying security system. One of those approaches is to use a Trust Association Interceptor (TAI) instead of direct LDAP access.
Eclipse BIRT Home
Eclipse BIRT Home: "BIRT is an open source, Eclipse-based reporting system that integrates with your application to produce compelling reports for both web and PDF.
BIRT provides core reporting features such as report layout, data access and scripting. The current released version is 1.0.1. Please try BIRT and tell us what you think by filling bugs reports & enhancement requests through Bugzilla as explained on the community page."
BIRT provides core reporting features such as report layout, data access and scripting. The current released version is 1.0.1. Please try BIRT and tell us what you think by filling bugs reports & enhancement requests through Bugzilla as explained on the community page."
Saturday, January 07, 2006
aisland: Home
aisland: Home: "AIsland's goal is to provide a framework to build and distribute agents.
The framework exposes objects (graphic module, audio module, neural network, fuzzy logic ...)
to an agent developer, who can glue these modules together using a scripting language, initally JavaScript.
Mobile Agents travel between different AIslands. If an Agent requests a module unknown to an AIsland,
the platform will ask the user for permission to load code from another peer. AIslands can persist trust relationships.
The inital version builds on Java and fat clients, facilitating a Java Swing GUI and a BSF/ Rhino engine,
to script against modules sitting on an JMX component bus hosted by an Avalon based micro kernel.
A port to small devices (J2ME - Java phones) is a future option.
An Agent is represented by an XML document and is distributed as a JXTA Codat.
Agents contain script code, which is interpreted by an AIsland (a JXTA peer) in a secure manner.
Host file systems are protected against malicious agents.
Agents and AIslands communicate using JXTA.
Network access through proxies for HTTP (SOAP) and SMTP is supported as well."
The framework exposes objects (graphic module, audio module, neural network, fuzzy logic ...)
to an agent developer, who can glue these modules together using a scripting language, initally JavaScript.
Mobile Agents travel between different AIslands. If an Agent requests a module unknown to an AIsland,
the platform will ask the user for permission to load code from another peer. AIslands can persist trust relationships.
The inital version builds on Java and fat clients, facilitating a Java Swing GUI and a BSF/ Rhino engine,
to script against modules sitting on an JMX component bus hosted by an Avalon based micro kernel.
A port to small devices (J2ME - Java phones) is a future option.
An Agent is represented by an XML document and is distributed as a JXTA Codat.
Agents contain script code, which is interpreted by an AIsland (a JXTA peer) in a secure manner.
Host file systems are protected against malicious agents.
Agents and AIslands communicate using JXTA.
Network access through proxies for HTTP (SOAP) and SMTP is supported as well."
Hive
Hive: "Hive is a Java software platform for creating distributed applications. Using Hive, programmers can easily create systems that connect and use data from all over the Internet. At its heart, Hive is an environment for distributed agents to live, communicating and moving to fulfill applications. We are trying to make the Internet alive."
Subscribe to:
Posts (Atom)