had that problem
it's a mapping problem... (oracle-schema)
Strings get Mapped to varchars(size)...
They get chopped at size chars...
the only solution is to declare the field as java.lang.Object
then use it as string
public Object name;
public void setName(String name)
{
I
thinnk you will find that the build.xml format has changed from 1.1 to 1.2 I
seem to remember having to change the copy src/desc/
instructions.
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of trang
leSent: 11 January 2001 05:39To:
we have content in the DB and we want to do something like this:
hello %= username %, this is your content page.
That's when we're going to hit a snag. You see there IS a need for
dynamic
content. Perhaps this is too off topic for this list, and if it is, could
anyone recommend a good
AFAIK some stuff got deprecated (e.g. copydir, deltree). 1.1 files should
run, however. Just did a migration for my own project
- Original Message -
From: "Ronald Hatcher" [EMAIL PROTECTED]
To: "Orion-Interest" [EMAIL PROTECTED]
Sent: Thursday, January 11, 2001 8:57 AM
Subject: RE:
as I criptically point in my post, you can change the database-schema for
it; StringBuffer is another workaround,
specially 'cause it implements Serializable.
however for many reasons I prefer to have Strings map to varchars (which,
let's remeber that, should grow as needed)
because it's
I
wasn't personally aware that Orion used a mailing list as their support
mechanism. It's not this one in any case.
We had
one issue surrounding SSL certs, and got through by phone easily enough (we're
license holders). The Orion team couldn't help much, but as it turned out it was
our
Hello Juan,
Thursday, January 11, 2001, 3:53:41 AM, you wrote:
JLC had that problem
JLC it's a mapping problem... (oracle-schema)
JLC Strings get Mapped to varchars(size)...
JLC They get chopped at size chars...
JLC the only solution is to declare the field as java.lang.Object
JLC then
Hi,
Probably been asked before but I can't find it in archives.
I have a legacy database with over 80 tables, most of them represent many to
many relationships (M:N) just with 2 or 3 foreign keys. I'm building a EJB
layer on top and the initial load is proving to be a bit slow.
An example of
