RFCs

RFC #0169: New package unittest.web

at 2008-08-14 in RFCs, Unittests by friebe

Scope of Change
A new package unittest.web will be created. It will contain the base class WebTestCase with which web tests can be written.

Rationale
Integration testing.

Read the full RFC here

RFC #0171: Rename util.DateInterval class

at 2008-08-08 in RFCs by friebe

Scope of Change
The util.DateInterval class will be renamed.

Rationale
PHP 5.3 has a class called DateInterval built-in. Thus, non-namespaced versions of the XP framework won't run on PHP 5.3.

Read the full RFC here

RFC #0164: Exceptions for XPClass::get*()

at 2008-07-14 in RFCs by friebe

Scope of Change
The following methods in lang.XPClass will throw exceptions instead of returning NULL for the case the respective element is not found:

getConstructor()
getMethod(string name)
getField(string name)

Rationale
Allow for chaining, be consistent with other APIs (if a hasX method exists, the getX method will throw an exception) and the getAnnotation() method.

Read the full RFC here

RFC #0162: HTTP Proxy

at 2008-06-01 in RFCs by friebe

Scope of Change
A functionality will be added to the peer.http.HttpConnection class to support HTTP proxies.

Rationale
Some machines in restricted networks may not access other networks directly.

Read the full RFC here

RFC #0166: XP Runners

at 2008-05-31 in RFCs by friebe

Scope of Change
This RFC defines the standards for the XP runners.

Rationale
Clarification is needed.

Read the full RFC here

RFC #0165: New text.regex package

at 2008-05-10 in RFCs by friebe

Scope of Change
A new package text.regex will be added.

Rationale
Object oriented API for regular expressions.

Read the full RFC here

RFC #0158: Register scriptlet, state and context as XSL callback

at 2008-04-14 in RFCs by kiesel

Scope of Change
Register instances of scriptlet objects whereever available to provide a standard basis for applications where to put XSL callback methods.

Rationale
XSL callbacks should be used where implementing in XSL is reimplementation of thing already available in XP or just to difficult to implement.
A standard way of providing these callbacks need to be provided as access to the XSL processor is required to register a callback and that access is not given at all places.

Read the full RFC here

RFC #0157: Make product, language and session optional URL parts

at 2008-04-14 in RFCs by kiesel

Scope of Change
Make product, language and session an option URL part for XP
applications that use XMLScriptlet.

Rationale
Every setup includes a default product and a default language which can be used when no value has been passed through the URL.

Many applications do not have more than one product or more than one language, so always passing it is overhead. In case non-default values are chosen, they'll again be passed through the known URL format.

Read full RFC here.

RFC #0160: xml.IXSLProcessor::setXMLTree() / setXSLTree()

at 2008-04-12 in RFCs by friebe

Scope of Change
Two new methods will be added to the xml.IXSLProcessor interface and implementing classes: setXMLTree() and setXSLTree().

Rationale
Allow for a separate implementation.

Read the full RFC here

RFC #0159: Deadlock handling

at 2008-04-12 in Databases, RFCs by friebe

Scope of Change
A new class rdbms.SQLDeadlockException will be introduced. The rdbms drivers will handle dead lock situations specially and throw this new exception instead of a generic SQLStatementFailedException.

Rationale
Deadlocks are a very special case in database systems and often need special programmatic handling.

Read the full RFC here

You can subscribe to the XP framework's news by using RSS syndication.