Adrien Guillon wrote:
What is the official design reason for resources not being accessible by
child site maps ?
I guess originally this has just been forgotten to be implemented.
Any suggestions would be greatly appreciated!
With 2.2 we will have a different solution, the virtual
Carsten Ziegeler wrote:
Adrien Guillon wrote:
What is the official design reason for resources not being accessible by
child site maps ?
I guess originally this has just been forgotten to be implemented.
Any suggestions would be greatly appreciated!
With 2.2 we will have a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Don't know if others have that too. Cannot compile trunk as the
cocoon-forms-impl block seems to miss dependency on different commons
jars (jxpath, lang, ...).
Anyone else?
And I had to locally fix the OSGiSpringECMFactory.java class which
Giacomo Pati schrieb:
Don't know if others have that too. Cannot compile trunk as the
cocoon-forms-impl block seems to miss dependency on different commons
jars (jxpath, lang, ...).
Anyone else?
And I had to locally fix the OSGiSpringECMFactory.java class which seems
to miss the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 4 May 2006, Carsten Ziegeler wrote:
Date: Thu, 04 May 2006 12:19:09 +0200
From: Carsten Ziegeler [EMAIL PROTECTED]
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: Cannot compile trunk
Giacomo Pati schrieb:
Don't
Giacomo Pati wrote
If the fix mentioned above is all we have to do (couldn't get it to
compile ATM and thus don't know if that's all) it would be easy to
upgrade to 1.2.7.
I guess the mentioned fix should be all and imho it makes sense to
upgrade to 1.2.7 if possible (use always the
LDAPTransformer: ClassCastException with Binary fields
--
Key: COCOON-1842
URL: http://issues.apache.org/jira/browse/COCOON-1842
Project: Cocoon
Type: Bug
Components: Blocks: Naming
Versions: 2.1.9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 4 May 2006, Giacomo Pati wrote:
Date: Thu, 4 May 2006 12:28:25 +0200 (CEST)
From: Giacomo Pati [EMAIL PROTECTED]
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: Cannot compile trunk
Giacomo Pati wrote
Anybody any idea?
Strange! I'm using latest m2 (2.0.4) and I have a mirror setup in my
settings.xml:
mirror
idsunsite.dk/id
urlhttp://mirrors.sunsite.dk/maven2/url
mirrorOfcentral/mirrorOf
/mirror
Don't know if that makes a difference.
What
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 4 May 2006, Carsten Ziegeler wrote:
Date: Thu, 04 May 2006 15:06:19 +0200
From: Carsten Ziegeler [EMAIL PROTECTED]
Reply-To: dev@cocoon.apache.org
To: dev@cocoon.apache.org
Subject: Re: Cannot compile trunk
Giacomo Pati wrote
Anybody
LDAPTransformer: add-entry tag doesn't work
---
Key: COCOON-1843
URL: http://issues.apache.org/jira/browse/COCOON-1843
Project: Cocoon
Type: Bug
Components: Blocks: Naming
Versions: 2.1.9
Reporter: Nicola
I will investigate the virtual sitemap components, and see what I can see...
thanks for the pointers.
Cocoon is pretty crazy... how does one normally find out about all these nifty
features?
AJ
On 4 May 2006 4:12 am, Upayavira wrote:
Carsten Ziegeler wrote:
Adrien Guillon wrote:
What
Another problem... you mentioned this is in 2.2... I'm still on 2.1.9. Is
there a method by which I could take the Virtual Sitemap Components and put
that functionality into 2.1.9? As in, is it just a plain old transformer
that I can take, or would this be too difficult a thing to do ?
Adrien Guillon wrote:
Another problem... you mentioned this is in 2.2... I'm still on 2.1.9. Is
there a method by which I could take the Virtual Sitemap Components and put
that functionality into 2.1.9? As in, is it just a plain old transformer
that I can take, or would this be too
Thanks David.
Best Regards,
Antonio Gallardo.
David Crossley escribió:
Antonio Gallardo wrote:
Pier ping! :-)
There are other people here who can do that.
Simone, i found that you have two Jira usernames
s.gianni and [EMAIL PROTECTED]
The latter only had one issue, so i moved it
Daniel Fagerstrom wrote:
What I mean is that the tree processor currently get the path to the
sitemap.xmap from the configuration file. If the tree processor stop
being a managed component and just is setup in the SitemapServlet, it
will still need to get the sitemap path from somewhere. IMO
Sylvain Wallez skrev:
Daniel Fagerstrom wrote:
What I mean is that the tree processor currently get the path to the
sitemap.xmap from the configuration file. If the tree processor stop
being a managed component and just is setup in the SitemapServlet, it
will still need to get the sitemap
Carsten Ziegeler wrote:
What about others? Are Giacomo and I the only ones trying to build 2.2?
nope :) I had actually spotted the spring compilation the day after you
committed it and was wondering why continuum hadn't notified us of this.
It turns out that CI uses incremental compilation
How difficult would it be to alter 2.1.9 instead, to allow access to resources
defined in parent sitemaps from children sitemaps? If I can do that, I can
easily change the resource access methods to the virtual sitemap components
when 2.2 rolls out...
AJ
On 4 May 2006 10:03 am, Carsten
Adrien Guillon schrieb:
How difficult would it be to alter 2.1.9 instead, to allow access to
resources
defined in parent sitemaps from children sitemaps? If I can do that, I can
easily change the resource access methods to the virtual sitemap components
when 2.2 rolls out...
That
Okay, I really prefer this solution... porting my code from resources to
virtual sitemap components in the future will be very easy from what I have
seen. Could you please direct me to a few classes to look at and
documentation? Maybe any pointers you could give for how to proceed? This
is
Take a look at
http://marc.theaimsgroup.com/?l=xml-cocoon-devm=106649931022515w=2 for
a description on how the treeprocessor works. The function of the
virtual sitemap components is described here
http://marc.theaimsgroup.com/?l=xml-cocoon-devm=111316710610638w=2. I
don't know if the VPCs
Daniel Fagerstrom wrote:
Take a look at
http://marc.theaimsgroup.com/?l=xml-cocoon-devm=106649931022515w=2
for a description on how the treeprocessor works. The function of the
virtual sitemap components is described here
http://marc.theaimsgroup.com/?l=xml-cocoon-devm=111316710610638w=2.
I
Sylvain Wallez skrev:
Daniel Fagerstrom wrote:
...
IIRC, there are a few subtle things involved in the resource handling
code, so be prepared to that you might need to spend some time
learning how it works ;)
Views and resources are handled similarily as things that are purely
internal to a
Automated build for cocoon-docs FAILED
Log attached.
--
Forrestbot run ended at 05 May 12:24 AM
Using Forrest 0.8-dev
Forrestbot administrator: ForrestBot
--
[echo]
... Forrest render START 2006-05-05 12:02:11
... Rendering docs in
25 matches
Mail list logo
