Community Issues, Eclipse Import, etc.

[Daniel Kastenholz <da...@in.tum.de>]

Guys,

after having received no answer from anyone to my question about type 
checking and type restrictions at runtime, I addressed myself directly 
to Jochen Wiedmann and learned then that this part of the JAXB 
specification is apparently not implemented in JaxMe yet. (Neither is it 
in the JAXB reference implementation, but _they_ mention it in their docs!)

Jochen suggested to me to implement this feature myself. Fine, be my 
guest, why not. So I have downloaded the sources and now tried to turn 
the JaxMe source tree into a working Eclise project for almost two 
hours. No offense against those who still prefer hacking their source 
into VI, but since Eclipse is more or less the de facto standard for 
Java development, isn't that a little high for an entrance barrier?

With all due respect to your work & efforts, the impression of the 
community awareness in this project is just emberrassing!

So please: what do I have to do to get this project running in Eclipse? 
I have imported all included JARs (which might actually have resolved 
all JAR dependencies -- unsure!), but first of all I get these annoying 
error messages from all the subprojects inside the "src" folder whose 
package names are wrong. (Adjusting the build path seems NOT to work.)

Cheers


Daniel

---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org

Type validation at runtime (was: Re: Community Issues, Eclipse Import, etc.)

[Daniel Kastenholz <da...@in.tum.de>]

Hi everyone,

@Robert: thanks a lot for your friendly and immediate response, I had 
almost given up hope!

It took a couple of hours for my message to be sent over the mailing 
list, and in the meantime I have found a solution for the original 
problem (JAXB fail-fast / runtime type validation).

(I am now injecting custom handler code using Ant's regular expression 
matching task right after the XJC tasks. Certainly this is neither a 
generic approach nor beautiful, actually somewhat risky in case the XJC 
output pattern changes, but for now, it does the job.

Nevertheless, I thought somebody else might also find this idea helpful 
-- so here it is, for your archives.. ;-) )

Thanks again.


Daniel


---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org

RE: Community Issues, Eclipse Import, etc.

[Robert Eric Reeves <ro...@phurnace.com>]

Daniel,

Thank you for offering to add support for type checking and type
restrictions at runtime.

I'm not sure if I checked out from the correct branch. I chose the trunk
here: http://svn.apache.org/repos/asf/webservices/jaxme/trunk. But, it looks
like Jochen is working on the v0.5 and MAVEN branches most recently. The
.project and .classpath files exist in all of these locations.

I picked the trunk and checked it out using Subclipse. After the first
Eclipse build pass, I got some missing resource errors. So, I just ran the
default target in the build.xml.

Then, I notice a lot of errors in the IDE. Since the build worked just fine
from the ant command, I started looking into the build files.

I noticed that there are a lot of "excludes" in the javac tasks in pm.xml an
jm.xml in the ant folder. So, I just added them to the .classpath file. The
svn diff is attached.

Good luck!

Robert




-----Original Message-----
From: Daniel Kastenholz [mailto:daniel.kastenholz@in.tum.de] 
Sent: Wednesday, June 21, 2006 3:48 PM
To: JaxMeJS development
Subject: Community Issues, Eclipse Import, etc.

Guys,

after having received no answer from anyone to my question about type 
checking and type restrictions at runtime, I addressed myself directly 
to Jochen Wiedmann and learned then that this part of the JAXB 
specification is apparently not implemented in JaxMe yet. (Neither is it 
in the JAXB reference implementation, but _they_ mention it in their docs!)

Jochen suggested to me to implement this feature myself. Fine, be my 
guest, why not. So I have downloaded the sources and now tried to turn 
the JaxMe source tree into a working Eclise project for almost two 
hours. No offense against those who still prefer hacking their source 
into VI, but since Eclipse is more or less the de facto standard for 
Java development, isn't that a little high for an entrance barrier?

With all due respect to your work & efforts, the impression of the 
community awareness in this project is just emberrassing!

So please: what do I have to do to get this project running in Eclipse? 
I have imported all included JARs (which might actually have resolved 
all JAR dependencies -- unsure!), but first of all I get these annoying 
error messages from all the subprojects inside the "src" folder whose 
package names are wrong. (Adjusting the build path seems NOT to work.)

Cheers


Daniel

---------------------------------------------------------------------
To unsubscribe, e-mail: jaxme-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: jaxme-dev-help@ws.apache.org