Well, the xmas holidays are arriving so it's all coming to a final rush. Too many things to do and not enough time. To the guy that was asking me some UML diagrams; I'm remodeling a bit the whole thing so I'm more in the programming mode then design mode. I'm trying to explore the use of Filters and the goal would be to switch from the ActionServlet to an "ActionFilter" that I'm for the moment calling Controller. At the moment I'm assigning a URL mapping /Controller, but perhaps it'd be nice not to do a fixed URL, something like *.action? I had some bugs during deployment, I'm not sure if it's not possible to do or it was a netbeans problem (damn beta). A question that I'm asking myself now is if I call the next Filter in the chain that is mapped to /Controller once passed all Filters in the chain, it calls the ones in the /*? It's something that I think could help separate the Actions and a mechanism of Autorizations/Authentications/Error_notification.Also, which would be the best order to apply the filters? I'm already thinking about an Transformation Filter but they are not among the list of things that filters in general do. Also this would be a nice moment to start working with JSF but seeing the extent of the effort needed to integrate it with my framework I'm a bit conservative. In that way I'd be branching away from the use of JSP as the Model, thus making the application more prone to use over different devices. Still at this moment I think it's too early. I also started to develop my own tags (as .tag for now, perhaps a tag library if the need arouses) so that the resulting jsp's are even cleaner now. Like I said my own tags are perhaps just a way to postpone the use of JSF but we'll see what the future brings.
Relaxing SSL validation for JaxWS
I've recently had the need to access a web service developed in .Net and signed with a self signed certificate. I've decided to use the JaxWS and the Metro stack to develop the client and run it on Java6. As a plus, the service was protected with username and password. The service was exposed on an IP address and I repetedly had problems in establishing a connection. In the end, thanks to this article, it was obvious that the certificate was not created with the alternative name attribute but it was not an option to change the certificate as the web service was already used by other consumers (.net clients don't suffer by this issue). So, on my quest to relax the validation, I've found out this article and code snippet, which did not compile at first (I guess package names were changed in JDK6) so I've did some trivial refactoring and now, after invoking the static methods in the client code, the SSL connection gets validated with no problems. Hope it helps and th...
Comments