I don't know what I've done wrong, but everything is not working as it
should!
After I spend ours with deployment stuff (Jetty and PostgreSQL), I
finally noticed that the SessionVar ist not working in Jetty.
I've shopping cart, without Jetty - NO PROBLEM - with Jetty - the
content is not cleared and can be seen in all browsers accessing the site!
This is definitely not good!
thanks.
--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
Here's how I deploy my Lift apps.ᅵ I create the WAR file (this depends on your build tool).ᅵ mvn package or sbt package will do just fine.
Next, I download Jetty: https://github.com/dpp/lift-samples/raw/master/jetty_instance.tgz
I un-tar Jetty and copy my WAR file to webapps/root.war inside the Jetty directory structure.
To start my app, I type "start_prod.sh" from the top level of the Jetty container.
There are files that contain the heap setting and the port setting in the top level.
You can change the database connection settings in the props file at build time.ᅵ the default.props file is used for development and the production.default.props file is used in production mode.
We are here to help you be successful with your Lift application.ᅵ But we are not here to be your system administrators.ᅵ Please read some of the thousands of articles on deploying a WAR file in an J/EE web container and setting up JDBC connections before posting more questions on this issue.
Hi David,
It wasn't my purpose to SPAM the list with stupid questions.
But I think you have to understand, that somethings are not well documented for the beginner, like I am.
Besides that, I await that 'code' is working the same way on my production system as well as it does on my development machine.
That's why I wrote this message. I got beyond my deployment problem and it worked - and than I figured out, that the same application is behaving differently than without deployment (Jetty), which is a little bit strange to me.
What shall I do - test for each machine and each setup? I'm only speaking about code not about configuration, and I expect that code always works the same way, right? I think that's what everybody's expecting...
Finally, I figured out, that I'm having this issue on my development machine, too. And without being offensive I did what you told me and I made an update from 2.1-M1 to 2.1.
I think that's where the problem comes from, because I didn't do other changes.
thanks.
Here's how I deploy my Lift apps. I create the WAR file (this depends on your build tool). mvn package or sbt package will do just fine.
Next, I download Jetty: https://github.com/dpp/lift-samples/raw/master/jetty_instance.tgz
I un-tar Jetty and copy my WAR file to webapps/root.war inside the Jetty directory structure.
To start my app, I type "start_prod.sh" from the top level of the Jetty container.
There are files that contain the heap setting and the port setting in the top level.
You can change the database connection settings in the props file at build time. the default.props file is used for development and the production.default.props file is used in production mode.
We are here to help you be successful with your Lift application. But we are not here to be your system administrators. Please read some of the thousands of articles on deploying a WAR file in an J/EE web container and setting up JDBC connections before posting more questions on this issue.