Frank,

To get MMBase working, your first step SHOULD be to step up a working
server environment. You won't be able to do anything with MMBase without
a properly installed servlet container. I suggest you setup MMBase with
Tomcat 4.x as this gives best results with the JSP based editors (the
relation editor generates JASPER compile errors under Tomcat 3.x) of
MMBase.

Besides that, my "tip of the day" would be to setup MMBase with Tomcat
first *outside* WSAD. Once you got that running you can transfer your
webapp context from your Tomcat directory to your WSAD workspace
directory. From there you should be able to configure your Tomcat test
instance within WSAD.

As an alternative you should consider to setup MMBase with Eclipse and
the Tomcat plugin from SYSDEO (in stead of WSAD). This is probably a
much easier way to setup MMBase in a development environment. I know
WSAD is based on Eclipse release 1.0 which contains some pretty nasty
bugs running Tomcat and probably will give you some long and lonely
nights with your debugger. These bugs are fixed in Eclipse 2.0.

Running MMBase against DB2 requires a DB2 driver for MMBase, as MMBase
doesn't (yet) support DB2 out of the distro. We have written such a
driver and are currently test-driving it. We expect to release it to the
MMBase community shortly.

The problem you mention with HTML files doesn't ring a bell. We had none
of those problems. Did you try a distro of MMBase or did you use a CVS
snapshot?

Good luck,

Rogier

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
> On Behalf Of [EMAIL PROTECTED]
> Sent: Wednesday, June 26, 2002 10:17
> To: [EMAIL PROTECTED]
> Subject: RE: tag and charset errors in mmbase html source 
> files imported into WSAD
> 
> 
> 
> Hello Henk,
> we would like to try and run mmbase in a wsad test 
> environment. wsad has the following servers available: ws 
> advanced edition test environment v.4, apache tomcat v.3.2 
> and v.4, but we did not fully set up a server yet. We have 
> just started to use mmbase AND WSAD; and we are for practical 
> reasons interested to get mmbase running in this new enviromnent.
> 
> I was referring to errors that occur when the mmbase files 
> downloaded from the mmbase.org site have been imported into 
> wsad. We have not created (yet) our own files....Several 
> downloaded files contain the charset (the meta tag of some 
> files says "word97") causing funny  chars and the tag errors, 
> I believe.
> 
> We would like to use db2 database (not set up yet for 
> mmbase), because we already run it on our machines.
> 
> Here are some (wsad) errors (there are hundreds of these 
> types): often in a html file lines begin with a </..> tag, 
> which wsad (and DreamweaverUltradev too, by the way, I tested 
> some files) does not like. Or tags are nested in a nonregular 
> way such that WSAD (and DW) does not understand it 
> completely. I have noticed that DW tries to fix this type of 
> code by adding extra tags by or reoganising the code.
> 
> no start tag <form>
> no start tag <body>
> no start tag <html>
> no start tag <tr>
> invalid character used in text string
> 
> One file that contains many of these errors is scan1_0.html 
> (225 errors)
> 
> I hope this is useful information.
> Thank you very much for your comments.
> 
> Kind regards,
> Frank
> **************************************************************
> **************
> 
> The information contained in this message and any attachments:
> 
> 1. does not constitute an offer or an acceptance of an offer or
>    a representation or warranty, nor shall it form any part 
> of a legally
>    binding contract.
> 
> 2. has been compiled with care but no representation or warranty
>    (express or implied) is made as to its accuracy or 
> completeness and no
>    liability can be accepted for any loss arising from the 
> use of any of
>    the information.
> 
> 3. may include opinions or views, which unless expressly stated
>    otherwise, are not those of the company or any person in 
> relation to
>    whom the company would have vicarious liability or responsibility.
> 
> 4. is not guaranteed to be free from any so-called computer viruses
>    and it is strongly recommended that you check for such 
> viruses before
>    down-loading it to your computer equipment.
> 
> 5. may include hypertext links to the sites of other companies or
>    persons, the content of which this company has no control over and
>    accepts no liability for.
> 
> 6. is for the exclusive use of the addressee and may contain 
> confidential,
>    privileged, work product immunity and/or non-disclosable 
> information.
>    If you are not the intended recipient and receive this 
> message and any
>    attachments, you must not read, copy, transmit, disclose 
> or otherwise use
>    any of them (or part of them) in any way (to do so may be 
> unlawful) and
>    we would be grateful if you could inform us immediately of any such
>    receipt and subsequently entirely and permanently erase 
> the message and
>    any attachments from your equipment.
> 
> E-mail is an informal method of communication and is subject 
> to possible data corruption. For these reasons it will 
> normally be inappropriate to rely upon information contained 
> in an e-mail without obtaining tangible written confirmation of it.
> 
> **************************************************************
> **************
> 
> 
> 
> 
> 


Reply via email to