* JMS JBossJMS@localhost JMS provider JBoss 4.0 JBoss 4.0 channel configuration
* JMS WebLogicJMS@localhost WebLogic JMS Provider 9.1 WebLogic JMS example configuration for localhost
* JMS WebSphereMQ@localhost

Example:
Imagine that clocks go forward 1 hour at 1:00am. If we start a wait of duration 1 hour at 0:30am, we will calculate that the wait should expire at 1:30am. At 01:00, the system clock goes forward 1 hour and the wait is now treated as expired. That is, the wait only actually lasts 30 minutes.

When clocks go forward 1 hour, we will expire alarms and waits up to 1 hour too early. When clocks go back 1 hour, we will expire them up to 1 hour too late.

The following NullPointerException occurs:
[02-Apr-2007 14:24:15.161 IST] ERROR <DefaultProcessor> An exception occured processing a process instance [id: 99, activity: /process[1]/sequence[1]/assign[1]/copy[1], cursor activity: /process[1]/sequence[1]/assign[1]/copy[1], cursor last executed: /process[1]/sequence[1]/assign[1]].
java.lang.NullPointerException
at com.capeclear.bpel.runtime.executor.assign.Copy.preSet(Copy.java:71)
at com.capeclear.bpel.runtime.executor.CopyExecutor.execute(CopyExecutor.java:65)
at com.capeclear.bpel.runtime.cache.impl.DefaultProcessor.doWork(DefaultProcessor.java:182)
at com.capeclear.bpel.runtime.cache.Processor$ProcessorThread.run(Processor.java:58)

This does not affect cases where the element being assigned into already exists. In this case, only the content of the element (of simpleType) is assigned.

<bpws:copy>
<bpws:from expression="bpws:getVariableProperty('getValueRequestMessage', 'wrapper:identifier')/>
<bpws:to variable="setValueRequestMessage" property="wrapper:identifier" />
</bpws:copy>

The BPEL runtime does not support assignments of the form:

<bpws:copy>
<bpws:from variable="getValueRequestMessage" property="wrapper:identifier"/>
<bpws:to variable="setValueRequestMessage" property="wrapper:identifier" />
</bpws:copy>

When a project containing an import of a schema is deployed, the following error is displayed:

com.capeclear.capeconnect.application.TargetException:

Invocation failed for application test-tsimport for interface com.capeclear.applications.duplo.TransformServiceImpl

- Error initialising JAX-RPC service for application test-tsimport with interface com.capeclear.applications.duplo.TransformServiceImpl

- failed to load transformer: textToXml

- failed to initialize from schema data: Invalid Schema : 1206 : An error occurred while initialising the text schema processor for the element {http://schemas.capeclear.com/2004/01/TextSchema/Swift/MT54X}Transactions: [/xsd:schema[@targetNamespace=&quot;

http://schemas.capeclear.com/2004/01/TextSchema/Swift/MT54X"]/

xsd:element[@name=&quot;MT54X&quot;]/

xsd:complexType/xsd:sequence/xsd:element[1]] Invalid Schema: 13292 : Failed to find definition of the referenced element &apos;

{http://schemas.capeclear.com/2004/01/TextSchema/Swift/types}

SectionOne&apos;.

This error is similar to the Studio error where an imported type is not being found.

ERROR <MessageStoreInterceptor> Failed to mark request message ID=5 delivered on fault. Reason: Cannot commit/rollback as no persistence transaction exists.

The delivered status of the message is however correctly updated and this message can be ignored.

Note that if you were running Manager from within Cape Clear Studio (Eclipse), this error is displayed immediately. If you were running in standalone Internet Explorer, it may not be displayed immediately, depending on your IE settings. However, an error icon is displayed in the bottom left-hand side of the status bar.