Den 2. sep. 2008 kl. 03.17 skrev David Crossley:
I switched that cron job off now. The skins-based one will
still be operating.
Thanks.
I will start committing now, first some small preparatory commits, and
then one big commit that will update the pdf plugin in one step. This
large update
Sjur Moshagen wrote:
> Thorsten Scherler:
> >>
> >>But it does NOT work if I DON'T add it manually there, even though
> >>the
> >>entity is now defined both in core and in project within
> >>$FORREST_HOME.
> >
> >Hmm that is weird. I have to admit unless like David I am not the
> >expert
> >i
Thorsten Scherler wrote:
> Sjur Moshagen wrote:
> > Thorsten Scherler:
> > >>
> > >> But the basic issue is that I don't want to commit, because I know I
> > >> would break PDF functionality in dispatcher - but I won't get any
> > >> feedback if I don't commit. A separate branch could be overkill,
Den 1. sep. 2008 kl. 14.36 skrev Thorsten Scherler:
But it does NOT work if I DON'T add it manually there, even though
the
entity is now defined both in core and in project within
$FORREST_HOME.
Hmm that is weird. I have to admit unless like David I am not the
expert
in the entity config
On Mon, 2008-09-01 at 14:05 +0300, Sjur Moshagen wrote:
> Den 22. aug. 2008 kl. 11.53 skrev Thorsten Scherler:
>
> > On Fri, 2008-08-22 at 11:44 +0300, Sjur Moshagen wrote:
> >> Den 22. aug. 2008 kl. 11.29 skrev Sjur Moshagen:
> >>
> >>> But when I start up Forrest again, I get the following error
On Mon, 2008-09-01 at 13:46 +0300, Sjur Moshagen wrote:
> Den 27. aug. 2008 kl. 12.47 skrev Thorsten Scherler:
>
> >> But the basic issue is that I don't want to commit, because I know I
> >> would break PDF functionality in dispatcher - but I won't get any
> >> feedback if I don't commit. A separ
Den 22. aug. 2008 kl. 11.53 skrev Thorsten Scherler:
On Fri, 2008-08-22 at 11:44 +0300, Sjur Moshagen wrote:
Den 22. aug. 2008 kl. 11.29 skrev Sjur Moshagen:
But when I start up Forrest again, I get the following error:
CAUSE:
The entity "pdf-config-file" was referenced, but not dec
Den 27. aug. 2008 kl. 12.47 skrev Thorsten Scherler:
But the basic issue is that I don't want to commit, because I know I
would break PDF functionality in dispatcher - but I won't get any
feedback if I don't commit. A separate branch could be overkill, and
dispatcher is in the whiteboard... Woul
On Wed, 2008-08-27 at 01:20 +0300, Sjur Moshagen wrote:
> Den 26. aug. 2008 kl. 12.49 skrev Thorsten Scherler:
>
> >> I need to review your commit.
> > ...
> >
> > I had a quick look on the weekend but I am not sure. Many featured you
> > described in this thread seems to be not commited yet. Is t
Den 26. aug. 2008 kl. 12.49 skrev Thorsten Scherler:
I need to review your commit.
...
I had a quick look on the weekend but I am not sure. Many featured you
described in this thread seems to be not commited yet. Is that
correct,
because you wrote that you have some stack of changes on your
On Fri, 2008-08-22 at 11:37 +0200, Thorsten Scherler wrote:
> On Fri, 2008-08-22 at 12:29 +0300, Sjur Moshagen wrote:
> > Den 22. aug. 2008 kl. 12.12 skrev Sjur Moshagen:
> >
> > >> That is why I wrote in the other mail that best is to implement the
> > >> default in the core.
> > >
> > > Ok, I'll
On Fri, 2008-08-22 at 12:29 +0300, Sjur Moshagen wrote:
> Den 22. aug. 2008 kl. 12.12 skrev Sjur Moshagen:
>
> >> That is why I wrote in the other mail that best is to implement the
> >> default in the core.
> >
> > Ok, I'll add it there as well.
>
> Done as of r688036.
>
> This case is closed,
Den 22. aug. 2008 kl. 12.12 skrev Sjur Moshagen:
That is why I wrote in the other mail that best is to implement the
default in the core.
Ok, I'll add it there as well.
Done as of r688036.
This case is closed, as soon as I commit all my changes to the pdf
plugin (still some work left todo
Den 22. aug. 2008 kl. 11.53 skrev Thorsten Scherler:
On Fri, 2008-08-22 at 11:44 +0300, Sjur Moshagen wrote:
Den 22. aug. 2008 kl. 11.29 skrev Sjur Moshagen:
But when I start up Forrest again, I get the following error:
CAUSE:
The entity "pdf-config-file" was referenced, but not decl
On Fri, 2008-08-22 at 11:44 +0300, Sjur Moshagen wrote:
> Den 22. aug. 2008 kl. 11.29 skrev Sjur Moshagen:
>
> > But when I start up Forrest again, I get the following error:
> >
> > CAUSE:
> > The entity "pdf-config-file" was referenced, but not declared.
>
> Forget about that, I didn't noti
On Fri, 2008-08-22 at 11:29 +0300, Sjur Moshagen wrote:
> Den 22. aug. 2008 kl. 09.54 skrev Thorsten Scherler:
>
> > Actually a similar problem that you are trying to solve has been
> > solved
> > by David a while back. I remember because while updating I stumble
> > over
> > the solution agai
Den 22. aug. 2008 kl. 11.29 skrev Sjur Moshagen:
But when I start up Forrest again, I get the following error:
CAUSE:
The entity "pdf-config-file" was referenced, but not declared.
Forget about that, I didn't notice that Forrest had already copied in
an entity file in my $PROJECT_HO
Den 22. aug. 2008 kl. 09.54 skrev Thorsten Scherler:
Actually a similar problem that you are trying to solve has been
solved
by David a while back. I remember because while updating I stumble
over
the solution again.
Have a look in the main sitemap or the internal.xmap of the
dispatcher.
Den 22. aug. 2008 kl. 09.54 skrev Thorsten Scherler:
...
As you can see each project can provide a symbols-project-v10.ent
which
can override the configuration.
...
I think that is a quite elegant solution to our problem without the
need
for an extended debugging session.
Absolutely -
On Fri, 2008-08-22 at 08:30 +0300, Sjur Moshagen wrote:
> I think I will leave it as it is then, at least for the moment.
> Eclipse has turned out to be a steep learning thing for me (I have
> tried a couple of times, but I don't grasp the idea of the interface -
> it is just confusing to me)
I think I will leave it as it is then, at least for the moment.
Eclipse has turned out to be a steep learning thing for me (I have
tried a couple of times, but I don't grasp the idea of the interface -
it is just confusing to me), and setting this up would take more time
than I have at the
On Wed, 2008-08-20 at 11:05 +0300, Sjur Moshagen wrote:
> Den 20. aug. 2008 kl. 09.33 skrev Thorsten Scherler:
...
> > If the link rewriter is screwing things up you could debug
> > LinkRewriterTransformer. Anyway this transformer normally never should
> > rewrite anything in the sitemap.xmap.
>
>
Den 20. aug. 2008 kl. 09.33 skrev Thorsten Scherler:
On Wed, 2008-08-20 at 07:55 +0300, Sjur Moshagen wrote:
Den 19. aug. 2008 kl. 07.43 skrev David Crossley:
So we can see that the opening "{" and up to the ":" are processed.
I am not sure what is doing this processing. Perhaps the
LinkRewr
On Wed, 2008-08-20 at 07:55 +0300, Sjur Moshagen wrote:
> Den 19. aug. 2008 kl. 07.43 skrev David Crossley:
>
> > So we can see that the opening "{" and up to the ":" are processed.
> >
> > I am not sure what is doing this processing. Perhaps the
> > LinkRewriter block.
>
> Is that Forrest? Or
Den 19. aug. 2008 kl. 07.43 skrev David Crossley:
So we can see that the opening "{" and up to the ":" are processed.
I am not sure what is doing this processing. Perhaps the
LinkRewriter block.
Is that Forrest? Or Cocoon? (ie, is it something we can easily do
something about?)
Best reg
Den 19. aug. 2008 kl. 10.19 skrev Sjur Moshagen:
Then search the locationmap.log file for strings like:
"location returned for hint: pdf."
Otherwise if it is not found, it keeps looking through various
locationmaps until it runs out of places to look. There is no
"not found" type message.
Ok,
Den 19. aug. 2008 kl. 07.22 skrev David Crossley:
Sjur Moshagen wrote:
(*) I don't *know* that the matching file is found, I'm just assuming
here - how can I check that?
Turn on logging first:
http://forrest.apache.org/faq.html#logs
Thanks for the hint.
Then search the locationmap.log fi
Den 18. aug. 2008 kl. 15.05 skrev Thorsten Scherler:
To sum up:
1. if the path is hardcoded in the sitemap, all is ok
2. if the path is empty in the sitemap, all is ok
3. if the path is looked up via lm, and a matching file is found(*),
the path returned is garbage
4. if the path is looked up v
Sjur Moshagen wrote:
> Could it be that it is the fact that the locationmap lookup in the
> sitemap is specified as element content, and not as an attribute
> value? All other examples I have found using lm has the lm lookup in
> an attribute. That is, I'm thinking that this case is not so mu
Sjur Moshagen wrote:
>
> (*) I don't *know* that the matching file is found, I'm just assuming
> here - how can I check that?
Turn on logging first:
http://forrest.apache.org/faq.html#logs
Then search the locationmap.log file for strings like:
"location returned for hint: pdf."
Otherwise if it
On Mon, 2008-08-18 at 14:34 +0300, Sjur Moshagen wrote:
> >> To me it looks like the locationmap, when nothing is found, returns
> >> the path
> >> to the locationmap.xml file (excluding the filename), combined with
> >> the last
> >> part of the lm: specification in the sitemap: 'pdf.user-conf
Could it be that it is the fact that the locationmap lookup in the
sitemap is specified as element content, and not as an attribute
value? All other examples I have found using lm has the lm lookup in
an attribute. That is, I'm thinking that this case is not so much
tested compared to the u
To me it looks like the locationmap, when nothing is found, returns
the path
to the locationmap.xml file (excluding the filename), combined with
the last
part of the lm: specification in the sitemap: 'pdf.user-config}'
An empty locationmap selection:
returns th
On Mon, Aug 18, 2008 at 6:29 AM, Sjur Moshagen <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I'm trying to set up locationmap-based user configuration of the
> FOPNGSerializer, but I'm having some problems.
>
> In the present output.xmap within the pdf plugin, FOPNGSerializer is
> defined/initialised
Hello all,
I'm trying to set up locationmap-based user configuration of the
FOPNGSerializer, but I'm having some problems.
In the present output.xmap within the pdf plugin, FOPNGSerializer is
defined/initialised as follows:
src="org.apache.cocoon.blocks.fop.FOPNGSerializer" mim
35 matches
Mail list logo
