--- David Sean Taylor <[EMAIL PROTECTED]> schrieb:
> Now that jogs my memory
> We have a bug here
> You are making my 'job' too easy for me :)
> Look at the portlet preferences:
>
> <preference>
> <name>JdbcConnection</name>
> <value>jdbc:derby:/tmp/productiondb</value>
> </preference>
>
> We need to changed that to point to the directory
> where you installed
> Jetspeed-2 into. Unfortunately the dialog box doesnt
> allow a string long
> enough to hold it!
>
> It should be:
>
> C:\Program Files\Apache Jetspeed
> 2.0\webapps\jetspeed\WEB-INF\productiondb
>
> Recommend reinstalling to someplace with a short
> name like
>
> c:\j2
>
> And then once you install, edit the preferences
> dialog to point to
>
> /j2/webapps/jetspeed/WEB-INF/productiondb
>
> Let me know if it works
> and sorry about the untested demo feature
>
>
I had the same error (or to be honest it was one of
the many errors I came accross) and through the many
reinstallations I too chose the j2 directory to ease
navigation which solved this problem without me
knowing what fixed it.
There are lots of portlets not being initialized
porperly with the demo portal though.
Is there a common practise in 'debugging' these errors
in J2. As a noob I'd rather be pointed to a checklist
than asking for each error.
I understand JSR168 being a powerfull standard which
not only allows standard definition of portlets but
should allow standard debugging.
So what are the common steps you (aka the pros) go
through when coming accross a "Failed to retrieve
Portlet Definition for XYZ" message?
Thanks in advance.
Stefan
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
