Round II:
Here's my transformer code, (I know there's extra imports I don't need just yet):
-
package com.openweather.cocoon.transformation;
import org.apache.cocoon.transformation.AbstractSAXTransformer;
import org.apache.cocoon.environment.SourceResolver;
import org.apache.cocoon.ProcessingEx
Hi:
JCS is a reality in Cocoon thanks to Carsten and the JCS team that was
quick responsive and very helpful.
Before we used JISP. Now we can deprecate JISP support and if someone need
it too much there is always a path to use it through JCS.
The proposal is:
Deprecated JISP support in 2.1.5 an
Sorry not be more explicit first time, and, yes I can:
http://wiki.apache.org/cocoon/MIDI
see: ==Sample Xmidi==
http://wiki.apache.org/cocoon/Action
see: === Built-in Actions ===
Cheers,
Mark
On 20 May 2004, at 20:08, Upayavira wrote:
Mark Leicester wrote:
Hi Upayavira,
Keep up the great work! I ha
Mark Leicester wrote:
Hi Upayavira,
Keep up the great work! I had a little look around and noticed that
2nd and 3rd level headings don't appear to convert correctly.
Can you give an example?
Regards, Upayavira
Hi Upayavira,
Keep up the great work! I had a little look around and noticed that 2nd
and 3rd level headings don't appear to convert correctly.
Mark
On 20 May 2004, at 17:17, David Crossley wrote:
Upayavira wrote:
Well, I must be a regexp whizz, because I got this working within five
minutes. I
Upayavira wrote:
> >
> Well, I must be a regexp whizz, because I got this working within five
> minutes. I was distracted by the fact that it didn't work on my local
> Moin, but it works on Apache's so it is fine.
Nice. Thanks for persisting.
--David
David Crossley wrote:
But it is odd how it works. JXTemplateGenerator will only see
TemplateGenerator as the link without the JX. It is going to be tough
just using this, as even when we've done the conversion people are going
to be inadvertently adding CamelCase to their new Wiki pages.
I gue
Antonio Gallardo wrote:
>
> I hope we soon will get rid of jisp. What about to deprecate
> current JISP support? If someone want to use JISP there is
> still a posibility using JCS.
>
+1
Carsten
Upayavira wrote:
It is there somewhat more akin to an anteater test. Therefore, given
these facts, I propose to leave the CocoonBeanTestCase disabled, and
simply remove the test suite (as it isn't needed anyway.). I will
continue to use the test case locally on my own testing, and will
reflect
Ugo Cei wrote:
Upayavira wrote:
I need to remove the test-suite and use samples/test, and confirm
that Ugo's fixes have made the CocoonBeanTestCase work, and then
re-enable it.
A word of caution. My fixes add the blocks directory and
block-provided jars to the classpath for tests and make the
10 matches
Mail list logo
