Re: Deploying Source Code

2007-10-26 Thread agodinhost
I don´t know if I really understood what you mean. If you are just talking about the iBates part of code, to give a more examples, it is okay. But if you are talking about the whole application this can be a nightmare!!! Please, explain better your idea. Woody - Original Message -

RE: Deploying Source Code

2007-10-26 Thread Clinton Begin
I mean deploying your .java files to production alongside your .class files and having it available on the classpath at runtime. com/yourdomain/yourapp/SomeClass.java com/yourdomain/yourapp/SomeClass.class I hope that’s more clear. Clinton From: agodinhost [mailto:[EMAIL

Re: Deploying Source Code

2007-10-26 Thread Larry Meadors
I used to do that, but looking at it now, I am asking What's the cost and what's the value?. The cost in terms of disk is negligible these days - You can't buy a drive 120GB these days, so what's a few hundred KB, or even a few MB on disk? Especially compared to the 80MB of struts or spring? I'm

RE: Deploying Source Code

2007-10-26 Thread Clinton Begin
You've caught me...and you're the perfect person to have done so. I am indeed thinking of enhanced runtime reflection. See if Java reflection was complete, this wouldn't even be a discussion. Certainly in C# land it is not. There's two reasons: 1) parameter names as you've guessed, 2)

Re: Deploying Source Code

2007-10-26 Thread Brandon Goodin
I think there would be a couple issues... The first is overcoming the stigma of deploying src alongside your compiled code. The knee jerk reaction is going to be about security. However, what is humorous about that is that companies regularly expose their database structures via SQL in xml files

Re: Deploying Source Code

2007-10-26 Thread Jeff Butler
Agree - no security risk, no real downside except cultural. BTW - we used to do this as an elementary form of source control. Crude but effective. I'm interested - if you're looking to improve reflection, have you found a good parser? The Eclipse parser is excellent, but hard to break out as a

RE: Deploying Source Code

2007-10-26 Thread Clinton Begin
Definitely not a security risk...decompilers, decompilers, decompilers... :-) But, now it’s time to play the card I’ve been holding back. Every day, thousands of developers (of well over 50% of web apps) deploy their source code to their web/app servers in the form of PHP, Perl, Python and

RE: Deploying Source Code

2007-10-26 Thread Clinton Begin
I don’t think we need a parser. I could pull that out with regex. No need to go further than we have to with it. This is all very high level anyway...I wouldn’t plan on adding this as a release feature or anything. It’s just a thought. Cheers, Clinton From: Jeff Butler