friso dejonge

Hi,

There is a simple answer like the one below. But maybe it is more challenging to read the java tutorial:

http://java.sun.com/docs/books/tutorial/i18n/format/simpleDateFormat.html

regards,
friso

This is definitively not a topic for beginners. (for once I agree with Naing) Also it is a topic which deserves more attention than it is currently getting in the coding world.

Welcome Ira and Nate!

A whole book about reflection; this should be an interesting read.

Hi,
I would like to add something to this quote,

. You need to position your data in XML for the transformation. Therefore, there is the overhead to create XML. That was extra work I would rather not have done. If your data is coming from the Model as XML, then there is an argument to using XSL-FO – but IMO not a strong one.

2. You need to create an XSL style sheet. This means that the developer needs XSL skills. More importantly, the maintenance staff needs XSL skills. Since the developers already know Java, why develop a second skill set?

I' ve been in a project where I had to make sure we were delivering on time and within budget. This means making sure no more hours were actually booked then needed. So my project used iText, and the junior developers could - after reading the documentation start building pdf's. Obviously what we did was create a small framework for common headers, footers etc. We managed.
The learning curve was not too steep. Now I can only imagine what would happen if I gave junior developers the XML-XSL-FO skills to learn. It would never have been on time.

But to be fair the last remark on developers already knowing java, and why develop a second skill set I disagree. Developers nowadays need to know about all sorts of languages and skills (xml - xsl - java/j2ee - ant - junit - sql - etc) But that is up to the developer himself whether he want to invest time in new technologies, or if he wants to get this spoon fed.

regards,
friso

hi,

any tips on ejb's ? Take a look at Rod Johnson's book Expert - One-on-One J2EE Development without EJB. This is exactly the opposite of what you might want, but it does give you valuable (and life saving) tips.

regards,
friso

hi Pope,

What I have in mind is the following: changing switch case statements into a reflection orientated design like mentioned in book : 'Refactoring: Improving the Design of Existing Code' - 'martin fowler'.

I would like to know if the reflection in actin book described more refactoring issues.

regards,
friso

he baz,
long time mate, but take a look at chapter 7 which is downloadable, this may answer your question.
(http://www.manning-source.com/books/franciscus/franciscus_chp7.pdf)
cheers,
friso

welcome guys,
I hope you will take time (lots of time) to answer all questions.

Yes, we do use it in our project. We do use it in some sort of factory pattern and with the proxy pattern. It is a very large project and usually when new people start we have to explain a bit more than with the usual straightforward coding. I think this is a bit of a drawback, because you cannot really see which class is actually created. Therefore debugging / finding the right classes for fixing bugs is more difficult.

Maybe the authors can reply on this drawback.

regards,
friso

Hi writers,

First of all, thanks for writing this book, when I look at the book reviews this seems to be one of the must have books. So congrats on the 10 horseshoes from javaranch.

When I looked at the manning publishers website (http://www.manning.com/forman) it shows there are a couple of chapters up for download. Yesterday the links did not work, today they do. And I agree, it is a nice read.

So obviously this brings me to my working situation, to try and bring some of it in practice. I currently work in a location that could help with a lot of refactoring. My question is, are there any chapters on refactoring with reflection ?

thanks,
friso

Hi Korol,

Can't really help you with a direct answer, I can just give a warning. There is a book on java/net interoperability, but before you buy, read the revieuws first. It describes .net and it describes Java, but not a real interoperability between the two.

Now back to your question. There are a couple of approaches, currently the most common one is webservices which can be written and used by java and .net.

On the other hand, it may be enough for your application to export xml from one application and import it in the other applciation. That just depends on the type.

regards,
f

thanks eliotte for being here and answering the questions.

Congrats to the winners.

Hi elliotte,

Yesterday I read a book that handled insecure code, and proxies for requests and responses of your browser. In what way would your book be helpfull to write a proxy to see all incoming and outgoing messages and headers ?

thanks,
friso

hi elliotte,

When I follow the amazon link, I am also drawn to the reviews in there. Beside very good comments, there also seems to be one disturbing comment. What is your view on this. (I appreciate the fact that this probably deals with an earlier print)

Avoid. This book appears to have quite a reputation, but despite being in its 2nd edition, it is riddled with errors. The book exhibits some fundamental misapprehensions about TCP/IP; as a result it perpetrates some astonishing misinformation, much of it quite basic. Partial list: the nature of a socket close operation; what IOException when closing a socket means; what happens when the listen backlog is exceeded; specification of the ServerSocket constructors; Nagle's algorithm (Socket.setTcpNoDelay); linger; keepalive; etc etc.Of the examples which do work, the PortScanner and LocalPortScanner are provided in versions which perpetrate atrocities on the local machine and network by not closing sockets. Multi-homing very cursorily treated, not even indexed. Firewalls apparently treated in one page. Role of TTL in multicast apparently ignored.

thanks,
friso

welcome elliot,
hope you feel at home