hi yves,
maybe you could simply use one of the Cocoon IncludeTransformers, so that
your text file is included before the XSP is compiled and executed.
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von Yves Vindevogel
Gesendet: Donnerstag, 12.
did you mistype a map:act as act?
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von poornima ponnuswamy
Gesendet: Donnerstag, 19. Dezember 2002 05:11
An: [EMAIL PROTECTED]
Betreff: Problem in running XForm samples
I am using cocoon2.1, Apache
as you said yourself, you set the logging level to ERROR, so you still get
errors. you could set the level higher, but then you would get the
respective messages.
but I think you could just remove all the configured log targets.
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
hi stavros,
I don't know line 1039 of your build file, but something in there seems to
refer to a local path (the path shown in the error message). and as the
exception says, it's a malformed URL. the correct one would start like
file://c:/Documents...
-Ursprungliche Nachricht-
Von:
hi lenya,
you compile the java Action code like any other java code, i.e. via javac,
IDE, etc.
if you package the resulting classes as JAR this has to be in WEB-INF/lib of
your cocoon. otherwise the classes go to WEB-INF/classes of you cocoon.
note that the package structure has to be reflected
the stacktrace says that the AbstractMultiAction can't be found.
make sure that this class is in the classpath (it should be in the cocoon
JAR, but you better check that out).
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von Julian Klein
Gesendet:
are you using your xsp as an action via ServerPagesAction?
are you using your xsp as the target for the form action? like this:
form action=save-form-data ...
in your sitemap:
map:match pattern=save-form-data
map:generate type=serverpages src=save-form-data.xsp/
hi,
as you may know, actions get parameters via avalon Parameters. if you look
at the API you see that the parameters in the end can only contain strings.
so you have no direct way to pass objects of other type.
but you could pass your objects e.g. via request/session attributes. have a
look at
well, it does work, I tried it out.
only one generator per pipeline, that's right (only one generator can be set
at pipeline setup time). but in this case, there is only one pipeline, that
is the ServerPagesGenerator. the redirect is to another pipeline.
anyway, I can imagine the use of XSP
hi julio,
In lack of details I don't completely understand your use case, but if
you're trying to code in the stylesheet you should consider writing a
transformer for your needs.
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von jcplerm
Gesendet:
AFAIR your sitemap variable is only accessible within your map:act block,
something like this:
sitemap-snippet
map:match pattern=view/**
map:act type=task
map:parameter name=method value=doAddSubjectsAndMyCategories/
map:parameter name=task-subject-node
hi cyril,
the problem is the '{critere}'. you have no sitemap component creating this
sitemap variable. but in this case you don't need that anyway since you are
instructing the XSLT-/TraxTransformer to 'use-request-parameters', i.e. make
all request parameters available to the stylesheet as
hi julian,
sorry, I haven't worked with XIndice yet. but from looking at the XIndice
sources the NPE seems to be caused by the key being null. as already
mentionend, I'm not into XIndice so I don't know where that key is being
specified (created by your action, maybe?), but perhaps this info
hi johannes,
I think you should be matching the request parameter(s) via the respective
matcher, i.e. RequestParameterMatcher. the default (WildcardURI) matcher
most probably only matches on the URI.
so (from the top of my head) it would be something like:
!--php try--
map:pipeline
map:match
hi jordi,
please have a look at cocoon's web.xml. there's an init-param named
show-time, which, when set to yes/true makes cocoon add the processing time
to each response.
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von Jordi Valldaura
you should probably code that as an action, that you can use in your
sitemap. please see relevant docs.
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von gv
Gesendet: Dienstag, 28. Januar 2003 21:13
An: [EMAIL PROTECTED]
Betreff: How can I
one might be able to better help you if the error message was translated.
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von CARLETTA ANGELO
Gesendet: Dienstag, 28. Januar 2003 12:16
An: [EMAIL PROTECTED]
Betreff: How to run 2 tomcat-coocon
hi richard,
well, you probably didn't find it, because your logging configuration seems
to be different (i.e. strange to me ;-). maybe that's normal for older
cocoon versions, I only know cocoon = 2.0.3.
one issue (actually 3 ;-) I could find, which is an error in your
sitemap.xmap:
!--
for this
purpose. I think you can get hold on the original
request from the Environment.
Maybe .../components/source/URLSource.java
is a good starting point ...
hussayn
Marco Rolappe wrote:
you should probably code that as an action, that you can use in your
sitemap. please see relevant docs
hi richard,
I'm currently using Cocoon 2.0.4, Tomcat 4.1.18, Apache 1.3.26 and mod_jk2
(which I didn't have problems with yet).
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im Auftrag
von Richard Cunliffe
Gesendet: Mittwoch, 29. Januar 2003 15:08
An: [EMAIL
I think you're mixing up the concepts of files and resources.
persistent URLs should AFAIR bind to resources, which in turn may represent
a file (and may redirect to a URL for that file, or something like that).
example (contrived):
http://cocoon.apache.org/manuals/BeginnersGuide
this, being a
hi richard,
I think this is a path issue. see below:
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von Richard Cunliffe
Gesendet: Donnerstag, 30. Januar 2003 11:34
An: [EMAIL PROTECTED]
Betreff: RE: Apache error on startup
Hussayn,
I
maybe your user agent has several languages set in Accept-Language and maybe
the input module uses these (LocalAction using first encountered).
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von Cyril Vidal
Gesendet: Freitag, 31. Januar 2003
hi heiko,
please have a look at:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16246
this explains why the session created in an XSP is not visible later in the
pipeline (being created after pipeline setup).
you could create your session within your XSP if you override the
generator's
hi richard,
from what you wrote in your mail it seems you have misplaced the
map:select. those go into the pipeline definitions.
maybe it would be best if you read some introductory material on the sitemap
or have a look at samples sitemaps.
your sitemap should look something like this:
!--
hey heiko,
see comments inline
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von Heiko Milke
Gesendet: Samstag, 1. Februar 2003 01:32
An: [EMAIL PROTECTED]
Betreff: Re: AW: Accessing session variables in the sitemap.xmap
Hello Marco,
hi richard,
first point: don't be afraid to look at the logs yourself ;-) most of the
time they'll reveal what's going wrong. for example in the error.log you
attached:
ERROR (2003-02-02) 22:45.52:747 [core] (Unknown-URI)
Unknown-thread/Cocoon: Could not configure Cocoon environment
richard,
once again my advice: take a look at the logs (here access.log):
DEBUG (2003-02-03) 13:18.51:614 [access]
(/cocoon/soundpool/database.html)
HttpProcessor[8080][4]/AbstractEnvironment: Reset context to
file:/C:/tomcat/webapps/cocoon/
WARN(2003-02-03) 13:18.51:614 [access]
hi
nesto,
I
assume that the JSP knows how to handle the parameters.
you
don't really have to process the parameters (via actions, matchers, whatever),
since you said you are generating an html form.
so, in
the generated form there should be something like this:
...
form method="get"
hi roberto,
the reason why your elements are empty probably are the following; the
session accessed in your XSP might be different from the JSP's session.
since you redirect without url encoding the redirect url, the session
probably doesn't survive the redirect. now in the XSP you didn't specify
hi roberto, please see bottom of mail.
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von Roberto Cipollini
Gesendet: Freitag, 7. Februar 2003 10:16
An: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Betreff: Re: AW: Session problems
Unfortunatly the
for subsequent requests...
After having saying this, i bet you cross webapp boundaries ...
regards, hussayn
Marco Rolappe wrote:
hi roberto,
snip/
-
Please check that your question has not already been answered in the
FAQ
hi derek,
could you tell me please how the XSP is accessed? the problem might be that
your XSP is dealing with a different session (XSPs default to creating a new
session).
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von Derek Hohls
hi hussayn,
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von SAXESS - Hussayn Dabbous
Gesendet: Montag, 10. Februar 2003 15:20
An: [EMAIL PROTECTED]
Betreff: global sitemap parameters and programatic cocoon
configuration
Hy, all
I just
why don't you have a look at your tomcat logs?
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von [EMAIL PROTECTED]
Gesendet: Montag, 10. Februar 2003 15:52
An: [EMAIL PROTECTED]
Betreff: Tomcat error!
Hi,
I had some troubles with cocoon
hi hussayn,
I see the classes available and modules declared in cocoon.xconf in 2.0.4,
so; 1. they seem to be released stuff and 2. you should be able to use them
in 2.0.4.
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von SAXESS - Hussayn
hi
collin,
with
XSPs an easier alternative would be to pass your 'parameter' as a request
parameter.
then
you would:
map:match pattern="edit.xml"
map:generate type="serverpages"
src=""/
map:serialize type="xml"/
/map:match
map:match pattern="edit/*"
map:generate
src=""/
...
CummingsSubject: Re: Pass custom parameters into an
XSP
Wow. I did not know you could use the XSP to
override the setup method. That is VERY helpful. Thanks!!
- Original Message -
From:
Marco Rolappe
To: [EMAIL PROTECTED
hi andi,
you didn't tell what the source for the dynamically created wbmp image is.
if it's based on xml input, you could write a corresponding Serializer (have
a look at the respective sources).
another option is to write a Reader (which doesn't actually need to read
something ;-).
third
hi laurent,
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von Laurent Comte
Gesendet: Freitag, 14. Februar 2003 19:48
An: [EMAIL PROTECTED]
Betreff: Using a RequestAttributeSelector
snip/
BUT, it seems that the request read by the
I don't know what the 'ixiarequest' maps to in your pipeline, but maybe
there's a problem with that component (generator, I uess?). otherwise I
can't directly see the sense of needing cocoon to reload.
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
hi
nesto,
that
IllegalStateException is a current cocoon bug (should by now be resolved in
cocoon-2.0.5-dev and 2.1). cocoon is trying to notify an error, i.e. the one you
are searching for. please have a look at your logs to see what the actual error
is. if the cocoon logs don't reveal
then you should definitely have a look at the source code ;-)
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von Lionel Crine
Gesendet: Montag, 17. Februar 2003 17:54
An: [EMAIL PROTECTED]
Betreff: What does cocoon-reload initialized
I'd
hi nesto,
I don't know the xbean logicsheet at all (doesn't seem to be in cocoon =
2.0.4), but anyway;
in the simplest case, the jsp:useBean boils down to a variable declaration
(scope = page):
jsp:useBean id=myBean scope=page class=mypackage.MyClass/
would have an equivalent of something like
the limitation of one generator per pipeline is no real problem here;
instead of going 'the linear way', just go 'the indirect way': you can have
the map:generate reference a pipeline as source. so, in one pipeline you
generate the xsp, in the other you have that xsp generate output.
your
I'd rather tell you to RTFL ;-) the L is log.
there you discover ClassNotFoundExceptions for classes 'For' and 'IBM'.
looking at the virgin cocoon web.xml we find following:
snippet
!--
This parameter is used to list classes that should be loaded
at initialization time of the
from within an XSP you can have a session be created by specifying the
xsp:page's attribute @create-session=true (this is handled by the
session logicsheet. this way a session will be created if it didn't yet
exist.
problems can occur with these sessions, though; sessions created by the
session
although it's a bit clumsy, you *can* use request parameters with an
internal pipeline;
map:match pattern=test/ParamToAgg.xml
map:generate
src=cocoon:/test/getParam.xml?paramTest=a+param+value+9876/
map:serialize type=xml/
/map:match
map:match pattern=test/getParam.xml
map:generate
hi amelie (nice name ;-),
instead of passing the 'name' parameter as an attribute of mytag:user you
could use an element with the same name. the logicsheet-util logicsheet that
comes with cocoon has templates that you can call to get a parameter. it
checks for an attribute and an element with the
hi again, see inline...
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Auftrag von Amelie Cordier
Gesendet: Sonntag, 2. März 2003 17:07
An: [EMAIL PROTECTED]
Betreff: Re: AW: Generating dynamic attributes in xsp
snipped-nice-name-et-al/
I can't
hi jakob,
having a quick look I assume you could use RequestContextPathModule or
RequestURIModule. please see your cocoon.xconf whether those modules are
declared. you may have to add declarations yourself.
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
hi again too :)
:-D
I agree with you but each time I add year or year or @year or @year
or year, cocoon crashes with this error :
// start error (lines 95-95) expected
import
// end error
where does this one show up? on the page or in the logs? a bit more context
around that
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Auftrag von Amelie Cordier
Gesendet: Sonntag, 2. März 2003 22:12
An: [EMAIL PROTECTED]
Betreff: Re: AW: Generating dynamic attributes in xsp
Ok.
I'm using a cvs version of cocoon that I build about one
hi derek,
AFAIR the nodebuilder for map:act type nodes (and probably others) doesn't
resolve those variable references for @type attributes. thus I think it's
not possible.
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Auftrag
von Derek Hohls
Gesendet:
you could post relevant snippets from your page, logicsheet. and please
check the logs, too. maybe there's an error somewhere else occurring.
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Auftrag von Amelie Cordier
Gesendet: Mittwoch, 5. März 2003 01:14
the xsp:attribute on the xsp-request:get-parameter is not possible; it's
translated to java code and first executed when generation starts, i.e. when
the xsp-request:get-parameter has already been translated.
but you should be able to use following:
WHICH
error do you get?
-Ursprüngliche Nachricht-Von:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]Im
Auftrag von NestoGesendet: Freitag, 7. März 2003
17:12An: [EMAIL PROTECTED]Betreff: xhtml
serializers
Hi!
How can I define a set of serializers in the
just a sidenote; for testing/prototyping purposes you don't need to declare
your logicsheets in cocoon.xconf. there's an XSP element you can use to
declare a logicsheet within your xsp. example;
xsp:page ...
xsp:logicsheet location=context://logicsheets/my-cool-logicsheets.xsl/
...
!-- other
hi
nesto,
you
can use omit-xml-declarationyes/omit-xml-declaration in your
serializer config.
but
IIUC the xml declaration should be in the markup, since it's xhtml. maybe you
have to use a mime-type different from text/html?
-Ursprüngliche Nachricht-Von:
[EMAIL PROTECTED]
Title: Problem writing a BetwixtTransformer
hi
keith,
I
didn't analyze the code and can't tell you directly where the bug is
but...
I also
got a similar exception which seemed to be an XSLT/xalan exception but actually
was an exception thrown from within a custom transformer. somehow the
Title: Problem writing a BetwixtTransformer
hi
keith,
which
exceptions did you catch? AFAIK NullPointerException and RuntimeException are
unchecked exceptions, so they most probably inhreit from Throwable not from
Exception. please make sure that you are catching those Throwables (for
hi
richard,
well,
what can I say... the xsl not only looks complicated, it looks like a mess
;-) you should really, really (really ;-) read up on the technologies
you're trying to use.
1.
what do you need the DTD for?
2. why
are you trying to handle elements which are supposed to be
as you were probably already told: actions are executed at pipeline assembly
time, i.e. before the pipeline processing (including your transformer)
starts.
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Auftrag von Lionel Crine
Gesendet: Donnerstag, 13.
hi christopher,
I remember other people trying to do this, but unfortunately the 'type'
parameter is not dynamically resolved. this restriction doesn't only apply
to map:act. other examples are map:serialize's type, which could also
be useful.
so in short; it's not possible your way.
but I
hi richard,
I had a quick look at the xsl and it seems to me you should be learning some
XSL ;-) maybe go to http://www.w3schools.com and check out their XSL
tutorial. they even use some kind of cd database in that tutorial. may be
the right thing for you.
to the xsl: the title element was
hi kevin,
in case you copypasted it may just be a typo:
map:selector logger=sitemap.selector.host name=host
src=org.apache.cocoon.selection.HostSelector/
^^^
element closed
I wonder if you're
hi geoff,
I actually encountered the problem you mentioned and back then I just added
a '*' to match the port string.
from a quick look at the sources it seems to me that in the case of the
selector things are different; it seems to be checking for a substring
match.
-Ursprungliche
hi stephan,
you might also want to take a look at tomcat's logs, if nothing appears in
cocoon's logs. the 'empty' page is most probably because of 'buggy'
error-handling (which I think is fixed by now).
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
hi richard (again ;-),
you may have a stylesheet for it, but from the sitemap.xmap attached I don't
see it applied to your xml.
another thing; you're not getting any images displayed, are you? just asking
because I see your matches on *.gif and *.jpg not being defined within
pipelines. the paths
as was already mentioned WML is an XML application, thus you 'generate' it
via the normal 'file' generator. afterwards, conversion to e.g. xhtml should
be possible.
for the .wbmps you could write a simple converting Reader, for example. JAI
has support for .wbmps, so you could read them in and
that's a servlet container issue, not a cocoon one. just don't use sessions
in your app (I assume you don't need to) and the JSESSIONID should be gone.
-Ursprungliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Auftrag von Stavros Kounis
Gesendet: Freitag, 14. Marz
hi group,
I don't really know if this is a problem or just seems like one. apart from
experiencing quite high cpu usage I encountered log entries assoctiated to
threads with very high thread numbers;
...
INFO(2003-03-16) 10:37.51:408 [access]
(/imode_de/galleries/nav(1,2).html)
hi amelie,
you may look at tomcat's log files ($TOMCAT_HOME/logs).
but first make sure please that logging is enabled for the components you're
using. i.e. for database actions, sql transformer, etc.
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Auftrag
Title: Message
AFAIK
the cocoon source comes with its own ANT including custom tasks. that ANT is
then used from the build script. you might be able to do the taskdef for
the eclipse integrated ANT. but maybe that's already handled by a target that
should exist in the build.xml;
hi stavros,
the empty page may stem from 'suboptimal' error handling which is fixed in
CVS AFAIK. please take a look at your tomcat logs. any exceptions (in this
case probably at least an IllegalStateException) should show up there.
maybe the OutOfMemoryError you got is actually the problem.
hi amelie (always reminds me of that wonderful movie ;-),
since I've not yet looked into/used the authentication framework, my first
thought would be another authorization action.
you supply the action with the respective parameters or let the action grab
it from the session, etc. from within
hi magne,
several possibilites:
- have a look at the util.xsl logicsheet. it define several tags for
including stuff (e.g. util:include-source, util:include-uri, ...)
- CIncludeTransformer
- XIncludeTransformer
for the latter two you should be able to find docs. regarding the logicsheet
I
hi phil,
please try com.mysql.jdbc.Driver as the driver class. that should work. your
dburl seems to be correct.
otherwise have a look into your mysql-connector jar. there should be a
README inside.
HTH
-Ursprngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
first, HTH = Hope That Helps ;-), my first name is marco,
my mysql driver jar's name is 'mysql-connector-java-2.0.14-bin.jar' (which
is in WEB-INF/lib).
within the jar I have a file README. a snip from the section 'USAGE AND
INSTALLATION':
...
If you are going to use the driver with the JDBC
hi bert,
the 119MB is the amount of memory used by the java process (i.e. heap and
other resources).
the -Xmx parameter specifies the maximum size of the heap, i.e. not the
maximum size of memory used by the process.
the other numbers tell you that the heap's current size is 64MB of which
19MB
hi hill,
geoff refers to the flow layer (the layer supposed to control the web app
flow). check out the cocoon wiki (http://wiki.cocoondev.org/) and search for
'flow'.
the language for the flow layer is basically pluggable (though it has to
support continuations), it defaults to javascript.
hej morten,
I don't see a reason why you shouldn't be able to dynamically generate your
xmlforms. write corresponding pipelines for the xmlform descriptions, apply
the xmlform transformations and you should be set.
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL
-
From: Marco Rolappe [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, June 10, 2003 2:13 AM
Subject: AW: Dynamically build xmlforms
hej morten,
I don't see a reason why you shouldn't be able to dynamically generate
your
xmlforms. write corresponding pipelines for the xmlform
ho,
if you haven't setup a serializer for wml (specifying the doctype, etc.),
then you should do so.
that would look something like:
...
map:serializer logger=sitemap.serializer.wml
mime-type=text/vnd.wap.wml name=wml
src=org.apache.cocoon.serialization.XMLSerializer
84 matches
Mail list logo