cvs commit: cocoon-2.1/src/documentation/xdocs who.xml
reinhard2003/06/30 06:59:41 Modified:src/documentation/xdocs who.xml Log: First commit ;-) Revision ChangesPath 1.6 +1 -0 cocoon-2.1/src/documentation/xdocs/who.xml Index: who.xml === RCS file: /home/cvs/cocoon-2.1/src/documentation/xdocs/who.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- who.xml 18 May 2003 10:54:21 - 1.5 +++ who.xml 30 Jun 2003 13:59:40 - 1.6 @@ -59,6 +59,7 @@ liChristopher Oliver (coliver.at.apache.org)/li liGiacomo Pati (giacomo.at.apache.org)/li liKonstantin Piroumian (kpiroumian.at.apache.org)/li + liReinhard P#246;tz(reinhard.at.apache.org)/li liOvidiu Predescu (ovidiu.at.apache.org)/li liJeremy Quinn (jeremy.at.apache.org)/li liGianugo Rabellino (gianugo.at.apache.org)/li
Introduction Reinhard Pötz
I'm really moved by the vote and I want to thank you for the confidence. I'm 25 years old and live in Vienna, Austria. I studied business consultancy and graduated three years ago. Now I work as consultant for EFP Consulting Austria and as freelancer (Cocoon consulting and training). The first time I came in touch with Cocoon was during the JAX2001 (conference for Java, Apache, XML and WebServices) in Frankfurt. Used to use (released) commercial software I was impressed by the quality of open source *alpha* software (Cocoon was available in version 2.0alpha5). After this experience Michael Gerzabek and I started to build our first prototyp connecting Cocoon with SAP. This was also the hour of birth of Web3 which has been part of Cocoon 2.1dev since the beginning of this year. Web3 has also become the basis of some of our projects. On my Cocoon todo-list the top issue is finishing the flow (design implementation) and I hope this can be reached within the next two weeks. After this I want to spend some time on documentation espacially the flow. The next big thing on my list is finding/finshing/promoting a/the Cocoon form framworks that can compete against M$ webforms, JSF, Struts, ... Apart from Cocoon I'm on the way to become a Certified Transactional Analyst (this has nothing to do with IT as many people believe but more with psychology), like to read, play tennis and learn to dance (waltz, cha-cha, jive, ... ;-) Cheers, Reinhard
RE: More on FOM
Hi Ricardo, From: Ricardo Rocha [mailto:[EMAIL PROTECTED] Hi friends, The following items reflect the discussions Stefano and I have had around the FOM: - The load(uri) global function should be supported. This is clearly needed for nested source file inclusion (which map:script does not support). +1 - The cocoon.releaseComponent(component) method should be supported in conjunction with cocoon.getComponent(id). Further discussion is needed about whether the FOM implementation should automatically take care of releasing components. I'm with you that this part will need more investigation and use cases. But for now I'm fine without some automatism. So +1 too. - There should be unrestricted access to all components via cocoon.getComponent(id). I'll implement getComponent( id ) and releaseComponent( component) ASAP because the current flow implementation exposes the component manager and this leads to a serious bug! If you have more than one user the component manager can become null. This can be very annoying if you want to train some people ... Among other goodies, this will give indirect access to Actions and Modules without providing explicit FOM support for them. Access to request input modules, in particular, should account for request.getURI(). AFAIK many of them need the object model and this is not provided by the flow so I think you have no chance to use the actions and input modules which need objects of the object model. Am I right here? - Access to continuation objects should be provided. var kont = sendPageAndWait(uri, data) This is deemed necessary as certain continuation usage patterns may call for explicit, programmatic invalidation of continuations. - Properties - id - Methods - getParent() - getChildren() - invalidate() - Events - onExpiration() What do you guys think? sounds good. It should also be possible to create your own continuations objects without sending a page. See the JXForms implementation which needs this to provide previous/next-navigation. I'll add all those things to the proposal ASAP. Reinhard
cvs commit: cocoon-2.1/src/targets ide-build.xml
reinhard2003/06/30 12:22:16
Modified:.build.properties
src/targets ide-build.xml
Log:
- support for a OUTPUT_DIR property -- so it can be overwritten locally
Revision ChangesPath
1.22 +3 -0 cocoon-2.1/build.properties
Index: build.properties
===
RCS file: /home/cvs/cocoon-2.1/build.properties,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- build.properties 13 Jun 2003 10:27:38 - 1.21
+++ build.properties 30 Jun 2003 19:22:15 - 1.22
@@ -147,6 +147,9 @@
tools.loader.dest=${tools}/loader
tools.jetty=${tools}/jetty
+# IDE
+ide.eclipse.outputdir=${build.root}/eclipse/classes
+
# Libraries
lib=lib
lib.core=${lib}/core
1.7 +1 -1 cocoon-2.1/src/targets/ide-build.xml
Index: ide-build.xml
===
RCS file: /home/cvs/cocoon-2.1/src/targets/ide-build.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- ide-build.xml 23 Jun 2003 18:11:30 - 1.6
+++ ide-build.xml 30 Jun 2003 19:22:16 - 1.7
@@ -84,7 +84,7 @@
filter token=SRC_DIRS value=${srcs}/
filter token=LIBS value=${libs}/
filter token=MOCKS_DIRS value=${mockss}/
-filter token=OUTPUT_DIR value=${build.root}/eclipse/classes/
+filter token=OUTPUT_DIR value=${ide.eclipse.outputdir}/
/filterset
/copy
cvs commit: cocoon-2.1/src/scratchpad/src/org/apache/cocoon/components/flow/javascript/fom FOM_Cocoon.java
reinhard2003/06/30 12:11:10
Modified:src/scratchpad/src/org/apache/cocoon/components/flow/javascript/fom
FOM_Cocoon.java
Log:
- Implemented functions:
* getComponent( id )
* releaseComponent( component)
* load( script)
- support for cocoon:// protocol when sending pages
- some code formatting
Revision ChangesPath
1.7 +81 -16
cocoon-2.1/src/scratchpad/src/org/apache/cocoon/components/flow/javascript/fom/FOM_Cocoon.java
Index: FOM_Cocoon.java
===
RCS file:
/home/cvs/cocoon-2.1/src/scratchpad/src/org/apache/cocoon/components/flow/javascript/fom/FOM_Cocoon.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- FOM_Cocoon.java 26 Jun 2003 19:44:04 - 1.6
+++ FOM_Cocoon.java 30 Jun 2003 19:11:10 - 1.7
@@ -49,9 +49,12 @@
*/
package org.apache.cocoon.components.flow.javascript.fom;
+
import java.io.OutputStream;
import java.util.Map;
+import org.apache.avalon.framework.component.Component;
+import org.apache.avalon.framework.component.ComponentException;
import org.apache.avalon.framework.component.ComponentManager;
import org.apache.avalon.framework.logger.Logger;
import org.apache.cocoon.components.flow.ContinuationsManager;
@@ -63,13 +66,20 @@
import org.apache.cocoon.environment.Response;
import org.apache.cocoon.environment.Session;
import org.mozilla.javascript.JavaScriptException;
+import org.mozilla.javascript.Script;
import org.mozilla.javascript.Scriptable;
import org.mozilla.javascript.ScriptableObject;
import org.mozilla.javascript.Undefined;
import org.mozilla.javascript.Wrapper;
import org.mozilla.javascript.continuations.Continuation;
+
/**
- * Implementation of FOM (Flow Object Model)
+ * Implementation of FOM (Flow Object Model).
+ *
+ * @since 2.1
+ * @author a href=mailto:coliver.at.apache.org;Christopher Oliver/a
+ * @author a href=mailto:reinhard.at.apache.org;Reinhard Pötz/a
+ * @version CVS $Id$
*/
public class FOM_Cocoon extends ScriptableObject {
@@ -120,6 +130,7 @@
this.interpreter = null;
}
+
private void forwardTo(String uri, Object bizData,
Continuation continuation)
throws Exception {
@@ -132,8 +143,14 @@
lastContinuation,
0);
}
-interpreter.forwardTo(getParentScope(), this, cocoon://+
- environment.getURIPrefix() + uri,
+
+String redUri = uri;
+
+if(! uri.startsWith( cocoon:// ) ) {
+redUri = cocoon:// + this.environment.getURIPrefix() + uri;
+}
+
+interpreter.forwardTo(getParentScope(), this, redUri,
bizData, wk, environment);
}
@@ -179,12 +196,64 @@
}
*/
-
-public Object jsFunction_getComponent(String id) {
-// what is this?
-return null;
+
+/**
+ * Access components.
+ *
+ * TODO: Do we want to restrict the access of sitemap components? (RP)
+ * TODO: Do we want to raise an error or return null? (RP)
+ */
+public Object jsFunction_getComponent( String id ) {
+Object o = null;
+try {
+ o = this.componentManager.lookup( id );
+ } catch (ComponentException e) {
+ o = null;
+ }
+return o;
+}
+
+/**
+ * Release pooled components.
+ *
+ * @param component - an codeObject/code that is an instance
+ * of codeorg.apache.avalon.framework.component.Component/code
+ */
+public void jsFunction_releaseComponent( Object component )
+ throws JavaScriptException {
+try {
+this.componentManager.release( (Component) component );
+} catch( ClassCastException cce ) {
+throw new JavaScriptException( Only components can be released! );
+} catch( Exception e ) {
+throw new JavaScriptException( Error during release of component
occurred! + e.getMessage() );
+}
}
+/**
+ * Load the script file specified as argument.
+ *
+ * @param filename a codeString/code value
+ * @return an codeObject/code value
+ * @exception JavaScriptException if an error occurs
+ */
+public Object jsFunction_load( String filename )
+throws JavaScriptException {
+org.mozilla.javascript.Context cx =
+org.mozilla.javascript.Context.getCurrentContext();
+try {
+Scriptable scope = getParentScope();
+Script script
[Flow] Serious problem with cocoon.getComponent(id)
I think we have I serious problem with the lookup of components
within flow scripts.
Under load the component manager can become null!!!
Could somebody with more knowledge about this part of Cocoon have
a look at it?
TIA!
Cheers,
Reinhard
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, June 30, 2003 9:11 PM
To: [EMAIL PROTECTED]
Subject: cvs commit:
cocoon-2.1/src/scratchpad/src/org/apache/cocoon/components/flo
w/javascript/fom FOM_Cocoon.java
reinhard2003/06/30 12:11:10
Modified:
src/scratchpad/src/org/apache/cocoon/components/flow/javascript/fom
FOM_Cocoon.java
snip/
+public Object jsFunction_getComponent( String id ) {
+Object o = null;
+try {
+ o = this.componentManager.lookup( id );
+ } catch (ComponentException e) {
+ o = null;
+ }
+return o;
+}
RE: [Flow] Serious problem with cocoon.getComponent(id)
From: Christopher Oliver [mailto:[EMAIL PROTECTED]
You need to describe how to recreate the problem in more
detail
ok, here some more details:
As you can see I implemented cocoon.getComponent(id). If I call
this method from the flow and do a lot of refreshes at once
(pushing the F5 key at IE) this error occurs.
If I include a debug statement writing the ComponentManager to
System.out I sometimes get null and not the manager.
IIRC last week a problem with the petstore examples and the
database connections was reported altough the old implementation
exposed the ComponentManager itself.
If you need more information please let me know!
Reinhard
for me to help you. The component manager will only
become null when the FOM_Cocoon object is invalidated. Your
scripts should not be executing in this state. If they are
that that indicates a bug and we need to find it.
Regards,
Chris
-Original Message-
From: Reinhard Pötz [mailto:[EMAIL PROTECTED]
Sent: Monday, June 30, 2003 12:57 PM
To: [EMAIL PROTECTED]
Subject: [Flow] Serious problem with cocoon.getComponent(id)
Importance: High
I think we have I serious problem with the lookup of
components within flow scripts. Under load the component
manager can become null!!!
Could somebody with more knowledge about this part of Cocoon
have a look at it?
TIA!
Cheers,
Reinhard
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, June 30, 2003 9:11 PM
To: [EMAIL PROTECTED]
Subject: cvs commit:
cocoon-2.1/src/scratchpad/src/org/apache/cocoon/components/flo
w/javascript/fom FOM_Cocoon.java
reinhard2003/06/30 12:11:10
Modified:
src/scratchpad/src/org/apache/cocoon/components/flow/javascript/fom
FOM_Cocoon.java
snip/
+public Object jsFunction_getComponent( String id ) {
+Object o = null;
+try {
+ o = this.componentManager.lookup( id );
+ } catch (ComponentException e) {
+ o = null;
+ }
+return o;
+}
RE: Contribution: MultiPartPostAction FilePartGenerator
Eric, Please use Bugzilla (http://nagoya.apache.org) to provide your enhancements otherwise I fear that they will be overlooked. Additionally I cc'ed cocoon-dev. Without looking at your sources and examples: What does your generator provide what http://cocoon.apache.org/2.1/userdocs/generators/stream-generator.html can't do for you? Cheers, Reinhard -Original Message- From: Simmerman, Eric [mailto:[EMAIL PROTECTED] Sent: Monday, June 30, 2003 7:50 PM To: [EMAIL PROTECTED] Subject: Contribution: MultiPartPostAction FilePartGenerator Hello all, As per the Cocoon contribution guidelines, I've made some Cocoon extensions source code available for download at: http://www.tempeststrings.com/cocoon/in dex.html. There are two files that meet the guidelines for contribution to the Cocoon code base: org.apache.cocoon.acting.MultiPartPostAction.java org.apache.cocoon.generation.FilePartGenerator.java Together, these will allow Cocoon to accept a multi part post containing an uploaded file and kickoff a pipeline by parsing the file's contents for generation. I've used this source to configure a Cocoon installation as a real-time data conversion service. Using the service, a user can upload a file in XML format, and immediately receive a response containing the same data in any format supported by Cocoon Serializers. A sample sitemap.xconf is included in the header comments of MultiPartPostAction. My hope is that these contributions will make their way into the Coccon code base. Please let me know if I can assist in any way. Please note that the other files (not the two described above) found in this distribution rely on GPL code and can not be released under the Apache license. Thanks, -Eric Simmerman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Give all Cocoon committers CVS access?
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Nicola Ken Barozzi Jeff Turner wrote, On 24/06/2003 13.38: As most of you probably saw, there's a thread on cocoon-dev suggesting that Forrest ought to be a Cocoon subproject, with the consensus being it makes sense. AFAICT the only practical difference would be that Cocoon committers would automatically become Forrest committers. Sounds fine to me. Can we vote on these issues then? Vote 1: Cocoon committers automatically become Forrest committers +1 +1 Vote 2: Forrest should become a subproject of Cocoon (http://cocoon.apache.org/forrest) +1 I vote +1 and +/-0. Both make sense, but 2) seems slightly more pain than gain, unless there's some advantage I've overlooked. Well, when this issue first came out, I agreed that Forrest could become different from Cocoon, and eventually use something else. Reality has shown us that we are tied double-rope with Cocoon, and this is being a good thing. Xml and Cocoon PMCs are both very nice to be in, and as for communities we are already cooperating anyways. But now that Lenya is under Cocoon, I tend to think that it changes things. And the more we go forward, the more we will be integrating new parts of the Cocoon Project, assimilating things like Linotype and Lenya, and becoming more and more part of the changes. We are a strong use case of Cocoon and I hope also Lenya and Linotype soon, hence we can be the reality check for all Cocoon projects. The question I ask myself is: community-wise, where do we belong? The answer is very easy: Cocoon. As for the future, were will we belong community-wise? Now I think that it also quite evident: Cocoon. This is the reason why I vote Cocoon. I don't think it will be a major change for us now practically, so it may seem more hassle than gain, but when things will start playing out, it will IMHO become more evident that we belong with the Cocoon community. +1 (Forrest should become a subproject of Cocoon) Reinhard
RE: FOM, views, and input modules
From: Christopher Oliver [mailto:[EMAIL PROTECTED]
I modified the FOM implementation in the scratchpad to make the FOM
available to the view layer, thinking that the view author
also should
see the FOM (See FOM_JavaScriptFlowHelper.java), rather than the raw
Request, Response, etc. Do others agree with this?
The same is valid for the view layer as explained from you below!
You can still pass parameters to generators or transformers of pipelines
called by the flow layer.
Additionally you can call pipelines that contain actions. Do we want
this?
I'm worried that people start to work around the restrictions of the FOM
...
I also modified the GarbageGenerator to use the FOM.
So because of the FOM you can't do this in a flow script anymore:
cocoon.request.sitemapURI
likewise in a Garbage view template you can no longer do this:
page whatever={$request/sitemapURI}
in both cases because the FOM doesn't expose the sitemapURI
property
of the Request.
However the input modules give full access to the original
Java Request
object, so in the sitemap you can still do this:
map:call function=whatever
map:parameter name=whatever value={request:sitemapURI}/
and pass it as a parameter to your flowscript, bypassing the FOM (!)
This seems inconsistent to me. What do others think?
Yes, you are right! Maybe we should disable input module substituion
within
call elements of the sitemap. (I don't know if this is possible at all.)
What do you think?
Reinhard
[OT] CVS access over SSH
Sorry for the off-topic post but I have a problem accessing Cocoon with SSH using Putty (win2k). Is there anybody out there who runs this configuration? I get some real strange error messages. TIA! Reinhard P.S. Of course I would write some documentation, promised!
RE: flow - database.js - Componentmanager
From: Stefano Mazzocchi on 6/20/03 11:52 AM Reinhard Pötz wrote: Yes, you are right. The current draft of the FOM does not contain a database layer. I see two options: 1.) remove it complety 2.) add it to the petstore examples (which are based on those JS functions) I'm in favour of removing them complety and encapsulate the database calls in the petstore examples using Java objects. So we can show our users what we envision as the best way of writing flow apps with database access. In theory, if the new FOM is complete, you can have access to the database connection avalon component directly from getComponent() and the petstore can be changed accordingly. This would: 1) remove the need for database.js 2) keep concerns separate 3) avoid the need for a javascript extension concept that we planned but never came to even design. What do you think? a late +1 (Christian has already moved it into the scratchpad examples) Reinhard
RE: [SourceResolver] getLastModified() for cocoon:// sources always returns 0
From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] Reinhard Pötz wrote: If I understand this correctly I get with source.getValidity() the SourceValidity. Yes. But if I call e.g. cocoon://blablalba.xml this method returns null. The default pipe is the caching pipe and I use it with map:pipeline ... /map:pipeline If I resolve a resource using the file protocol a SourceValidity object is returned. Do I have to change something to get a SourceValidity object returned from a cocoon source? No, this should work (and it worked some weeks ago :) ) So, if I understand you correctly, you're using the lastest 2.1-dev, use the SourceResolver to resolve cocoon://blablalba.xml, get a o.a.e.source.Source object and when you call getValidity(), you get null as the result? I used 2.1-dev-M2. I going to set up a test example using the latest CVS snapshot and report if it works for me. Reinhard
RE: [SourceResolver] getLastModified() for cocoon:// sources always returns 0
From: Christopher Oliver [mailto:[EMAIL PROTECTED] You're right. But it's a bad idea to use the cocoon:// protocol as the source for JXTemplateGenerator (as it would be also for TraxTransformer, for example). In effect you are generating a new program for every request, that must be recompiled for every request, which is clearly _very_ inefficient. Perhaps caching could fix this in some cases, but it seems like a bad practice in the first place. Not in my use case. I use datasource pipelines that provide raw data only instead of objects. I'm aware that those parts can't be compiled but I'm completly satisfied if the Cocoon internal caching mechanism works. I'll check why source.getValidity() doesn't work for me with the latest CVS. Reinhard
RE: [Flow] Preparing the vote - long!
From: Steven Noels [mailto:[EMAIL PROTECTED] On 22/06/2003 6:01 Stefano Mazzocchi wrote: Both actions and input/output modules were created to overcome sitemap programmability limitations. Flow doesn't have those limitations anymore so i don't see the reason to keep those artifacts here. What do others think about this? I think the current community and mindshare behind flow is still too small to already start deprecating 'old-fashioned hacks' I think nothing will be depracated - not at the moment. The time will show if there is still need for 'old-fashioned hacks'. which were and still are being (ab)used a lot for the same reasons flow will be (ab)used for. Also, the continuations thing appears to be only one possible way to address the webapp dev paradigm. I don't think you are suggesting an active depreciation, but suggestions like the one above seem rather tendencious and suggestive IMHO. OK, it is only a small quote lifted out of context, but it is a good illustration of my worry that flow, being a very interesting approach, still is _only_just_one_ approach to attack the given problem domain. As Yes, one of _many_ approaches. much as I'm genuinely interested in continuation-based flow, I think flow needs some more real-world usage (like Pier's case) before we consider it being part of the core features of Cocoon (on the same level of 'streamlined XML processing' and 'the sitemap'). I read the above statement as a suggestion into that direction. Ok. Then we should tell our users that Cocoon 2.1 offers a new way of writing web applications, use the time until Cocoon 2.2 (or whatever) will be released to use the flow in more real life use cases. And then if we still say Wow, what a revolutionary approach of writing web apps! we can resposition Cocoon in that sense that the control flow is an equal part to the sitemap. (Please note, this has nothing to do with technology itself but with marketing!) What do you think? If I say 'core', I mean the kind of stuff which you _have_ to use if you want to use Cocoon, not the 'blocks vs core' discussion, or 'it has an impact on the sitemap grammar'. I'm pretty sure that you don't want to see flow added to Cocoon with people openly saying 'ok', but silently thinking 'whatever, I'm going to stick to my way anyhow'. Oh. Do please read this as a neutral observation, will you? I'm not into flames. If I'm wrong with my observation, just say so and I'll withdraw to my cave. ;-) Cheers, /Steven Reinhard
[Stammtisch-Vienna] Reminder!
I want you to remind that the first Austrian Cocoon Stammtisch will take place on June, 25th, 8pm at Centimeter I (8th district behind the city hall). (http://www.tourist-net.co.at/lokale/centimeter/centimeter1.htm) The table is reserved for Pötz. I'm looking forward to meeting you all! Kind regards, Reinhard
[SourceResolver] getLastModified() for cocoon:// sources always returns 0
If I call the method getLastModified() for cocoon:// sources the return value is always 0. Is this the correct behaviour? If yes at least the JXTemplateGenerator (line 2868) doesn't work correctly and I think some more components too. Reinhard
RE: [SourceResolver] getLastModified() for cocoon:// sources always returns 0
From: Sylvain Wallez [mailto:[EMAIL PROTECTED] Reinhard Pötz wrote: If I call the method getLastModified() for cocoon:// sources the return value is always 0. Is this the correct behaviour? Yes ! If yes at least the JXTemplateGenerator (line 2868) doesn't work correctly and I think some more components too. Didn't look at it, but 2.1 components should rely on Excalibur Sources and the associated SourceResolver (looked up in the component manager) to use the Source's validity. Thank you! If I understand this correctly I get with source.getValidity() the SourceValidity. But if I call e.g. cocoon://blablalba.xml this method returns null. The default pipe is the caching pipe and I use it with map:pipeline ... /map:pipeline If I resolve a resource using the file protocol a SourceValidity object is returned. Do I have to change something to get a SourceValidity object returned from a cocoon source? Reinhard
RE: flow - database.js - Componentmanager
Yes, you are right. The current draft of the FOM does not contain a
database layer.
I see two options:
1.) remove it complety
2.) add it to the petstore examples (which are based on those JS
functions)
I'm in favour of removing them complety and encapsulate the database
calls in the petstore examples using Java objects. So we can show our
users what we envision as the best way of writing flow apps with
database access.
Reinhard
-Original Message-
From: Geoff Howard [mailto:[EMAIL PROTECTED]
Sent: Friday, June 20, 2003 6:44 PM
To: [EMAIL PROTECTED]
Subject: Re: flow - database.js - Componentmanager
um, isn't this database access directly from flow one of the
deprecated parts of the API??
Geoff
At 11:55 AM 6/20/2003, you wrote:
I think i solve it. Check this new Database.js
I've changed the original one:
[ Starts here
]---
// // CVS $Id: Database.js,v 1.2 2003/03/20 02:46:32 vgritsenko Exp $
//
// Prototype Database API
//
// TBD: Move this Database stuff to its own library outside of flow
//
defineClass(org.apache.cocoon.components.flow.javascript.Scr
iptableCon
nection);
defineClass(org.apache.cocoon.components.flow.javascript.Scr
iptableResult);
Database.componentManager=this.cocoon.componentManager;
Database.getConnection = function(selectorValue) {
var selector =
this.componentManager.lookup(Packages.org.apache.avalon.excal
ibur.datas
ource.DataSourceComponent.ROLE
+ Selector);
try {
var ds = selector.select(selectorValue);
return new Database(ds.getConnection());
} finally {
this.componentManager.release(selector);
}
}
[ Ends here ]---
On Fri, 2003-06-20 at 16:25, Nuno Santos wrote:
What i've found is that the flowscript works just fine
when i start
the cocoon engine, but whenever i make any change to the
script, it
just loose the cocoon.componentManager!
On Fri, 2003-06-20 at 16:19, Frank Taffelt wrote:
I also found this bug in the flow Database.js!
It seems that the componentManager is null whenever
the script
is reloaded!
Hmm, what do you mean with script is reloaded? I
didn't find any
rational
reason for this ...
--
Nuno Santos [EMAIL PROTECTED]
[Flow] Preparing the vote - long!
. Reinhard: I think we need the continuations object available within the flows. Especially if you write high advanced flows (look at the JXForms implementation) you need access to the continuations object since you have to create continuations without sending a page. Without this trick the next-previous navigations wouldn't work. What do you think? Note to the vote: + This is a simple yes/no question too. ** * Modules (input/output) * ** Stefano: what modules? I meant the input and output modules. I think there is information available in input modules (e.g. static global parameters) that could be useful within flows. Output modules could be useful too. But maybe Christian could come up with more detailed explanations. Note to the vote: + This is a simple yes/no question too. ** * Script load support* ** Stefano/Ricardo: The reason for removing load() is because we want to avoid people from loading scripting dynamically. This goes in parallel with the anti-pattern of dynamic pipeline construction. WARNING: removing load() does *NOT* imply that you have to force all your flow in one big file. The way to fragment your flow into different files is to use several map:script elements in the map:flow section of the sitemap. Sylvain: Load support is IMO required because JS lacks an import statement. Not having it means we'll have to write a map:script for the script we want to use, but also for *all the scripts it depends on*, recursively. This will be very difficult to manage. Stefano: since we agreed that blocks only expose a URI space controlled by the sitemap (they don't expose resources directly!) you can use a reader to get the flow to the dependent block, or you can use a pipeline to generate your flow (for example, traducing a workflow written using a markup language into the equivalent flow instructions). Here you have all the machinery you need to compose your flows as you like. Recursively. The difference between the above and load() is thin but real: while load() has to be executed at runtime, the map:script calls can be done at sitemap assembly time. It could have a big impact on runtime performance of the flowscripts. Note to the vote: + Simple question: Do we support the load() function within scripts? - o - Are there any other open points! Please speak now! Reinhard
[Flow] Scope and Sessions
Today I tried to find out how sessions and flow work together: 1. If my tests are correct the global scope of a flow only lives as long as the session which the flow is tied to is active. So if the session expires or you use another client to continue a 'waiting' function you only have access to the local scope within the flow function. 2. All scripts within a map:script.../ part share the same global context. If you want to share more objects you need another scope (request, session, context). Is this description correct? If yes is this the intended behaviour? From a technical point of view, are there any other possiblities of implementing the JavaScript global scope. If so has there ever been a community decision (vote) which of these possibilities is best? I'm only asking because I'm curious - no offense to anybody! Best regards, Reinhard
RE: Continuations in Aggregations?
Richard, Sorry, but this won't work and is not intended to work (I discussed this with Ovidiu some months ago). He told me to think the other way around - the flow should be your ONLY controller and decides which page will be sended to the client. Up to now I didn't run into this problem again but may be you come up with a use case where it is not possible to solve a problem this way please let us know! Regards, Reinhard -Original Message- From: Richard In Public [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2003 6:00 PM To: [EMAIL PROTECTED] Subject: Continuations in Aggregations? [I originally posted this to cocoon-users but am reposting it after receiving a suggestion to post it here...] Hi I've started (trying) to incorporate FlowScripts/XmlForms into a project. I'm working from the PetStore example (thanks Upayavira) and have a paired-down version of the new account form. This form is served correctly when access directly (..cocoon/myproj/newAccountForm.do) but causes the following exception when access from within an aggregate element: org.apache.cocoon.ProcessingException: Attempted to process incomplete pipeline. The relevant parts of my sitemap are below, together with the full stack trace. I sure hope that aggregation and continuations are compatible! Thank you, Richard Hoberman
RE: [ANN] XMLForm as a standalone servlet toolkit
Ivelin, From: ivelin [mailto:[EMAIL PROTECTED] Now, let's do some constructive talking. You probably remember the endless threads that were started in the last few months regarding the complexity of Cocoon and the fact that it continuously misses its release dates. I am only refering to them to point out that not everything is perfect around here. More specificly: As it stands XMLForm is way behind the XForms standards. It was about a year ago when Torsten, Konstantin, and I invested a lot of time to bring to light the initial version of what seems to be a significant improvement to Cocoon. Since then it has been polished by many people and stabilized somewhere around September last year. Ever since, I have been planning to invest time into another major release which would bring the module up to the latest standards. However such an initiative will obviously require a lot of discussions, trial, errors and rollbacks, I did not want to jeopardize the 2.1 release which has been first planned for release in November and has been postponed indefinitely ever since. It is hard to not notice that C2.1 has been in the clean-up stage forever. I understand that moving to a top level domain is time consuming and it is very important for the future of the project. From my point of view please don't move out the further development of XMLForms from the Cocoon CVS. I think the Cocoon control flow would have never become part of Cocoon if Ovidiu had created his own project ... (but mayme I'm wrong here). But there are also some other reasons to have the further development of XMLForms within Cocoon: - there are many other parts of Cocoon which are changing (control flow) or newly created - you can integrate them into XMLForms at once - you can freeze the current status of XMLForms for the upcoming Cocoon 2.1 distribution and put the new development in - there are many developers and lurkers who have a look at cocoon-dev - XMLForms are an integral part of Cocoon (a framework within the framework) and should be developed by the community (what would you do if you make further developments within your sourceforge project and then you come back to Cocoon and ask for a vote to include it and your vote is not accepted because of some reasons e.g. incompatible changes, ...) Only some thoughts of a XMLForms user ... Best regards, Reinhard
RE: [heads-up] wiki abuse: your advice please
From: Matt Sergeant [mailto:[EMAIL PROTECTED] On Friday, Mar 14, 2003, at 13:46 Europe/London, Steven Noels wrote: while briefly checking the Wiki, I was confronted with some apparent abuse: people uploading attachments which don't have much to do with Cocoon (possibly just making benefit of the bandwidth we are sponsoring), people playing around on certain non-Sandbox pages, even to the extreme of erasing the Main page, and various other not-so-funny things. I'm very happy to see some people go in and correct, and the new 'restore latest version' feature of JSPWiki sure helps with this. Nevertheless, I'm annoyed a bit by the lack of adult behaviour by some IP addresses, and was wondering whether (and how) I should block them. I know this sounds pretty harsh, and that's why I'm polling you guys to see what you would think would be a fair policy. FYI, when people do this on the Apache AxKit Wiki, I block their IP at our firewall. Harsh, but fair. And no complaints so far. This only helps to some point because (at least in Europe) many people use dial-in connections with changing IP adresses. A second problem arises with enforced proxies. My cable provider installed a proxy and I have to use it for all HTTP connections whether I like it or not. Just some thoughts ... Reinhard
RE: Snapshot links at Cocoon website
That is the only occurrence of the word xml-cocoon2 on the server, all other problems are client-cache related... I checked it again and now the link is correct. Probably a proxy server issue because client caching is turned off in all my browsers. Reinhard
RE: Snapshot links at Cocoon website
From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] Ok, it's working here as well, but shouldn't the links go to cocoon-2.1? Good question ... I would link to http://xml.apache.org/cocoon/mirror.cgi#nightly but this would need a rebuild of the complete site (as Pier pointed out). But maybe this update can be done directly at the webserver and the CVS is updated in the same way. Reinhard
Snapshot links at Cocoon website
From: Pier Fumagalli [mailto:[EMAIL PROTECTED] On 10/3/03 7:42, Carsten Ziegeler [EMAIL PROTECTED] wrote: b) Let's get the nightly build working asap Carsten, are you talking about the nightly builds (GUMP) or the nightly CVS snapshots??? Because if the latter, I was just waiting for the CVS repository split to integrate their automatic checkout back into the snapshotting scripts already ran by root on cvs.apache.org... And I've done that (well, just now, but at least one less problem to worry about) http://cvs.apache.org/snapshots/cocoon-2.0/ http://cvs.apache.org/snapshots/cocoon-2.1/ I also patched the download (mirror) page to reflect the change... http://xml.apache.org/cocoon/mirror.cgi#nightly Currently the link Dev Snapshots leads to http://xml.apache.org/from-cvs/xml-cocoon2/. Maybe that's the reason why it can't be found by many people. I suggest linking to http://xml.apache.org/cocoon/mirror.cgi#nightly but I guess that's your intention ;-) Regards, Reinhard
RE: STX could seriously replace XSLT on the server side
From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED] If you don't know what STX is, just take a look here: Daniel has already done some first steps using it. See http://marc.theaimsgroup.com/?l=xml-cocoon-devm=104566478723403w=2 Reinhard
RE: [ARTICLE]Excel Reports with Apache Cocoon and POI
http://www.xml.com/pub/a/2003/01/22/cocoon-excel.html Perhaps, we can build a wiki page of all this very interesting articles. Checkout http://wiki.cocoondev.org/Wiki.jsp?page=Links - there you should find all? articles mentioned on cocoon-users or cocoon-dev. Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: [vote] finilizing the pending votes on flow [was Re: [RT] Flow/SitemapIntegration]
-Original Message- From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]] Reinhard Poetz wrote: There remains one open question for me: How to I get 'feedback' whether the called pipeline did its job well or not? And if not, how to I get information about what happend (error message/status information)? What do you think? I think you are getting right to the bone of the problem and I don't think I have a clear-cut solution... but I gotta go now, have to meet Pier at a pub downtown and we don't want to make a nice english beer wait, don't we? :) Of course not ;-) A further issue are asynchronous calls of pipelines in the case - you do not want to wait for response of the backend - or the backend is at the moment of calling it not available - or you want to guarantee the call of the backend Regards, Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: [vote] finilizing the pending votes on flow [was Re: [RT] Flow/SitemapIntegration]
Thank you very much! I thought that it would work the other way!
Regards,
Reinhard
-Original Message-
From: Christopher Oliver [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 17, 2003 7:18 AM
To: [EMAIL PROTECTED]
Subject: Re: [vote] finilizing the pending votes on flow [was Re: [RT]
Flow/SitemapIntegration]
Hi Reinhard,
Just a warning, you should always use the var keyword with local
variables in JavaScript. Your function should probably read:
function callPipeline(src) {
var xc = cocoon.componentManager.lookup( myXMLConsumer.ROLE );
var resolver =
cocoon.environment.getObjectModel().get(source-resolver);
var srce = resolver.resolveURI(src);
resolver.toSAX( srce, xc );
return xc;
}
Without var you are creating global variables named xc, resolver,
srce. .
Regards,
Chris
Reinhard Poetz wrote:
For my flows I use a self-defined function which makes this for me:
function callPipeline(src) {
xc = cocoon.componentManager.lookup( myXMLConsumer.ROLE );
resolver =
cocoon.environment.getObjectModel().get(source-resolver);
srce = resolver.resolveURI(src);
resolver.toSAX( srce, xc );
return xc;
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
RE: [vote] finilizing the pending votes on flow [was Re: [RT] Flow/SitemapIntegration]
-Original Message-
From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 17, 2003 1:27 PM
To: [EMAIL PROTECTED]
Subject: Re: [vote] finilizing the pending votes on flow [was Re: [RT]
Flow/SitemapIntegration]
Reinhard Poetz wrote:
Stefano Mazzocchi wrote:
snip
Let me add:
- make a new method that allows the flow to call a pipeline and pass a
different output stream. This will allow to use pipelines as tools to
serialize things, say, to disk or to other means.
What do you think?
/snip
I think you mean a function in the system.js, don't you?
Yes, exactly. A function equivalent to sendPageAndContinue() that I can
use to call a pipeline but to use it orthogonally from the normal stream
of data that flows from the request to the response.
This is very useful, for example, to save stuff to disk or to CVS or to
any other repository and will finally, IMO, give an end to the need for
a forked pipeline that goes in two different places.
For my flows I use a self-defined function which makes this for me:
function callPipeline(src) {
xc = cocoon.componentManager.lookup( myXMLConsumer.ROLE );
resolver =
cocoon.environment.getObjectModel().get(source-resolver);
srce = resolver.resolveURI(src);
resolver.toSAX( srce, xc );
return xc;
}
The component myXMLConsumer has a method codepublic String
getDocument()/code ... mabe there is a better/more elegant way, but it
works for me ;-)
nonono, careful. You are calling a pipeline to have its data as an
object model to play with. While this is fair, I don't like it at all
and would not want it included in system.js. It looks like an hack from
miles away (sorry, no offense, just stating my impressions honestly)
I had the same impression but no idea of making it better. I'm looking
forward to reading your RT.
(I have no problem with other ideas and valuable feedback from people who
have the same/different needs - I think that's the big difference between
commercial software and open source software because commercial software is
nearly always focused and once written and working only reviewed if problems
arise.)
Therefore I'll come up with a solution of using the flow as controller for
XMLForms - a 'pre-alpha' version is already running at my laptop. I know
that my solution is far from being perfect (continuations can be very tricky
...) but I want to learn and the feedback will make me learn new things and
this will make our/my solutions better.
One note: If I look back the last two years it's really incredible what I
learned about design patterns (coming from the M$ visual programming world I
have never heard of it before), java programming, xml, xslt, ... only by
studying Cocoon and Avalon concepts/source code/examples and
following/taking part in disussions. I don't know which university/school
can offer an education at this level - maybe I'm wrong.
What are the experiences of others?
Reinhard
What I want is something different.
I'll come up with an RT later today or tomorrow.
For now, consider it separated from this vote since it has not been
discussed well and I want more feedback on it.
--
Stefano Mazzocchi [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
RE: [vote] finilizing the pending votes on flow [was Re: [RT] Flow/SitemapIntegration]
For my flows I use a self-defined function which makes this for me:
function callPipeline(src) {
xc = cocoon.componentManager.lookup( myXMLConsumer.ROLE );
resolver =
cocoon.environment.getObjectModel().get(source-resolver);
srce = resolver.resolveURI(src);
resolver.toSAX( srce, xc );
return xc;
}
The component myXMLConsumer has a method codepublic String
getDocument()/code ... mabe there is a better/more elegant way, but it
works for me ;-)
nonono, careful. You are calling a pipeline to have its data as an
object model to play with. While this is fair, I don't like it at all
and would not want it included in system.js. It looks like an hack from
miles away (sorry, no offense, just stating my impressions honestly)
After having a second look at my sources I think I don't really need the
part generating the string. This would reduce it to following lines:
function callPipeline( src ) {
var xc = cocoon.componentManager.lookup( anyXMLConsumer.ROLE );
var resolver = cocoon.environment.getObjectModel().get(
source-resolver );
var srce = resolver.resolveURI( src );
resolver.toSAX( srce, xc );
}
Then the pipeline called with src makes everything on its own.
1. gather the necessary information from somewhere (input modules,
database, ...)
2. save the information (send a mail, write to cvs, write to disc, ...)
There remains one open question for me: How to I get 'feedback' whether the
called pipeline did its job well or not? And if not, how to I get
information about what happend (error message/status information)?
What do you think?
Reinhard
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
RE: [vote] finilizing the pending votes on flow [was Re: [RT] Flow/SitemapIntegration]
Ugo Cei wrote:
Reinhard Poetz wrote:
Therefore I'll come up with a solution of using the flow as
controller for
XMLForms - a 'pre-alpha' version is already running at my laptop. I know
that my solution is far from being perfect (continuations can
be very tricky
...) but I want to learn and the feedback will make me learn
new things and
this will make our/my solutions better.
Do you mean something like this?
var form = getForm(progetto-form, progetto,
context://flows/workflow-schema.xml);
while (true) {
form.save(cocoon.environment.getObjectModel(), request);
sendPageAndWait(progetto-form, { username : user.name });
form.populate(cocoon.environment.getObjectModel());
form.validate(progetto);
if (form.getViolations() != null
form.getViolations().size() 0) {
continue;
break;
}
Yes. (Additionally?) I use continuations to move forward/backward within the
flow. This works well but sometimes I get some strange results after using
the previous/next button of the *browser*.
My next step will be controlling Ivelin's XMLForm example with a flow
script. If this works I'll submit a patch that enables others to have a look
at it.
Reinhard
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
RE: [RT] Flow/Sitemap Integration
Michael Melhem / Stefano Mazzocchi wrote:
snip
map:sitemap
map:components
/map:components
map:flow
map:script
src=myflow.js
/map:script
map:flowmap
map:map pattern=login/ flow=login/
map:map type=regexp pattern=register*/
flow=registerUser/
map:map pattern=logout/ flow=logout/
/map:flowmap
/map:flow
map:pipelines
...
/map:pipelines
/map:sitemap
We could define a flow mapping as a matching between a flow function
and its corresponding entry point pattern (which could be an URI
or whatever)
True.
We could use the map:match directly withing the flowmap to implement
this, but this would not force the user to call a flow method and would
not allow for the compact easy-to-read syntax above.
But I'm pretty sure that people *will* want to extend that and will
complain about the fact that map and match do, in fact, the same
thing, but with different semantics and this won't please people (nor
please my sense of semantic elegance, to tell you the truth)
A map:map = map:match + map:call
Im not against using map:match here within the flowmap...but
I do have to ask wouldnt it suggest to the user (incorrectly) that this
is another a pipeline where they can assemble anything they like?
I don't think so because the flow related stuff is outside of
map:pipelines.../map:pipelines. And a second arguement: the sitemap
interpreter will not allow such constructs.
Therefore I would use following XML to declare the mappings to flow scripts.
...
/map:components
map:flow
map:scripts language=JavaScript
map:script src=scripts.js/
/map:scripts
map:flowmap
map:match pattern=xxx
map:flow call-function=xxx()/
/map
map:match type=request-parameter pattern=cont-id
map:flow continue-with={1}/
/map:match
/map:flowmap
/map:flow
map:pipelines
...
This would have following advantages:
- reuse of the matchers
- easier for existing cocoon users to understand the mapping
between uri/request-parameter/what-ever --- flow
- possible to submit parameters to the matcher AND to the function
- clear separation between pipelines and flows
and
- (as already mentioned in this thread): the map:flow-part should match
before the map:pipelines part
... disclaimer:
I know that element/attribute names are important but my point in this mail
is the structure - so please don't discuss why I named elements this ;-)
Perhaps at the implementation level map:match and map:map are
similar, but conceptually they are different. Using map:map will
encourage the user to think of the mapping as a single atomic
instruction and not try and tinker with other
components (routing or otherwise). Hmmmbut im still in two minds
about this. :)
What do you mean exactly?
What I *really* need is a way to redirect to a URI which is mapped to a
flowscript - which is currently possible.
If we use map:map component (as suggested above), the question then
becomes, how do we get the map:map component to match (URIs in
the above case)?
Is there a reason why we wouldnt use (under the hood) the
already existing matcher components to the matching here?.
No technical reason (that I can think of) but it's a purely
semantical one.
Granted that it makes sense to move the flow hooks from the pipeline, I
think that we should reuse semantics where it makes sense, because
people already made an effort to learn it and in that case we reduce
their need to learn new stuff.
Exactly!
Thoughts?
What about issues like backwards compatibility. If we were to get the
the go ahead form the list to implement this, would we still allow
flow-hooks within the pipelines sections as is the case now - for the
sake of backward compatibility??
I think there should be a *final* vote about the semantics without
considering backward compatibilty:
- should flow-hooks within the pipelines be removed?
- names of the flow elements (scripts, call-function, continue)
- allowing the cocoon protocol calling scripts?
(I'm in favor of it because this could become a *really* cool feature!)
Regards,
Reinhard
Regards,
Michael
--
Stefano Mazzocchi [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
RE: [vote] finilizing the pending votes on flow [was Re: [RT] Flow/SitemapIntegration]
Stefano Mazzocchi wrote:
snip
Let me add:
- make a new method that allows the flow to call a pipeline and pass a
different output stream. This will allow to use pipelines as tools to
serialize things, say, to disk or to other means.
What do you think?
/snip
I think you mean a function in the system.js, don't you?
For my flows I use a self-defined function which makes this for me:
function callPipeline(src) {
xc = cocoon.componentManager.lookup( myXMLConsumer.ROLE );
resolver = cocoon.environment.getObjectModel().get(source-resolver);
srce = resolver.resolveURI(src);
resolver.toSAX( srce, xc );
return xc;
}
The component myXMLConsumer has a method codepublic String
getDocument()/code ... mabe there is a better/more elegant way, but it
works for me ;-)
Regards,
Reinhard
--
Stefano Mazzocchi [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
RE: [ERROR] CVS build failed.
Antonio Gallardo wrote: ... BUILD FAILED file:/xml-cocoon2/build.xml:1209: Compile failed; see the compiler error output for details. ... Please can someone advise what I am doing wrong? Best Regards, Antonio Gallardo Antonio, You should find a few mails about this problem - have a look at the archives. Did you check out CVS after Ovidiu's patch? Regards, Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Build system problems on OS/X 10.2.3
We get the same error on Win2k + java1.3.1 but at another position during the build process. What's the reason for this ant problem? Regards, Reinhard -Original Message- From: Ovidiu Predescu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 08, 2003 7:44 PM To: [EMAIL PROTECTED] Subject: Re: Build system problems on OS/X 10.2.3 On Wednesday, Jan 1, 2003, at 04:46 US/Pacific, Jeremy Quinn wrote: On Wednesday, Jan 1, 2003, at 02:44 Europe/London, David Crossley wrote: I get the same problem on Linux with Java-1.3.1 ./build.sh -Dinclude.webapp.libs=yes webapp Well that is interesting! I was seriously beginning to think this was a problem somehow introduced by Apple's release of the MacOSX 10.2.3 upgrade .. which happened around the same time this problem was first noticed. Sorry you are having the same problem though ;) Any solution to this problem yet? I've been bitten by it this morning after I did an update from CVS. Here's the relevant portion: validate-config: Conducting validation of core configuration files. (You can turn validation off if you must, using ./properties.xml) Validating all cocoon.roles instances ... Validating all stylesheets ... BUILD FAILED java.lang.OutOfMemoryError no stack trace available Total time: 2 minutes 48 seconds java.lang.OutOfMemoryError no stack trace available Greetings, -- Ovidiu Predescu [EMAIL PROTECTED] http://webweavertech.com/ovidiu/weblog/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: [Proposal] Implementing XMLForm with Flow
-Original Message- From: Ugo Cei [mailto:[EMAIL PROTECTED]] Sent: Friday, December 06, 2002 9:25 AM To: [EMAIL PROTECTED] Subject: Re: [Proposal] Implementing XMLForm with Flow Reinhard Poetz wrote: I have already successfully reimplmented the XMLForms using the control flow. I would have posted an example but internal reasons made enhancements and changes to the XMLForms implementation necessary. I will come up with some more details soon. Are you interested? Regards, Reinhard Nah, I was planning to do it all myself because I'm a Real Programmer (TM) ;-. ;-) Jokes aside, yes, I'm very much interested. Please share what you have with us. If I'm right you want to start in January when your holidays start. My example should be available then. Regards, Reinhard Ugo -- Ugo Cei - http://www.beblogging.com/blog/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: [Proposal] Implementing XMLForm with Flow
Hi Ovidiu, I will post an example as soon as I have a free day because I have to remove some enhancements which make no sense as they require our internal libraries. I hope you'll hear from me next week but I can't promise it. Regards, Reinhard -Original Message- From: Ovidiu Predescu [mailto:[EMAIL PROTECTED]] Sent: Friday, December 06, 2002 8:45 AM To: [EMAIL PROTECTED] Subject: Re: [Proposal] Implementing XMLForm with Flow Hi Reinhard, On Thursday, Dec 5, 2002, at 13:25 US/Pacific, Reinhard Poetz wrote: Conclusion: let's reimplement XMLForm using Flow as the controller and get rid of those actions. I have already successfully reimplmented the XMLForms using the control flow. I would have posted an example but internal reasons made enhancements and changes to the XMLForms implementation necessary. I will come up with some more details soon. Are you interested? Yes, there is a great deal of interest for having this integration. Could you please share the idea behind your implementation? Code would also be great ;) Best regards, -- Ovidiu Predescu [EMAIL PROTECTED] http://webweavertech.com/ovidiu/weblog/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: [Proposal] Implementing XMLForm with Flow
Conclusion: let's reimplement XMLForm using Flow as the controller and get rid of those actions. I have already successfully reimplmented the XMLForms using the control flow. I would have posted an example but internal reasons made enhancements and changes to the XMLForms implementation necessary. I will come up with some more details soon. Are you interested? Regards, Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Changing Xalan XSL (WAS Re: SVG - java socket exception)
Chris, The problem you have is a well-known problem of Cocoon or more precicly of Xalan. There are many mails in the archives about this topic (e.g.: http://marc.theaimsgroup.com/?l=xml-cocoon-devm=101994024218728w=2). If you want to use Saxon have a look at http://outerthought.net/wiki/Wiki.jsp?page=Saxon - it should help (and is faster than Xalan). Regards, Reinhard -Original Message- From: Chris Faulkner [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 03, 2002 6:26 PM To: [EMAIL PROTECTED] Subject: Changing Xalan XSL (WAS Re: SVG - java socket exception) HI More on this - a couple of others seem to have similar problems but nobody ever got a reply when they post the error makes me think it is a bug. Anyhow, if I change this parameter to false (it is true by default) in cocoon.xconf parameter name=incremental-processing value=false/ I don't get the errors but the JSP is still being called 2 or 3 times so it is much slower and I'd rather leave the incremental-processing parameter at true. How can I change from xalan to another XSL engine ? There is a mention of this on the performance tips page but no instructions about how to do it. Chris Hello I am getting on OK with Cocoon. I like it very much. I am using some JSP code as a generator. This creates some XML data which I apply xsl to transform to SVG. This is then serialised with svgxml and returned to the client. It all works fine. Except that, looking at my logs, very often, the first execution of the JSP returns this to stdout/stderr. java.lang.RuntimeException: java.net.SocketException: Connection aborted by peer : socket write error at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java :3231) at java.lang.Thread.run(Thread.java:479) I can see in the logs that Cocoon automatically seems to fire the same JSP again. It then works on the next shot, I get my SVG displayed in my SVG viewing app and it is just fine. This is obviously slowing things up though. Any ideas - I am using Cocoon 2.0.3 on Tomcat 4.0.1, JDK 1.3.1_06 on W2K. Thanks Chris - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: 2.1 : cinclude / sourceresolver and request parameter handling changed?
Michael, try cinclude:include src=cocoon:/configresources/contact/ select=/contact/title/ Regards, Reinhard -Original Message- From: Michael Homeijer [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 26, 2002 10:59 AM To: '[EMAIL PROTECTED]' Subject: 2.1 : cinclude / sourceresolver and request parameter handling changed? Hi, I have just migrated my application to the latest CVS version (xmlforms requirements). It seems that the sourceresolver handles request parameters differently. I have an xml file with the following element in it: cinclude:include src=cocoon:/configresources/contact/?xpath=//contact/title/ It is transformed by the cinclude transformer. This was working in the 2.0.3 version, but with the lates version it seems that request parameters (xpath=) are not passed to the internal cocoon pipeline. I can't see anything wrong with the cinclude transformer sources, so I guess that the sourceresolver has changed? Any ideas? TIA, Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Cocoon Workshop by Software AG and TECCO
Today I have been invited to a Cocoon workshop. It wouldn't be that interessting that I post it here but it's not that Cocoon we all are thinking of. It seems to be something similar because the workshop is called Multi-Media Content Engineering mit CORSO Spaces (it think I needn't translate the *German* title ;-). The speakers are Kurt Höll and Eva Kühn and come from Software AG and TECCO Software Entwicklung AG (http://www.tecco.at) - I think they should know it better. For all German speakers - here is the info text of the workshop: Dynamisches, adaptives Content Engineering verknüpft Informationen aus verschiedensten Quellen zu einem auf persönliche Bedürfnisse und unterschiedliche Arbeitsumgebungen angepassten Ganzen. Wesentlich dafür ist real-time Zugriff auf verteilte Datenbestände, hohe Performance und Ausfallssicherheit sowie weitgehende Abstraktion von Endgeräten, vom PC bis zu mobilen Devices quer über alle Plattformen hinweg. Cocoon, ein europaweit führendes Unternehmen im Bereich Content Engineering, setzt für die nächste Generation seiner Produkte auf CORSO Shared Object Spaces der TECCO Software Entwicklung AG. CORSO bietet maximale Unabhängigkeit von Hardware, Betriebssystemen und Kommunikationsstandards, intelligentes Caching von Daten und höchste Performance auch auf mobilen Endgeräten. Im Vortrag erklären die CTOs der beiden Unternehmen, wie der Einsatz der Shared Object Spaces Technologie den Codierungsaufwand für kollaborative Transaktionen drastisch reduziert und Cocoon den entscheidenden Entwicklungsvorsprung sichert source: http://www.aoug.at/exptreff_0204.htm Regards, Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Cocoon Workshop by Software AG and TECCO
-Original Message- From: Bertrand Delacretaz [mailto:[EMAIL PROTECTED]] Sent: Monday, November 25, 2002 4:17 PM To: [EMAIL PROTECTED] Subject: Re: Cocoon Workshop by Software AG and TECCO As I understand it this has nothing to do with the well-known Software AG, After reading it twice I got it ... I read Cocoon Technologies, break, Software AG ;-) But I think it is very confusing that a company called Cocoon offers similar products (at least in some way) to Apache Cocoon. Regards, Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Status of (Input)Modules
As input modules make the life of a cocoon developer much easier I like to use them (the concept is great!) What is the current status of them? I remember that there was a proposal by Stefano [http://marc.theaimsgroup.com/?l=xml-cocoon-devm=103428659914565w=2] introducing expanders and a answer by Carsten [http://marc.theaimsgroup.com/?l=xml-cocoon-devm=103433133012968w=2] proposing to reimplement the input modules. As far as I know there was no *final* result of the discussion or have I missed something? Best regards, Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[OT] Googlefight (was: RE: [ot] oscom berkeley)
At googlefight.com you can compare keywords - which one is requested by the google users more often. I tried cocoon vs. zope ;-) http://www.googlefight.com/cgi-bin/compare.pl?q1=cocoonq2=zopeB1=I%27m+Fee ling+Groggy%21%21+Go%21compare=1langue=us Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: [OT] Googlefight (was: RE: [ot] oscom berkeley)
From: Ivelin Ivanov [mailto:[EMAIL PROTECTED]] Wow. Even Apache vs Zope is in favor of the latter. How trustworthy is this source? I don't know - but it's entertaining ... Reinhard From: Reinhard Poetz [EMAIL PROTECTED] At googlefight.com you can compare keywords - which one is requested by the google users more often. I tried cocoon vs. zope ;-) http://www.googlefight.com/cgi-bin/compare.pl?q1=cocoonq2=zopeB1 =I%27m+Fee ling+Groggy%21%21+Go%21compare=1langue=us Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[Summary] RE: [control flow] Reloading Scripts
Hi Ovidiu, Thank you! Your patch solved the problem with the reload. Regards, Reinhard -Original Message- From: Ovidiu Predescu [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 01, 2002 9:42 AM To: Reinhard Poetz Cc: [EMAIL PROTECTED] Subject: Re: [control flow] Reloading Scripts Hi Reinhard, Please test the latest changes in the CVS, the code should work now. I still have to implement an automatic test of this feature, so that we can prevent this bug from happening in the future. Until then, please let me know if you still see problems. Regards, Ovidiu On Sunday, September 29, 2002, at 09:43 AM, Reinhard Poetz wrote: Ovidiu, Yestery I did some tests with the control flow - everything worked fine but the scripts have not been reloaded. In the cocoon.xconf I set the check-time for the flow-interpreters to 1 and then to 0 but both values didn't help. Only a restart led to a reload of the scripts. I know there were ?similar? (at least the symptom is the same) problems 5 weeks ago: [http://marc.theaimsgroup.com/?l=xml-cocoon-devm=102956711018659w=2]. Regards Reinhard -- Ovidiu Predescu [EMAIL PROTECTED] http://webweavertech.com/ovidiu/weblog/ (Weblog) http://www.geocities.com/SiliconValley/Monitor/7464/ (Apache, GNU, Emacs ...) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[control flow] Reloading Scripts
Ovidiu, Yestery I did some tests with the control flow - everything worked fine but the scripts have not been reloaded. In the cocoon.xconf I set the check-time for the flow-interpreters to 1 and then to 0 but both values didn't help. Only a restart led to a reload of the scripts. I know there were ?similar? (at least the symptom is the same) problems 5 weeks ago: [http://marc.theaimsgroup.com/?l=xml-cocoon-devm=102956711018659w=2]. Regards Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Fw: XML Journal poll.
Maybe somebody should place a link at http://xml.apache.org/cocoon Reinhard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Giacomo Pati Sent: Sunday, August 25, 2002 5:59 PM To: [EMAIL PROTECTED] Subject: Re: Fw: XML Journal poll. The number of votees are relatively small compared to the community people we have here on the list. So, I'd encourage everybody here to vote. Giacomo On Fri, 23 Aug 2002, Ivelin Ivanov wrote: It is weird that Apache is not the most valuable vendor and Cocoon is not the most innovative XML application ... yet. ;) - Original Message - From: Yukio Fujiwara [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, August 21, 2002 6:42 PM Subject: XML Journal poll. Hi Every One, Please make your voices heard at XML Journal poll. This is important to promote Cocoon and Batik. In this poll employees of a company can vote for their own products, which give them unfair advantage. At this moment Batik and Cocoon is trailing very badly. You may see the results at: http://www.sys-con.com/xml/readerschoice2002/ You may cast your vote at: http://www.sys-con.com/xml/readerschoice2002/nominationform.cfm Thanks, Yukio __ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: [vote]: Applying patches
9075:[PATCH] Contribution of SAP R/3(r) connectivity components Adding the possibility to access SAP from Cocoon is IMHO a very usefull feature. Is someone already using it? +1 As Michael Gerzabek and I are the committers of this patch some words: Yes, we are already using it successfully at some of our customers :-) - the example comes with it's own sub-sitemap - we will add a 'welcome'-page with some instructions how you can set up a connection to an SAP-R/3-system - add JCo.jar (available at http://service.sap.com/connectors -- if you have a SAP-system you have access to this site) - enter the correct logon-parameters in the configuration file -- that's it There was a question: What happens if there is any SAP-system available? -- As long as you only watch the welcome-page and don't click on the example - nothing -- The connection to SAP-R/3 is established at the first time you call a pipeline using our RFC-transformer There remains only one problem: --- In order to build our sources, JCo.jar (SAP Java Connector) is absolutly necessary. As JCo.jar is copyright-protected by SAP I can only offer following 'workaround': - case1: JCo.jar is not available -- during the build of Cocoon our prebuild web3-core.jar is taken and the source files are ignored - case2: JCo.jar is available -- during the build of Cocoon our prebuild web3-core.jar is ignored and the source files are compiled What do you think? Is it an acceptable solution? Regards, Reinhard PS: We improved some of the classes. If you like to include the connectivity-tool (web3-core) we will provide the new patch. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Performance of XSLTC
Hi, Today I tried to find out how much faster XSLTC compared to Xalan is. My result: there is hardly any difference in performance (maybe XSLTC is slightly faster). My test case: - I used a pipline with two xslt transformation steps. The first time I used the standard transformer (XSLTC) and then I changed the type to xalan. I'm using Cocoon2.1dev - checked it out today. I got the results (measurements) from the profiler. I know that this was not a valid test series and only a first impression - but ... ... now I have some questions: -- - Am I doing something wrong? - Do I have to make a real load test to get a difference in performance? - Did anybody get other/similar results? Regards, Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Cocoon 2.1 samples page
Sylvain, ../cocoon/samples/ dont't forget the last slash! Regards, Reinhard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 04, 2002 6:16 PM To: [EMAIL PROTECTED] Subject: Cocoon 2.1 samples page Hi, Where could I find the samples page in Cocoon 2.1?? No links on the index page (../cocoon/documents/index.html)! Thank you Sylvain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Continuations are broken?
-Original Message- From: Ovidiu Predescu [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 4:48 AM To: [EMAIL PROTECTED] Subject: Re: Continuations are broken? On 6/19/02 12:48 PM, Vadim Gritsenko [EMAIL PROTECTED] wrote: Hi Ovidiu, and hi all, Either I did not understood continuations or they do not work as advertised. Walk through this test case and tell what/who is wrong: 1) Access http://localhost:8080/cocoon/samples/flow/examples/calc/ 2) Type 10, Enter. 3) See page with A = 10. URL is http://localhost:8080/cocoon/samples/flow/examples/calc/kont/3f557504821 5621d3c1c32191d868b573f751c7f?a=10 4) Open another browser window with this URL. See page with A = 10 5) Window 1: Enter B = 10 URL will be: http://localhost:8080/cocoon/samples/flow/examples/calc/kont/1b261330647 176442d5f45335c406211594a1d4f?b=10submit=Enter 6) Window 2: Enter B = 20 URL will be: http://localhost:8080/cocoon/samples/flow/examples/calc/kont/6034270b2e1 a6b7c4a591512417a3c3c437c?b=20 7) Window 1: Select plus, click Do It 8) See in Window 1: Result = 30. I expected to see 20, because B = 20 was entered in another window and went to continuation 6034270b2e1a6b7c4a591512417a3c3c437c, and B = 10 should be in continuation 1b261330647176442d5f45335c406211594a1d4f, however, both continuations has same B = 20. Am I mistaken? No, you're not mistaken, this is the correct behavior. Rhino used to have the behavior you described, but Christopher and I decided is better to have the current one, which is more useful to real applications. One effect of this change is that you can no longer implement what-if scenarios as easy as before. Christopher and I were talking about various solutions, but none of them is cheap enough at runtime to be worth the effort. What is the advantage of continuations? It seems that the calculator example has only one state ... Regards, Reinhard Regards, -- Ovidiu Predescu [EMAIL PROTECTED] http://www.geocities.com/SiliconValley/Monitor/7464/ (Apache, GNU, Emacs...) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: [RT] Flowmaps
So, what about a general interface to flow controller (be it a flow script or a flow map) that will allow to use any implementation you like? I know, I've already ask about this before, just want to remind about it. And as I've already said, though, I like the idea of continuations very much, but I can't and don't want to use your JS-based implementation in our product, but would like to plugin our XML-based flow engine (it is also supports something like continuations - we call it 'history' here). After a look into cocoon.xconf I think this is already possible: flow-interpreters default=JavaScript reload-scripts=true check-time=2000 logger=flow component-instance name=JavaScript class=org.apache.cocoon.components.flow.javascript.JavaScriptInterpreter load-on-startupresource://org/apache/cocoon/components/flow/javascript/sys tem.js/load-on-startup /component-instance !-- Temporarily disable Scheme, until full support is completed -- !-- component-instance name=Scheme class=org.apache.cocoon.components.flow.scheme.SchemeInterpreter load-on-startupresource://org/apache/cocoon/components/flow/scheme/system. scm/load-on-startup heap/WEB-INF/sisc.heap/heap /component-instance -- /flow-interpreters Regards, Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Cocoon in HEAD Hangs, is it really only me?
-Original Message- From: Jeremy Quinn [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 13, 2002 11:49 AM To: [EMAIL PROTECTED] Subject: Cocoon in HEAD Hangs, is it really only me? Hi All, Several people have commented that Cocoon 2 in HEAD hangs when Source files or XSLT files are altered, requiring that TomCat be killed. I have the same problems! Is this really only effecting a few people? Is this a system specific problem? my environment: Win2k_prof, tomcat401, cocoon2.1dev Who of you are successfully running the HEAD branch without this problem? What platform are you using? Thanks for any help. regards Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: XMLForms and Flowmap
We are looking for someone to step up and show us how these two can work together in a nice way. Interested? Ivelin Yes I am but my time and my java knowledge are limited (... but I'm learning) Anyway, I'll try it. Maybe there is somebody who has already some experience (Daniel?) who want's to join. Reinhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
AW: [XMLForms]
Ivelin, I added the parameter xmlform-data to the Sitemap. (map:parameter name=xmlform-data value=data.xml/) The bean uses this parameter to read the XML-File in order to set the values in the bean. What was my goal? I wanted to set all parameters without java coding. I hope I did it the right way - what do you think? As soon as the current version in the cvs will work again, I'll provide the patch. Regards, Reinhard -Ursprüngliche Nachricht- Von: Ivelin Ivanov [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 11. Juni 2002 15:09 An: Reinhard Poetz; [EMAIL PROTECTED] Betreff: Re: [XMLForms] Reinhard, Please submit the patch through Bugzilla and send me a note. I will look at it and we will discuss it. Can you explain with a few lines, what is the patch doing? Thanks, Ivelin Reinhard Poetz wrote: Ivelin, Yesterday I had a deeper look into the new XMLForms implementation. As a found it very interesting I startet to implement my own examples with the result that I wrote a bean, that uses an XML document which is set in the sitemap as input source. As I needed the SourceResolver and the sitemap parameters in the Bean I had to change the reflection part of the AbstractXMLAction and I had to write a new constructor for Beans. If the community is interested in a patch I can provide it by the end of this week. Regards, Reinhard Reinhard PötzEFP Consulting, Vienna, Austria [EMAIL PROTECTED] http://www.efp.cc http://www.efp.cc/v/rpo SAP Internet Solutions - Content Management - Knowledge Management -- -= Ivelin =- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
AW: [XMLForms]
-Ursprüngliche Nachricht- Von: Reinhard Poetz [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 11. Juni 2002 15:45 An: [EMAIL PROTECTED] Cc: Ivelin Ivanov Betreff: AW: [XMLForms] Ivelin, I added the parameter xmlform-data to the Sitemap. (map:parameter name=xmlform-data value=data.xml/) The bean uses this parameter to read the XML-File in order to set the values in the bean. What was my goal? I wanted to set all parameters without java coding. I hope I did it the right way - what do you think? As soon as the current version in the cvs will work again, I'll Of course I meant the current version of cocoon2. The build process is broken at the moment. Reinhard provide the patch. Regards, Reinhard -Ursprüngliche Nachricht- Von: Ivelin Ivanov [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 11. Juni 2002 15:09 An: Reinhard Poetz; [EMAIL PROTECTED] Betreff: Re: [XMLForms] Reinhard, Please submit the patch through Bugzilla and send me a note. I will look at it and we will discuss it. Can you explain with a few lines, what is the patch doing? Thanks, Ivelin Reinhard Poetz wrote: Ivelin, Yesterday I had a deeper look into the new XMLForms implementation. As a found it very interesting I startet to implement my own examples with the result that I wrote a bean, that uses an XML document which is set in the sitemap as input source. As I needed the SourceResolver and the sitemap parameters in the Bean I had to change the reflection part of the AbstractXMLAction and I had to write a new constructor for Beans. If the community is interested in a patch I can provide it by the end of this week. Regards, Reinhard Reinhard PötzEFP Consulting, Vienna, Austria [EMAIL PROTECTED] http://www.efp.cc http://www.efp.cc/v/rpo SAP Internet Solutions - Content Management - Knowledge Management -- -= Ivelin =- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[XMLForms]
Ivelin, Yesterday I had a deeper look into the new XMLForms implementation. As a found it very interesting I startet to implement my own examples with the result that I wrote a bean, that uses an XML document which is set in the sitemap as input source. As I needed the SourceResolver and the sitemap parameters in the Bean I had to change the reflection part of the AbstractXMLAction and I had to write a new constructor for Beans. If the community is interested in a patch I can provide it by the end of this week. Regards, Reinhard Reinhard PötzEFP Consulting, Vienna, Austria [EMAIL PROTECTED] http://www.efp.cc http://www.efp.cc/v/rpo SAP Internet Solutions - Content Management - Knowledge Management - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: NekoHTML in Cocoon....
What are there any differences to HTML Tidy (speed, functionality)? Reinhard -Original Message- From: Jörn Heid [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 14, 2002 1:27 PM To: [EMAIL PROTECTED] Subject: NekoHTML in Cocoon Necko is an HTML parser based on Xerces who can parse 'normal' HTML (not XHTML) and prodcues pure XML (SAX). http://www.apache.org/~andyc/nekohtml/doc/index.html Just thinking if it could be usefull... (I haven't tried it yet ;). One possibible use case would be the ability for Cocoon developers to use old html files and change them with XSLT. E.g. including news pages not based on XML in Cocoon, filtering information from external pages and so on. What do you think? I will ask Andy Clark for permission if you think it would be usefull for Cocoon. JOERN - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Web3 (was: [Announcement] Web3 - SAP R/3 connection components)
.-. | Thank you all for the great feedback! | `-' There have been a few questions we want to answer: Publishing Web3-Core We plan to publish Web3-Core at the end of next week (there are a few things to polish and a simple example has to be written). As proposed from Davanum we will post a patch at BugZilla. (Bert: If you are interested in Web3 we will post a ZIP with all necesary files at cocoon-dev.) Why we have called it Web3-Core? -- We have split Web3 into two parts: - Web3-Core (published under the The Apache Software License) - synchronos call mode (transformer) - sap style structure model - only inbound (Web3 calls SAP) connections - seamless cocoon2 integration - Web3 (extended) - 2 further call modes (asynchrounos, cached) - persistent xml database layer - user aware logon mechanism for RFC-connections - outbound (SAP calls Web3) connections - enhanced scheduling facilities - administration gui - bapi implementation wizard - monitoring Web3-Core and Cocoon2 - We think it is a good idea to put Web3-Core into the scratchpad of Cocoon2. As soon as cocoon blocks are available we will provide Web3 as a cocoon block. Further information --- Have a look at http://www.efp.cc/web3 (Granted, at the moment the information is rudimentary but it will be extended in the near future :-) or mailto:[EMAIL PROTECTED] Licencing - In order to use Web3 you need the Java Connector (JayCo) from SAP. Here the licence terms (source: http://service.sap.com/connectors) .-. |SAP Java Connector is only available from| |SAP for connecting Java Applications to SAP | |systems. Other than the above permitted usage| |is not allowed by SAP. The terms and regulations | |of the respective End User License Agreement | |shall otherwise apply. | | | |Java® is a registered trademark of | |SunMicrosystems, Inc., 901 San Antonio Road, | |Palo Alto, CA 94303 US. | `-' We are not lawyers but we think that means you should have a look into YOUR licence agreement with SAP ;-) Regards, Reinhard / Michael - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - EFP Consulting GmbH, Praterstraße 45, 1020 Wien - Austria www.efp.cc - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
AW: Cocoon + UserAgent Strings
Tony, Have a look at http://marc.theaimsgroup.com/?l=xml-cocoon-devm=101412181609134w=2 I extented the HTMLGenerator and use the httpclient-library of jakarta. Using this library you can set the UserAgent in the http-header. I haven't had the time yet to complete it (see http://marc.theaimsgroup.com/?l=xml-cocoon-devm=101412719423893w=2) and to send the diff to bugzilla. (planned for the next weeks). Reinhard -Ursprungliche Nachricht- Von: Tony Collen [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 08. Marz 2002 06:19 An: [EMAIL PROTECTED] Betreff: Cocoon + UserAgent Strings Hi all.. I posted this message to cocoon-users but it might be more likely to be answered here... I'm playing around with Cocoon, and I'm using map:generate type=html src=http://foo.bar; / to generate some XHTML from a website. I'm getting back a 403 Denied error from the server, and I've deduced that Cocoon is being denied access to the URL based on the User-Agent string that it sends. I did a little snooping and I came up with the following info out of my wwwlogs: GET / HTTP/1.1 200 18919 - Java1.3.1_01 Is there any way, short of digging through code, to change the User-Agent string that Cocoon sends? If not, is there someone who knows the Cocoon source well enough to make the User-Agent string something that could be configured through, say, cocoon.xconf? Tony Collen -= Web Programmer NHGIS: National Historical Geographic Information System http://www.nhgis.org -= - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
HTTPHTMLGenerator
I had the same problem as described in bug #6520 (http://marc.theaimsgroup.com/?l=xml-cocoon-devm=101402671004632w=2). I solved this problem using the HTTPClient (commons-httpclient-20011012.jar). The use of the HTTPClient makes it possible to use the POST-paramters and HEADER-parameters of the client/cocoon-connection. Browser ---Cocoon--- HTTP-Resource Request HTTPHTMLGenerator using HEAD POST of the Request I called this generator (based on the HTML-Generator) HTTPHTMLGenerator. Using this generator solved my problem posted last december (using Cocoon2 as Proxy): - http://marc.theaimsgroup.com/?l=xml-cocoon-devm=100758023726189w=2 - http://marc.theaimsgroup.com/?l=xml-cocoon-devm=100763795331083w=2 The HTTPHTMLConnector makes it very easy to integrate existing web applications into cocoon. Attached you find the sources (HTTPHTMLGenerator.java) - tested with Cocoon 2.0.1/Tomcat4.0.1/Win2K-Prof Reinhard Pötz HTTPHTMLGenerator.java Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
AW: Proxy Component?
-Ursprüngliche Nachricht-
Von: Piroumian, Konstantin [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 06. Dezember 2001 08:53
An: [EMAIL PROTECTED]
Betreff: Re: Proxy Component?
Is there any possibility to use Cocoon as proxy? I have some old
applications (written in PHP) that I want to use in combination with
cocoon
(I want to use some actions)
for example:
map:match pattern=old_application/**
map:act type=checkSession/
map:proxy src=http://old_application_server/{1}/
/map
map:redirect-to uri=login.html/
/map:match
Currently I solved the problem by using the HTML-generator but
if I use it
the header information of the client will get lost.
If there is no available component - what would be the best way of
implementing it?
You can create a reader for this purpose. I needed something like that to
get direct output from a JSP page (that is generating HTML, not XML) and
have implemented the JSPReader. Now you can use it like this:
map:match pattern=old_application/**
map:act type=checkSession/
map:read src=/jsp/page.jsp/
/map
map:redirect-to uri=login.html/
/map:match
Does the reader use the client's header data (for example the User-Agent) or
get this data lost and are replaced with some other values? (I tested this
some month ago with the result that the values in the header were replaced.)
I think of a component that works like a resource reader but uses the
client's http-header data. What do you think?
Regards,
Reinhard Poetz
So, I hope you got the idea.
Btw, developers, there are ServletGenerator and JSPGenerator componenets
that implement almost the same thing: get output from a servlet then
generate XML from it. JSPGeneretor uses JSPEngine for that.
Maybe it'll be
better to have something like ServletComponenet and use it either in
generators or readers that have to interact with other servlets?
Regards,
Konstantin Piroumian
Regards,
Reinhard
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
