Using 3.1.2 (yes, it's older, too many dependencies to upgrade).
our Spring context is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<beans...
Type: Posts; User: jwenting; Keyword(s):
Using 3.1.2 (yes, it's older, too many dependencies to upgrade).
our Spring context is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<beans...
doesn't matter what trickery you try. As long as someone can get at the server they can get the credentials one way or another.
Either you have to have the decryption key in plaintext somewhere, or...
override showForm and onFormSubmission instead of handleRequest and onSubmit.
something like this?
@Override
protected ModelAndView handleRequestInternal(HttpServletRequest request, HttpServletResponse response) throws Exception {
ModelAndView mav = new...
use POST form submission instead of GET, and use forwarding filters for the results.
yes, secure access to the server so not everyone can get at the file.
You should do that anyway.
Not that we're seeing any error messages whatsoever, just some informational stuff during the loading of the beans into the applicationContext.
So it never even gets to the part where you're...
ORM is not applicable when you have rules that don't map to the ORM logic.
Maybe your delete needs to do things that aren't mapped using the ORM framework and can't be put into a trigger for...
What's your configuration like? Do you maybe have a typo somewhere, causing the transactionmanager to not notice the existence of the entitymanager defined in your configuration?
You need...
I doubt he'll ever read your question, or respond even if he does.
It looks like a problem with the IBM JRE. You could try recompiling your classes using an IBM JDK, maybe even compile Spring from...
That indeed did the trick. Got the whole thing working.
Got to optimise the JPA code a bit still, seems to be a bit inefficient (generating too many queries that can be efficiently combined into...
Cheers. Will give that a try.
Looked through several books and all the examples use only primitives as fields of course.
While they mention property editors those are almost universally limited...
You can't, not the way you think you want to at least.
There is no difference in the incoming request depending on whether the request was generated using a link on your website or some other...
When using the form:select tag, the selected value(s) don't get set to the command bean.
I guess I'm doing something wrong, but what?
The main bean:
public class Book extends PublishedItem...
name it <ServletName>-context.xml where <ServletName> is the name of the Spring controller servlet.
Place it on the classpath (so in your WEB-INF/classes directory).
I don't think there's a built-in mechanism, but nothing prevents you from creating such a generator.
the iterate element indeed doesn't generate an "IN" element in the SQL, but something like "emp_id='123' or emp_id='425' or emp_id='633'".
This could conceivably have the same effect (depending on...
I'm not entirely sure, but it may well be that the loading takes place when the containing object instance is created, at which point the contained data isn't yet available.
To make sure, just load...
It would certainly be cleaner to get a new JdbcTemplate for the new query.
While what you look to do may work (somewhat doubtful, without looking at the framework code I can't know for sure but I...
In your case the client of the webservice is the real client.
How can you guarantee that that client properly terminates the session so you can close your resources?
Same principle applies as...
and don't use JRockit. It has problems of its own, which may affect interoperabillity with Sun VMs (and others).
in web applications you want to have a database session last at most the length of a single request.
Anything longer is a recipe for disaster (specifically connection starvation).
The antipattern...
that would be a problem with your hibernate configuration (or with your database configuration).
Without more information noone will be able to help you further than that.
usually such errors (if there are no log entries) result from typos in the web.xml (some errors there will cause log entries, some won't under all conditions).
That's not a problem with Spring but with your JSP engine, and specifically the JSP compiler/parser.
The code generation step where it generates Java source code from your JSP doesn't recognise your...