Forum Problems Installing LAMS: Re: Re: Re: Re: Re: Problem in depoy-tools


 
Search: 

6: Re: Re: Re: Re: Re: Problem in depoy-tools
In response to 5 06/11/07 02:34 AM
[ Reply | Forward ]
Hmm, I think this is due to the deploy-tool utility not being able to access the net when running. Are you trying to do a build on a machine that can't access the internet?

Unfortunately, the XML parser we are using won't work if it can't get to a website referenced in the DOCTYPE in the XML file it is parsing.

So if the computer you are building on isn't internet, then this step will fail.

Otherwise its a good parser so we don't want to change parsers!

There is a workaround:

* Do the normal assemble-ear and deploy.ear.
* Remove the DOCTYPE line from the application.xml file in server/default/deploy/lams.ear/META-INF (I suggest cutting and pasting it elsewhere as you will to paste it back again later).
* Run the deploy-tools
* Put the DOCTYPE line back into the application.xml.
* Start JBOSS

Fiona

Posted by Fiona Malikoff

7: Re: Re: Re: Re: Re: Re: Problem in depoy-tools
In response to 6 06/11/07 03:46 AM
[ Reply | Forward ]
Hi,

Thanks a lot! I was able to do a complete build.

I do not know whether the problem which i am facing now is related to this post or not.

During Authoring of "Q & A" tool, the instruction area normally shows "fckeditor" in version 2 but in this version, instead of displaying fckeditor below the instruction area, it shows a login screen. The tool is not able to remember the login information.

I hope i am able to explain the behaviour.

I believe there is something related to fckeditor.

Can somebody help me on this.

Thanks in advance

Regards,
Bhavesh R Bhanushali

Posted by Bhavesh Bhanushali

8: Re: Re: Re: Re: Re: Re: Re: Problem in depoy-tools
In response to 7 06/11/07 05:06 PM
[ Reply | Forward ]
Don't remember seeing this one before.

The FCKEditor lives in a different web-app to q&a, so that suggests something is going wrong with the "glue" that keeps you logged into LAMS.

I'm guessing here but could you check your serverURL setting? When that is wrong, all sorts of weird things happen.

Log in as sysadmin, go to the System Admin menu and do Edit Configuration Settings. Check the ServerURL entry. If will be accessing LAMS from just the computer running LAMS (e.g. your own PC when doing development or testing), then it can be set to http://localhost:8080/lams/. If you will be accessing LAMS from another computer, then you have to change "localhost" to the name/ip of the LAMS computer.

If that doesn't do it, can you grab the logs and post them here? Don't paste them into the window, zip them and attach them to a post. The instructions for the logs are on the wiki . I'll be particularly interested in the access log.

Fiona

Posted by Fiona Malikoff

Reply to first post on this page
Back to Problems Installing LAMS
.LRN Home