Ralf,
Thanks for your clarification on this XML issue. I totally understand
the situation. Can you take a look at the bug Castor-1267? I did exactly
what you suggested and worked out a fix. If it does not break anything,
can you commit the change?
thanks
Bill
Ralf Joachim wrote:
Hi Harish,
I'm sorry that you didn't get an response to you last mail.
Let me explain a bit about organisation of the castor project. Castor
consists of 2 parts that work together very close but require a bit
different knowledge from those working on it. Therefore we have
committers that mainly work on JDO or XML side of the project.
On the JDO side there are Werner and myself that are quite active
developing castor and offering support through mailing list. In addition
there are about 2 others that contribute from time to time.
On the XML side the situation doesn't look that good at the moment.
Keith Visco, the main developer of this part, only have very few time to
contribute. He is only able to answer some of the users questions at the
moment. Apart of Keith there are 1 or 2 others that frequently offer
support on the mailing list but there is none that actively takes care
on the developement.
Even if Werner and myself are willing to help out on XML we are not able
to also take over the XML developement. I may need to mention at this
point that castor is a open source project that depends on contribution
of vulenteers and we are also not paid for this and need to work on
Castor mainly in our free time.
As you are hit by one of the issues that Castor has on the XML side I
would suggest you to search if there is an open issue about that in jira
or create a new one if not. The next step to resolve that issue will be
to create a test case that enables others to reproduce the problem and
can later be used to verify that a featur added or a bug that has been
fixed will not be broken with futur changes. Next you need to prepare a
patch that fixes that issue and does not break other things.
If you are willing to go this way with us, Werner, Keith and myself will
help you as far as we can to resolve the issue and get it into the next
release.
Now back to where we have started. The reason why I did not respond to
your first mail is that it is related to XML which is not my main area
of work and that I did not understand what you wanted to know. Maybe I
would be able to help you if I would have had more details about your
problem. This could be a description of the problem in the mail or a
pointer to one of the issues in jira.
According to the problems you mentioned in your mail:
- why do you need to tweak a lot in code when your xsd changes?
- are you using introspection, mapping or source generator?
- what are the problems with mapping of dates?
- how does a simpel xsd look like where the naming problem happens?
- are you using a binding file (only applies to source generator)?
- are there issues in jira that describe your problems?
- what are the numbers of this issues?
Regards
Ralf
Castor JDO, committer
Vembu, Harish schrieb:
Hello All,
I did not get any reply for my posting so far. Any quick help would
be much helpful. I am planning to try out JAXB and/or JIBX as an alternative to
Castor 0.91. Please advise at the earliest.
Thanks & Regards,
Harish.V
-----Original Message-----
From: Vembu, Harish
Sent: Monday, January 09, 2006 10:13 AM
To: '[EMAIL PROTECTED]'
Subject: Castor0.91 implementation
Hello All,
I would like to get valid inputs and suggestions for the Castor
implementation in my project as given below. Are these below mentioned problems
taken care in latest version of Castor1.0 ?
Thanks in advance for your help.
Thanks & Regards,
Harish.V
________________________________________________________________________________________________
Hi Harish (asuming Harish is your first name),
would you please be so kind to post this to the dev mailing list, where
it will be dealt with in the appropriate way.
Regards
Werner
Vembu, Harish wrote:
Dear Werner,
Its always nice to know a new group who are experts in an area where you are just placed your feet.
My query is regarding a design change to be suggested for an existing solution implemented using Castor 0.91.
The existing solution in brief:
We have a J2EE portal application accessing another payment application through
JMS/MQ series. The communication with the Payment application - Request and
Response is through XML messages. Castor is used as for
marshalling/Unmarshalling of Java objects/ XML docs.
The problem:
Becasue of the frequent changes to the XSD schemas there is a necessity to tweak a lot with the Java code and also in the portal code. There is problem in mapping of Date field and for XSD schema elements having same names. Also when there are multiple elements with same name in XSD schema then there are issues with respect to marshalling and unmarshalling to and from Java objects. In short there is not 100 % mapping achieved. We need to find a design solution to avoid this shortcoming in using Castor.
This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied,
disclosed to, retained or used by, any other party. If you are not an intended
recipient then please promptly delete this e-mail and any attachment and all
copies and inform the sender. Thank you.
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
