I don't get it. You want to serialize an object to transport it via JMS - why another Interface/Object for that? If it's serializable, then serialize it! You just have to decide what output you want.. byte[], XML, JSON.. whatever..
philz
@philz
Best posts made by philz
Latest posts made by philz
-
RE: OOP fail
-
RE: Don't test, it gets in the way of code coverage
@Salami said:
The only problem here is that you care too much. If they want to do sloppy development in the company, that is what they are going to do, and you should go with the flow. In a lot of businesses, there is a lot more profit in writing bad code and not testing it.
This. If you're selling consulting for companies that want to spend the least amount necessary for something, this is what they actually want. They know they will not get an engineering masterpiece, but something that will get the job done.
They don't want perfect or even good, they just want 'good enough'.
-
RE: Force.com / Salesforce - is it WTFy?
Well I don't consider PHP bad - but then I never coded PHP for a living.
For me, the language, APEX in this case, is almost never the issue. APEX doesn't make your life too easy though - you cannot step through your code, as you could with some Java framework. So you might see a lot of System.debug('this is the spot') statements, which write into a debug log.
Or: APEX does not have namespaces and it only has very, very basic XML support. And no real support for out-bound SOAP-based webservices.
It depends very much how the company you'll be working for (congrats btw) handles development - salesforce makes it easy, so easy that some sales people start to do data modelling... If your company has sales people doing that... good luck. If not, you'll be alright - people are able to do WTFs in any language. Be sure to post them :-) -
RE: Force.com / Salesforce - is it WTFy?
It's not completly shit - it has some serious WTFs though.
You can code triggers in a language they call APEX. It's Java syntax (mostly) with a few changes: Variables are not case-sensitive. Strings go into single quotes.
They have a eclipse plugin to code your triggers etc - but syntax check is server side. Saving a file? 3 - 20 seconds - depending on which instance you work on and if the US is awake or not.
Checkboxes have 3 values (the value is a boolean - w/ 3 values): True, False and Null.The trickiest part with salesforce is getting around/working within the "limits" (google spring 11 governor limits) - for example you can only execute a few DML statements within a trigger (150 I think).