Just thought I'd a few minutes to update the group on my recent testing and use of Merlin 3.0. Porting some of my Phoenix blocks have went remarkably well, and successfully tested some features that I was interested in. Here's a summary of what I've done:
+ Merlin successfully hosting ports of the following Phoenix blocks: hsqldb database server, jetty-phoenix web server, apache ftp server. + I have this merlin deployment up and running as a Unix daemon service on my Solaris9 box at work. This server is now functioning as my team's web server and ftp server, and is available to be used as a general purpose development database server (in addition to our mysql server). + This server is also acting as our local repository for components. We are planning to distributing any components/blocks that we develop to this repository as part of our build process. Other merlin deployments will use this as a remote repository for fetching resources. + Speaking of remote repositories, I did successfully test the proxy support in merlin for resource fetching. Currently, I can fetch resources remote from repositories on the Internet (through our proxy) and simultaneous from a repository behind our firewall that doesn't require going through a proxy. I am now in a position to demonstrate to my team the merlin concept of simply pushing out a block.xml as a distributable artifact to existing standard merlin installations. I'm targeting this demonstration later in the week or early next week. Looks good so far. Next stop is playing with the new PhoenixJMS block and delving into Merlin composition concepts. Hopefully the PhoenixJetty and PhoenixFTP blocks that run under Merlin will be available soon for others to consume. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
