date:20040220

Re: XSP Validation XSP-formval

2004-02-20 Thread John L. Webber

Anna,

You're better off using a DateFormat object to parse the request 
parameter instead of the deprecated new Date(String). Then you can catch 
a ParseException and take action based on this. You can instantiate a 
SimpleDateFormat object using a pattern matching the input you expect.

If the XSP is an action, you can use xsp-action:set-success and 
xsp-action:set-failure to communicate the result to the sitemap.

John

Anna Bikkina wrote:

Hi,

I have another question using XSP form validation. I used XSP-formval using 
the descriptor file and it worked.
Now there are some other validations that I have to do and display errors 
other than what I can do with the descriptor file. Like I have to check the 
startdate and enddate entered by user and display error if startdate is after 
the enddate and things like that.  I created a xsp logic tag and did the 
necessary validations but I am getting error while running the xsp file

error is :
org.apache.cocoon.ProcessingException: Failed to execute pipeline.: 
java.lang.RuntimeException: org.apache.cocoon.ProcessingException: Exception 
in ServerPagesGenerator.generate(): java.lang.IllegalArgumentException

the xsp:logic paragraph that I add looks like this 
xsp:logic
  			if(notnew) {
  System.out.println(entering into not new);
  Date sd = new Date(request.getParameter(startdate));
  Date ed = new Date(request.getParameter(enddate));
  if(sd==null)
  	sd= new Date();
  if(ed==null)
  	ed=new Date();
  if(sd.after(new Date())){
			System.out.println(Start date is greater than today);
  	font color=red
		xsp:text* Startdate invalid. Date greater than today/
xsp:text   	
			   /font
			   bad=true;
			   			} 
  else if(ed.after(new Date())){
  	font color=red
		xsp:text* Enddate invalid. Date greater than today/xsp:text   	
			   /font
			   bad=true;
			   
  }   		 
  			}
  		/xsp:logic

Is there a way I can check errors in the input other than the formvalidation 
method. I understand that I can write multiple action classes for each of the 
error I can represent but from there how can I come back to the same file 
with the error messages.
 

--
-
Jentro Technologies GmbH
John L. Webber, Software Development
-
Rosenheimer Str. 145e	81671 München
Tel. +49 89 189 169 80 mailto:[EMAIL PROTECTED] 
Fax  +49 89 189 169 99 http://www.jentro.com
-



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

how to set the jdo environment with ojb for multiple databases

2004-02-20 Thread Johnson




Hi!

The sample for woody ojb is ok now,I've a question for how to 
set the jdo environment with ojb for multiple databases.
ie. how to set the
package.jdo
repository.xml
...
in classes path

Johnson

Woody integration in Portal

2004-02-20 Thread Remmerie Bart

Title: Woody integration in Portal

Hi,
I'm struggling with the implementation of woody in a coplet.

I've managed to create simple coplets where I manage to rewrite the links
using the portal-coplet transformer a href="" = portal-event.
And, as suggested, I always use the same uri for my coplet.

Trying to integrate woody seems to be more complex.
1. Using the form2bean.flow sample: each time I click a button,
the woody form leaves the portal fills the whole screen again.
2. Next to that, Using the html-output of the woody sample for my woody-coplet,
the title on the top of the browser window is set to the title of the woody-html-page

There are a lot of usefull tips in the cocoon-mailing-lists, but they don't solve my major question
how do I keep my woody-form in my coplet ?

I've been guessing to fix the problem (no success) with following approaches:
1. Using a linktransformer: this generates ev:eventlinks/ =
very interesting, but I don't know what to do with this
2. Using ApplicationCoplet as CopletBaseData: didn't get it running
...

My questions:
1. How can I get a woody-form properly running in a coplet?
(avoid jumping out of the portal, after one click)
2. How can I avoid that the portal pagetitle is set to the woody coplet title ?
(based on the html-output of the form2bean transformation)
3. Intrigued by what I found: what's the purpose for ApplicationCoplet ?
I know it is intended to get external apps running in a portlet,
but I could use some more detail.

My sitemap:

The URICoplet points to cocoon:/test

!-- form2bean.flow generates output in html, therefore I've split it up in 2 parts, test test2
test2 results in xml-output which I can use in my test-pipeline. There is probably a better way to do this --
map:match pattern=test2
map:generate src="">
map:serialize type=xml/
/map:match

map:match pattern=test
map:generate src="">
map:transform type=xslt src="">
!-- link2coplet.xsl transforms a href="" elements into cl:link parameter=attributes/inCopletPath value=foo/ --

map:transform type=portal-coplet/--
!-- transforms the cl:link/ elements into portal-events
!-- map:transform type=portal-link/--
!-- I don't know what this one exactly does --
map:serialize/
/map:match

Long message, lots of questions, ...

Thanks,
Bart

This message and its attachments may contain confidential information protected by intellectual property rights or other rights & is strictly for the exclusive use of the intended recipient. It is strictly prohibited to copy, alter or disclose this message or its contents to any other person without Elia's prior consent. If you are not the intended recipient of this message, please inform the person who sent it and delete the message from your system. Elia is not liable for any direct or indirect damage arising from errors, inaccuracies or any loss in the message, from unauthorized use, disclosure, copying or alteration of it or as a result of any virus being passed on. This message does not constitute any commitment from Elia except when expressly otherwise agreed between the intended recipient and Elia.

49 matches

Mail list logo