xswingx can help you...
* Add prompts to any text component.
* Add child components to any text field. (Called buddies. Wonder why? Read the FAQ.)
* Add a search field to your UI (and let it look and behave like native - or not).
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 strategies. 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.
* Alternative output format. The modular design allows other output formats. XStream ships currently with JSON support and morphing.
XRules is an XML business rules language that expresses constraints, calculations, interdependencies, and properties that describe and exist among elements and attributes of an XML document. XRules can be used to validate business rules in an XML transaction, attach metadata to the XML Infoset, or add dynamism to XML by using the Dynamic DOM.
This site is tracking the progress of the XML Processing Model Working Group. It is maintained by Norman Walsh, chair of the WG, but is not otherwise affiliated with the WG or the W3C.
Xooctory is an open source continuous integration server, aiming to provide the following features:
* Open Source
* Massively scalable
* Flexible
* Build dependency aware
* Instant and rich feedback
* Secured
xmonad is a tiling window manager for X. Windows are arranged automatically to tile the screen without gaps or overlap, maximising screen use. Window manager features are accessible from the keyboard: a mouse is optional. xmonad is extensible in Haskell, allowing for powerful customisation. Custom layout algorithms, key bindings and other extensions may be written by the user in config files. Layouts are applied dynamically, and different layouts may be used on each workspace. Xinerama is fully supported, allowing windows to be tiled on several physical screens.
he goal of XMLVM is to offer a flexible and extensible cross-compiler toolchain. Instead of cross-compiling on a source code level, XMLVM cross-compiles byte code instructions from Sun Microsystem's virtual machine and Microsoft's Common Language Runtime. The benefit of this approach is that byte code instructions are easier to cross-compile and the difficult parsing of a high-level programming language is left to a regular compiler. In XMLVM, byte code-based programs are represented as XML documents. This allows manipulation and translation of XMLVM-based programs using advanced XML technologies such as XSLT, XQuery, and XPath.
The Beryl XML GUI library was written to ease the development of graphical user interfaces using Swing on Java. It lets you store user interfaces as XML markup. This will help you avoid unnecessary clutter in your source - Swing code mixed with application logic can become a troublesome and hard to read mess as the application size increases. The library comes with a visual component builder, which makes development a breeze. The most important features are:
xfpt is a program that reads a file of plain text that contains relatively simple markup, and outputs an XML file. It is intended to simplify the management of XML data. It is not a program that attempts to turn a plain text document into XML. Markup within text is introduced by ampersand characters, but is otherwise "soft". You can define what follows the ampersand, for example, &" to generate a "quote" element. There is also a macro facility that allows for higher level concepts such as chapters, displays, tables, etc.
XMind, combined with online sharing service, provides a revolutionary way to enable both team brainstorming and personal mind mapping. With this major upgrade, we bring Web 2.0 concepts on community sharing into a popular desktop application. New Gantt view allows project managers to easily track project tasks and schedules. You'll find many more useful and time-saving functions in XMind product family.
XINS is an open-source Web Services framework supporting HTTP protocols such as REST, SOAP, XML-RPC, JSON, JSON-RPC and more.
From the specifications written in simple XML, XINS generates the Client API (.jar), the Java server code template (.war), the WSDL and the documentation of the specification in HTML (with the test forms) or in OpenDocument format.
Flying Saucer is an XHTML renderer written in Java. It's 100% Java, not a native wrapper, and it only handles well-formed XHTML + CSS. It is intended for embedding web-based user interfaces into Java applications (ex. web photo album generator, help viewer, iTunes Music Store clone). It cannot be used as a general purpose web browser since it does not support the malformed legacy HTML found on the web, though recent work on compatibility libraries may be enough to do what you need. You may be able to work with legacy HTML (e.g. HTML that is not well-formed XML) by using a pre-processor that cleans it up; there are several of these, including JTidy and TagSoup.
Hm. RAD environment with Swing GUI, no downloads yet (2008-08-18), uses an proprietary scripting language, only the Enterprise Edition (2.2 K $) allows to use the Java API. Targeted customer group seems to be procedural developers. What sort of Java product should that be where you need to mention that you can write your own classes??? doesn't seem to use the Java EE API, would be interesting if the "ObjectScript" is interpreted or bytecode.
IMHO too proprietary, goes into the wrong direction for bigger enterprises.
It is currently common to build a number of releases from a single code base. For example, a development release, a QA release, a production release and perhaps customer-specific releases. However, these releases seem to differ mostly in the contents of their XML configuration files, and then only very little. Maintaining all these slightly different configuration files is a real nuisance.
XConf was created to simplify this maintenance. Its fundamental premise is that a single development-release (or production-release) configuration file is created and maintained, and is processed by XConf at either build or deployment time into an appropriate release by applying one or more XML-based scripts. Each script contains only the differences required to create the appropriate release, thus removing the need for the mass duplication of configuration files.
This is not really a new solution, since XSLT has been used in the past to do this quite successfully, but XPath can get a little arcane, and maintaining transformation scripts using XSLT can become really complex very quickly. XConf uses a very simple and compact method of specifying elements that need to be processed, and provides some very useful constructs to make transformations painless.
L. Hunyadi, and I. Vajk. Proc. of the 15th International Conference on Systems, Signals and Image Processing (IWSSIP), page 197--200. Bratislava, Slovakia, (25--28 06 2008)
C. Krueger. PFE '01: Revised Papers from the 4th International Workshop on Software Product-Family Engineering, page 282--293. London, UK, Springer, (2002)