Search -

Not found what you where looking for? Try the advanced search

Go to page back123...162163164...165166167next

Joined: 3-March-2005

Posts: 23

Posted: 3-March-2005 10:38

sorry for the bad post, the preview did not work.

Hi,

like the bugxter application, I want to separate my model from my view. I also want to use the links.xml file in order to have some abstraction from the real uri's. Unfortunately, I does not work and I don't know where to look for a solution.
The error is :
The request ffcpl:/showForegs.idoc in module urn:org:ten60:netkernel:ext:dpml failed because no module could be located to handle it. See Exception trace for details of resolution process.

executing instruction

in idoc
ffcpl:/showForegs.idoc

this is my module.xml :
<?xml version="1.0" encoding="utf-8"?>
<module>
<identity>
<uri>urn:be:kmi_irm:labo:web:forecasts</uri>
<version>1.0.0</version>
</identity>
<info>
<name>ForecastWeb</name>
<description>web modules forecasts</description>
<type>application</type>
</info>
<publisher>
<name>My Org</name>
<uri>http://www.1060.org</uri>
</publisher>
<licence>
<name>1060 Public License v1.0</name>
<uri>http://www.1060research.com/license</uri>
</licence>
<export>
<uri>
<match>ffcpl:/forecast-web/.*</match>
<match>ffcpl:/(entrypoints.xml)</match>
</uri>
<class/>
</export>
<rewrite>
<rule>
<match>ffcpl:(/forecast-web/.*)</match>
<to>active:mapper+operand@ffcpl:$1+operator@ffcpl:/links.xml</to>
</rule>
</rewrite>
<mapping>
<this>
<match>ffcpl:/(links.xml|www/).*</match>
</this>
<import>
<uri>urn:org:ten60:netkernel:ext:xml:core</uri>
</import>
<import>
<uri>urn:org:ten60:netkernel:ext:xml:ura</uri>
</import>
<import>
<uri>urn:org:ten60:netkernel:ext:dpml</uri>
</import>
<import>
<uri>urn:org:ten60:netkernel:ext:xrl</uri>
</import>
<import>
<uri>urn:org:ten60:netkernel:ext:layer1</uri>
</import>
<import>
<uri>urn:org:ten60:netkernel:ext:sys</uri>
</import>
<import>
<uri>urn:org:ten60:netkernel:ext:xsecurity</uri>
</import>
<import>
<uri>urn:org:ten60:netkernel:ext:session</uri>
</import>
<import>
<uri>urn:org:ten60:netkernel:ext:xhtml</uri>
</import>
<import>
<uri>urn:org:ten60:netkernel:mod:xforms</uri>
</import>
<import>
<uri>urn:org:ten60:netkernel:mod:smtp</uri>
</import>
<import>
<uri>urn:org:ten60:netkernel:tpt:http</uri>
</import>
<import>
<uri>urn:be:kmi_irm:labo:services:forecasts</uri>
</import>
<super/>
</mapping>
</module>

and this is my links.xml:
<?xml version="1.0" encoding="UTF-8"?>
<links basepath="ffcpl:/forecast-web/">
<link>
<name>Show the foregs</name>
<ext>/showForegs</ext>
<int>active:dpml+operand@ffcpl:/showForegs.idoc</int>
<args>links,param,session</args>
</link>
</links>

the showForegs.idoc is in the module directory under /resources, but using ffcpl:/resources/showForegs.idoc does not work either.

showForegs.idoc :
<?xml version="1.0" encoding="UTF-8"?>
<idoc>
<seq>
<instr>
<type>copy</type>
<operand>hello</operand>
<target>this:response</target>
</instr>
</seq>
</idoc>

Solutions Developer > links.xml problem

henk

Joined: 3-March-2005

Posts: 23

Posted: 3-March-2005 10:36

links.xml problem

Hi,

like the bugxter application, I want to separate my model from my view. I also want to use the links.xml file in order to have some abstraction from the real uri's. Unfortunately, I does not work and I don't know where to look for a solution.
The error is :

Code:

The request ffcpl:/showForegs.idoc in module urn:org:ten60:netkernel:ext:dpml failed because no module could be located to handle it. See Exception trace for details of resolution process.

executing instruction

in idoc
ffcpl:/showForegs.idoc

this is my module.xml :

Code:

&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;module&gt;
    &lt;identity&gt;
      &lt;uri&gt;urn:be:kmi_irm:labo:web:forecasts&lt;/uri&gt;
      &lt;version&gt;1.0.0&lt;/version&gt;
    &lt;/identity&gt;
   &lt;info&gt;
      &lt;name&gt;ForecastWeb&lt;/name&gt;
        &lt;description&gt;web modules forecasts&lt;/description&gt;
      &lt;type&gt;application&lt;/type&gt;
    &lt;/info&gt;
    &lt;publisher&gt;
        &lt;name&gt;My Org&lt;/name&gt;
      &lt;uri&gt;http://www.1060.org&lt;/uri&gt;
    &lt;/publisher&gt;
&lt;licence&gt;
      &lt;name&gt;1060 Public License v1.0&lt;/name&gt;
      &lt;uri&gt;http://www.1060research.com/license&lt;/uri&gt;
   &lt;/licence&gt;
&lt;export&gt;
&lt;uri&gt;
      &lt;match&gt;ffcpl:/forecast-web/.*&lt;/match&gt;
      &lt;match&gt;ffcpl:/(entrypoints.xml)&lt;/match&gt;
&lt;/uri&gt;
&lt;class/&gt;
&lt;/export&gt;
&lt;rewrite&gt;
    &lt;rule&gt;
   &lt;match&gt;ffcpl:(/forecast-web/.*)&lt;/match&gt;
   &lt;to&gt;active:mapper+operand@ffcpl:$1+operator@ffcpl:/links.xml&lt;/to&gt;
    &lt;/rule&gt;
&lt;/rewrite&gt;
    &lt;mapping&gt;
   &lt;this&gt;
      &lt;match&gt;ffcpl:/(links.xml|www/).*&lt;/match&gt;
   &lt;/this&gt;
      &lt;import&gt;
         &lt;uri&gt;urn:org:ten60:netkernel:ext:xml:core&lt;/uri&gt;
      &lt;/import&gt;
      &lt;import&gt;
         &lt;uri&gt;urn:org:ten60:netkernel:ext:xml:ura&lt;/uri&gt;
      &lt;/import&gt;
      &lt;import&gt;
         &lt;uri&gt;urn:org:ten60:netkernel:ext:dpml&lt;/uri&gt;
      &lt;/import&gt;
      &lt;import&gt;
         &lt;uri&gt;urn:org:ten60:netkernel:ext:xrl&lt;/uri&gt;
      &lt;/import&gt;
      &lt;import&gt;
         &lt;uri&gt;urn:org:ten60:netkernel:ext:layer1&lt;/uri&gt;
      &lt;/import&gt;
      &lt;import&gt;
         &lt;uri&gt;urn:org:ten60:netkernel:ext:sys&lt;/uri&gt;
      &lt;/import&gt;
      &lt;import&gt;
         &lt;uri&gt;urn:org:ten60:netkernel:ext:xsecurity&lt;/uri&gt;
      &lt;/import&gt;
      &lt;import&gt;
         &lt;uri&gt;urn:org:ten60:netkernel:ext:session&lt;/uri&gt;
      &lt;/import&gt;
      &lt;import&gt;
         &lt;uri&gt;urn:org:ten60:netkernel:ext:xhtml&lt;/uri&gt;
      &lt;/import&gt;
      &lt;import&gt;
         &lt;uri&gt;urn:org:ten60:netkernel:mod:xforms&lt;/uri&gt;
      &lt;/import&gt;
      &lt;import&gt;
         &lt;uri&gt;urn:org:ten60:netkernel:mod:smtp&lt;/uri&gt;
      &lt;/import&gt;
      &lt;import&gt;
         &lt;uri&gt;urn:org:ten60:netkernel:tpt:http&lt;/uri&gt;
      &lt;/import&gt;
      &lt;import&gt;
         &lt;uri&gt;urn:be:kmi_irm:labo:services:forecasts&lt;/uri&gt;
      &lt;/import&gt;
    &lt;super/&gt;
  &lt;/mapping&gt;
&lt;/module&gt;

and this is my links.xml:

Code:

&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;links basepath="ffcpl:/forecast-web/"&gt;   
   &lt;link&gt;
      &lt;name&gt;Show the foregs&lt;/name&gt;
      &lt;ext&gt;/showForegs&lt;/ext&gt;
      &lt;int&gt;active:dpml+operand@ffcpl:/showForegs.idoc&lt;/int&gt;
      &lt;args&gt;links,param,session&lt;/args&gt;
   &lt;/link&gt;
&lt;/links&gt;

the showForegs.idoc is in the module directory under /resources, but using ffcpl:/resources/showForegs.idoc does not work either.

showForegs.idoc :

Code:

&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;idoc&gt;
    &lt;seq&gt;
   &lt;instr&gt;
         &lt;type&gt;copy&lt;/type&gt;
    &lt;operand&gt;hello&lt;/operand&gt;
   &lt;target&gt;this:response&lt;/target&gt;
        &lt;/instr&gt;
    &lt;/seq&gt;
&lt;/idoc&gt;

General Support > sql transaction support

francop

Joined: 19-February-2005

Posts: 7

Posted: 2-March-2005 09:44

sql transactions

Thanks Pete,
I look forward to trying the transactional SQL component as soon as its ready.

Thanks again.

Franco

General Support > xslfo-fop problem

pjr

Joined: 7-February-2005

Posts: 397

Location: UK

Posted: 25-February-2005 15:23

ext-xslfo fixed

We've posted a patch for the ext-xslfo module...

http://www.1060.org/forum/topic/18/1

News > XSLFO Module Update v1.1.1

pjr

Joined: 7-February-2005

Posts: 397

Location: UK

Posted: 25-February-2005 15:22

XSLFO Module Update v1.1.1

The add-on XSLFO module has been updated to fix a bug in which pass-by reference arguments were being resolved within the ext-xslfo module rather up the super-stack.

To install/update use the module wizard. Currently the new module is available from the primary 1060 servers - it will synced with the mirrors over the next 24hrs.

General Support > sql transaction support

pjr

Joined: 7-February-2005

Posts: 397

Location: UK

Posted: 25-February-2005 10:28

Having looked at the JDBC Connection API - we can very easily support the commit/rollback in the sqlBatch service. In addition we can probably optimize sqlBooleanQuery, sqlQuery by setting readonly.

We need to get the connection pooling work done RSN - we'll ensure these updates get done too. Probably next week.

Thanks for the suggestions.

Pete

General Support > sql transaction support

francop

Joined: 19-February-2005

Posts: 7

Posted: 25-February-2005 00:54

SQL transaction support

The only features I feel are missing from the sqlxxxx services (sqlBatch only really) is transaction
support. I do beleive that transaction support is not vendor specific.
I don't see how any non trivial SQL based/backed application can be developed
without such support.
The executeBatch JDBC feature seems an ideal vehicle to interact from an XML
pipeline. An XML document can be used
to represent a dataset of any complexity. It then needs to
be persisted into an RDBMS as an atomic set. XSLT is used
to translate the document into a set of SQL statements. But
then these statements need to be persisted as a single unit.
if the Nth statement fails, the entire set needs to be rolled back otherwise
the DB is in an inconsistent state.

The problem you mention regarding RESTfull invocations I don't beleive is
really a problem. (not for us anyway). I think what you mean (correct me if
I am wrong) is that there may be situations where a transaction lasts for a
number of RESTfull service invocations. This situation (in particular) with
RDBMS interactions should be avoided if at all possible. I do see that your static references could be used when the situation arose (but these could cause scalability issues when db connections are limited). What we do need
though is a guarantee that a single RESTfull service invocation (which may
alter a number of RDBMS tables) is consistent. It either succeeds or fails.
If it fails the system needs to be left in a consistent state - probably to
that which existed prior to the failed call. So the
'execute SQL batch' and 'commit/rollback' need to be performed in the one RESTfull service call.
The easiest way I can see this being done would be be to encapsulate the entire batch
sql statements into a transaction (in your java code), just by issueing a 'commit' after the
executeBatch command, and a 'rollback' in any exception handling code.

Thanks again for your time and quick responses.

General Support > sql transaction support

pjr

Joined: 7-February-2005

Posts: 397

Location: UK

Posted: 24-February-2005 14:19

The sqlXXXXX services are a set of tools for RDBMS interaction which are implemented using the JDBC API. The intent is to provide a common plain vanilla feature set - therefore there are no vendor specific features presented.

All of the services are hosted by a single accessor in the mod-db module...

org.ten60.rdbms.accessor.RDBMSAccessorImpl

It should be straightforward to modify this class to provide the features you need.

If you think there are features that are not vendor specific that we should add to the vanilla services please let us know.

FYI. We have work scheduled to improve connection pooling and provide static references to connections. At the moment there are rare situations in which consecutive RESTful invocations of the sql services fail because they are not being performed on the same connection. This can occur if the connection has been recreated after earlier being ejected from a heavily loaded cache.

One scenario which can highlight this is performing operations using mySQL temporary tables. MySQL directly ties the temporary table to the connection - if, because of the RESTful service invocation, you perform consecutive operations on two different connections the second will have no access to any temporary tables created on a previous connection. Using static references to the connections in the RDBMSAccessorImpl will resolve this.

General Support > sql transaction support

francop

Joined: 19-February-2005

Posts: 7

Posted: 24-February-2005 03:49

sql transaction support

Hello again,
Can you tell me if there is any transaction support within any of the SQL/RDBMS accessors.

That is, how can I specify when to perform a 'commit' or 'rollback'?

I have tried sqlBatch accessor and noticed there does not seem to be any way of rolling back the entire batch if any SQL fails. What seems to happen is that all SQL that succeeds prior to an exception are commited, and all subsequent SQLs after the failed SQL are ignored.
I am using oracle 8.1 and its doco seems to indicate that upon any sql exceptions being raised from its executeBatch command, it should be possible
to issue a rollback. I believe that in my situation the Oracle Autocommit setting is 'off'.
Is there a way of specifying an 'autocommit' setting? say in the configuration file.

Thanks again,
Franco

General Support > xslfo-fop problem

francop

Joined: 19-February-2005

Posts: 7

Posted: 24-February-2005 03:27

xslt-fop bug

Thank you for your quick response, that fixed the problem. Seems to be working well now.

Go to page back123...162163164...165166167next