Wait a sec - there is a difference between creating an object and persisting an object. I think it's been illustrated here. Using the constructor to create an object is a pretty standard usage. I'll second the idea of not persisting an object in a constructor. Give the developer the control...
If you only have a date then you can't get the timezone unless there is another field with it on the database table. The only other way is to do a lookup to another database.
Or another way is to have a string datatype with the ISO version of date time. That version of date time contains...
Look at Jakarta Tag Lib stuff
http://jakarta.apache.org/taglibs/doc/string-doc/string-1.1.0/index.html
Download the Tag Lib (and associated libraries it requires) and place it in your /lib files directory for your project. Add a line in your web.xml that looks like the lines pointing to the...
Ok - this is JSP
It looks like that perl code is building a hyperlink. Java the language itself doesn't have a function that will do what you want but you can write one.
There's a number of different ways to do what you want to do..
JSP can be used a number of different ways as well...
That means that Eclipse has parsed your code and found that you are not catching an exception that the compiler will expect you to catch. This is a nice feature because it will notify you of code that will break before you try and compile it.
To fix this you can highlight the code and use the...
My answer wasn't a knock against you dmazz. Not sure how you even took it as a negative comment?
I broadened my answer from "no you can't reuse perl scripts" to one that could encourage you to "re-use your skills" in the java world. :)
I would have each User associated with a UserProfile object. The UserProfile object will contain ViewSettings.
You can then pass the ViewSettings object into the instance of the form or page on loadtime. When the page loads it will use the ViewSettings to manipulate it's display to the user...
Of course,
These default constants will be in some XML/PROPERTIES file. Load them into a global object and then get/set them as necessary. Make sure that you always go to the global object for parameters when needed instead of caching them in other objects.
I'm not super familiar with app...
Syntax is cheap - meaning that you can use your perl skills in a pure java environment. But it's not syntax that you really want to re-use, it's your capability to develop creative solutions. So..
Think of your skills as programming skills, not just perl. :)
And do it in all java :)
Makes sense.
So sounds like these variables are CONSTANTS.
What you can do is create a global properties class (could be a hash map) and call this from your code OR load these constants at run time into the app level variable. Then write a proxy class for this so that your code calls...
of course - he didn't specify what he was building and there seemed to be some lumping together of java application/applet. Just wanted to clarify for him.
Hilber - how will users use this?
just to say another thing. If you build a java application as opposed to an applet then you won't need a web server or an app server. For example - a java application would be delivered as a jar and run from a console, but an applet will be delivered over a web browser.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.