The Jetty web application server is great. It is just not very well document and when it is documented it is aimed for the very uninitiated. If you’re using Jetty, it is almost like an old boys club – ‘you made it’.
Still, it appears that Jetty and Tomcat are becoming much more similar in their way of doing things, with both using a somewhat proprietary, if you can say that on an open source project, configuration schemes. So how do you deploy a web application to Jetty?
For my thesis, I am going to use the Jetty lightweight web server and as such am going to need a lot of trying and learning around how to use it, as it is more ’embedded’, for lack of a better word, than Tomcat. For me, Tomcat is a relatively known entity, having worked with in one form or another since 2000.
I am using Jetty 6.1.7,
So here goes…
<Set name="port"><SystemProperty name="jetty.port" default="8999"/></Set> |
Change the value of the default attribute to the port you want to use.
Class diagrams are great. RAD 7 has them and it generates and updates code based on them. Lovely.
The forward and reverse engineering capabilities, the works.
Now if you refactor the classes and change package names… then you’re in trouble. The class diagram is like, oblivious to the change and being unable to find the classes the diagram is based on it just chokes. So just be aware of this possible problem.
How to fix this:
Now open the diagram again using the DNX file viewer and voila – your diagram is back!
