Hi Hugh,
This was already fixed a few days ago, by myself in the CVS, as well as
updates to the SchemaWriter.
Thanks anyway.
--Keith
Hugh Winkler wrote:
>
> This patch fixes bug: Castor 0.9.4.2 builder generates erroneous xmlName
> for
> top level attributes referenced by an element. I just
Dennis,
thanks for the tip, looking at my test case code, I only called Unmarshaller.setValidation(false);
This did not improve the performance of the unmarshaller. Only my changes
did by swapping in a new XMLParser and some other minor changes. Low and
behold as I look them up I can't
i'm trying to run my junit tests with log4j level to set DEBUG and
castor.properties (specifying org.exolab.castor.debug=true) in my
classpath, but it's not working. also tried changing the
org.exolab.castor.debug setting in the castor.properties inside of
castor-0.9.4.2.jar, but to no avail.
Dean Hiller wrote:
here is one of the messages. I do now have VP approval to give code.
I just need to dig it up sometime. I have not gotten around to
narrowing what caused the hit down. I just have a fix. When I work
on it again, I will send you the code. I don't have the time to dig
i
here is one of the messages. I do now have VP approval to give code. I
just need to dig it up sometime. I have not gotten around to narrowing what
caused the hit down. I just have a fix. When I work on it again, I will
send you the code. I don't have the time to dig it up right now and I
Hi Dean,
I tried a couple of archive searches to see your code, but didn't find
anything - if you have a link to the particular email with the code I'd
be interested to see what you'd done. I did turn off validation for the
performance tests I described in the article, and used a parser that's
Gentlemen,
I have tried these fixes to no avial. I have tried the key generator
with both the trigger and returning params set and unset. Both ways
produce keys
for me but ultimately, my stacktrace ends up the same. Here it is. I
included
the entire output for reference.
C:\SchedulingFramew
Dennis,
I actually ran perfAnal on castor and improved their performance by
5 times for small documents if I remember correctly. That was sufficient
for our server environment. My change was never submitted as it was a hack.
All I did was put in the 1.4 parser with "no configuration."
Bruce Snyder wrote:
Reposting because Andre didn't see this.
Andre, Gustavo,
Because the data returned by these queries really don't need to be mapped
in Castor, I would suggest grabbing the underlying java.sql.Connection
and executing a straight SQL query on it. Here's an example of grabbing
This patch fixes bug: Castor 0.9.4.2 builder generates erroneous xmlName
for
top level attributes referenced by an element. I just lifted this code
from similar code in ElementDecl.java.
Please see attached testcase.
Hugh Winkler
BetweenMarkets Inc.
---
castor-0.9.4.2/src/main/org/exolab/ca
10 matches
Mail list logo
