Managing GlassFish JDBC Resources via REST
Jason Lee 2011-03-10
I was asked this morning about creating JDBC resources via REST. As with user management , it's actually pretty simple, once you've seen how. Let's take a look.
Jason Lee 2011-03-10
I was asked this morning about creating JDBC resources via REST. As with user management , it's actually pretty simple, once you've seen how. Let's take a look.
Jason Lee 2011-03-09
A user on the GlassFish forums recently asked how to create users in bulk. The asadmin
command create-file-user
doesn't support passing the password as a parameter, which makes scripting difficult. The REST interface, though, can help there, and it's really pretty simple.
Jason Lee 2011-03-04
If you've been following my series on using the GlassFish REST interface, you've probably noticed that your JSON and XML output isn't pretty-printed like mine. While there are several online tools that can fix that for you, there's no need for the extra step. GlassFish will do that for you. Let's look at how to make that happen.
Jason Lee 2011-02-28
In previous posts, I've shown various ways to manage a GlassFish 3.1 server via its REST interface. As nice as that is, we also support monitoring your server via REST as well. In this article, we'll take a look at some of the things you can ask of your server.
Jason Lee 2011-02-28
People often ask what the difference is between the free GlassFish and the commercially-supported version. The answer really is "not much" in terms of the core server itself (pretty much just branding changes). The commercial version, though, has some nice value-add features, such as the Performance Tuner , amongst others.
I'm really, really pleased with how GlassFish 3.1 has turned out. We still (and will always) have more work to do, but this is a solid release that finally fills in some enterprise holes that v3 didn't have time to fill. Download it, install it, kick the tires a bit, and tell us what you what you think . In the meantime, we're going to go ahead and get started on 3.2.