Insert Witty Irony Here

Main | Next page »

Friday January 11, 2008

Cannot edit entries on the GlassFish wiki?

You may run into this message when you try to edit a page on the GlassFish project wiki site:

Forbidden

Sorry, but you are not allowed to do that.

Usually we block access to something because you do not have the correct privileges (e.g., read, edit,
comment) for the page you are looking for. In this particular case, it is likely that you are not
listed in the page’s access control list or that your privileges aren’t high enough (you want to 
edit, but ACL only allows ‘read’).

It is also possible that JSPWiki cannot find its security policy, or that the policy is not 
configured correctly. Either of these cases would cause JSPWiki to block access, too.

Better luck next time.

You may ask, "Why can't I add or edit a page on the Glassfish wiki site after I have logged in?"

Due to spamming and wiki vandals, the folks in the GlassFish project have added an extra step to the authoring process.

You may ask, "How do I get permission to add and edit pages on the GlassFish wiki site?"

It is explained in a FAQ entry.

I hope this entry will provide you with "Better luck next time."

(2008-01-11 09:39:14.0) Permalink

Monday December 31, 2007

GIGAOM on SIP

I found this message about SIP in my reader today. If you are thinking about doing SIP application development, you might want to look at the capabilities that we are adding to NetBeans to develop SIP Applications and the Sailfin project.

(2007-12-31 10:43:15.0) Permalink

Monday July 30, 2007

Monkeying with the GlassFish Issue Tracker

I am a Firefox user but have never really gotten into customizing it with add-ons. That changed a couple days ago, when I came up with a punk hack that I wanted to enable on Google search result pages.

I started to look at Firefox add-ons that might already perform my hack... which would kind of ruin the fun of implementing it... or help me implement it.

One of the add-ons that I found was Greasemonkey. It doesn't perform my hack, but it has allowed lots of people to implement customizations of web-pages that are similar to what I want to do.

I installed it and started to look for scripts that would teach me how to monkey-around. I found this script by Jesse Glick that modifies the page title for Issuezilla entries. Direct link to Jesse's actual script. If you have Greasemonkey installed clicking the link to Jesse's script will ask you if you would like to install it.

I read through the script and took it for a testdrive... and I liked it. Then I remembered that the NetBeans Issuezilla is hosted by the same folks that host the Issue Tracker for the GlassFish community. So, I decided to try an experiment.

I opened the Greasemonkey Manage User Scripts... dialog and saw this.

I used the Add... button to update the Included Pages list to look like this.

I went to Java.net and logged in and went to look for some GlassFish issues that I need to VERIFY. I have been very lazy about that...

When I clicked on a link to see the details on an issue, this is what my Window title looked like.

Then, I figured I would share this with folks in the GlassFish community.

And now, I am done
(2007-07-30 20:00:00.0) Permalink

Thursday January 11, 2007

All good things come to an end.... Many of you know that NetBeans 5.5 provides an excellent development environment for Java EE 5 code to deploy on the application servers based on the GlassFish Project codebase for V1 U1, like Sun Java System Application Server 9.0 Update 1 Patch 1.

Many of you have also been taking advantage of the happy accident that the plugin for V1 U1 was also capable of targeting V2 domains.

Slowly but surely, that happy accidental compatability has erroded away. NetBeans 5.5 users have lost the ability to use NetBeans 5.5 as a development environment for apps that they want to target to recent V2 builds.

But all is not lost. NetBeans 5.5.1 is the SLR to NetBeans 5.5's 300 SL. One of the release drivers for NetBeans 5.5.1 is support for application servers based on the GlassFish Project codebase for V2.

Very few changes are getting rolled into the NetBeans 5.5.1 codebase, so builds are functional and very stable. But, it could use more testing because the GF V2 codebase is still in motion. (2007-01-11 15:52:17.0) Permalink Comments [1]

Friday May 26, 2006

You know what this project needs.... A Theme Song!

That's right; a theme song.

Here is my proposal for how this would work.

First we open an Issue tracker entry, that is the central catalog for the proposed songs...
Each entry is created as a new issue tracker entry, that is marked as a dependent of the catalog entry bug....
After about two weeks, we ask folks to vote for their favorite tune, using the Issue tracker's vote capability....
After a week of voting, we look at the totals and use that tune as the project theme song...

For folks like me with WAY TOO MUCH TIME on their hands, we could even have a second contest to select new lyrics, sung "to the tune of" the selected song. This is sort of like the NetBeans theme song.

Note: Linux has at least TWO... (2006-05-26 14:30:06.0) Permalink

Saturday May 20, 2006

Deploying Liferay : Teaser 1 I intend to write an entry about deploying Liferay onto Sun Java System Application Server Platform Edition 9 using the archive project module for NetBeans 5.5 IDE. It isn't ready yet.

I have run into an issue that has vexed a number of other folks:

The key error message is:

Error reading configuration for portal: The base properties file was not found

I was able to get around this issue by extracting the portal.properties file out of the EAR file and placing it into domain1's lib/classes folder. This folder is part of the domain's classpath.

I know that this won't help folks on "other servers" directly. I hope that folks are able to translate this into a work-around that is applicable to their environment. (2006-05-20 08:54:08.0) Permalink

Wednesday April 05, 2006

Access Log in "real-time" I noticed a thread about delayed updates to the access log for an instance of the app server built by the GlassFish Project.

The user expected the access log to update in real time. In other words, they expected to access a web page and see that access reflected in the access log immediately. When it wasn't, they were concerned.

I found a work-around, that exposed a bug.... But that is a different story....

The news that you can use is in the bug report though. The lag between a web page being accessed and that access being reflected in the access log is controlled by two properties: accessLogBufferSize and accessLogWriteInterval. You can read about them. Making the values of these properties small will decrease the lag between when a user accesses a web page and when that access appears in the servers access log.

It may well slow your server down, too, so you have been forwarned...

You may be able to leverage the self-management features of the GlassFish project's implementation of Java EE 5 to remember to crank up these values (and increase your applications performance "automagically").

That is an entry for another day/author, though.

UPDATE: One of the evaluators provides information about the access log rotation algorithm that is used by the app server implemented by the GlassFish project.

After you read it you will realize why the log hardly ever rotates if you change the rotation suffix to YYYY... (2006-04-05 11:48:23.0) Permalink Comments [1]

Saturday March 25, 2006

BIRT and GlassFish b41 The BIRT project includes a web application for displaying reports. After some fits and starts, folks have been able to get it working on GlassFish. While folks were able to get it working, I did not like the "solution". I spent a bit of time with BIRT 2.0.1 and build 41 to see if I could get a better solution.

I have been able to deploy 2.0.1 on GlassFish build 41, by following the instructions for JBoss, with a couple small changes:

I used the asadmin deploydir command, instead of copying files to a deploy directory. GlassFish has an autodeploy directory, but it expects archives to be placed there, not "exploded" archives.
I did not need to copy the files from Axis 1.2.1, listed in the instructions. It looks like the files are already there in the 2.0.1 release.

I created a <BIRT-ROOT>/WEB-INF/sun-web.xml file. It looked like this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 Servlet 2.5//EN" "http://www.sun.com/software/appserver/dtds/sun-web-app_2_5-0.dtd">
<sun-web-app error-url="">
  <context-root>/birt-viewer</context-root>
  <class-loader delegate="false"/>
  <jsp-config>
    <property name="classdebuginfo" value="true">
      <description>Enable debug info compilation in the generated servlet class</description>
    </property>
    <property name="mappedfile" value="true">
      <description>Maintain a one-to-one correspondence between static content and the generated servlet class' java code</description>
    </property>
  </jsp-config>
</sun-web-app>

I did need to copy commons-logging-1.0.4.jar from Axis 1.2.1, into <BIRT-ROOT>/WEB-INF/lib.
I had to copy the derby.jar from <BIRT-ROOT>/plugins/org.eclipse.birt.report.data.oda.jdbc to <BIRT-ROOT>/WEB-INF/lib

After doing this, I was able to view the "installation report" and the "more complex report". (2006-03-25 17:06:21.0) Permalink Comments [4]

Saturday March 11, 2006

AppFuse and Build 40 This is just a quick note, to let people know that AppFuse 1.9 (Struts/Spring/Hibernate configuration) is working with build 40. Folks will be pleased to note that disabling the security manager made many of the steps I outlined unnecessary.

I am working on entries that provide more details. Look for them in the next couple of days. (2006-03-11 15:19:31.0) Permalink

Wednesday March 08, 2006

Forum posting regarding Adobe's Flex 2.0 Beta on SJSAS 8 Around 1 Feb 2006, folks at Adobe released the Flex 2.0 beta. Since there was a web app associated with it, I decided to try to deploy it to GlassFish.

I wasn't too successful and "real work" diverted my attention from getting Flex 2.0 functional. I was able to share some tips with another Beta tester who was able to make more progress according to this thread. (2006-03-08 00:34:47.0) Permalink

Friday March 03, 2006

Autodeploy classes at your own risk... I have noticed a number of people having issues with using autodeploy. I think they may be following the "advice" of entries/articles like this or this.

Extending the methodology espoused by these entries hasn't been well tested. It is a great trick for demos and examples, but it doesn't scale. You may want to read through this book for more details about the numerous deployment strategies that are supported by application servers, based on the GlassFish Project's code-base. This section is particularly important. The autodeploy mechanism is designed to work with archive files. (2006-03-03 20:46:11.0) Permalink

Wednesday March 01, 2006

Top of the Pops in Santa Clara; Empathy for Developers Sorry, Mick, Keith, Brian, Bill, and Charlie. I could not resist.

A number of people have run into issues deploying and running applications on GlassFish, due to the security manager. You can read some of the stories by clicking on the linked blogs and articles that you can find here.

Well, those GlassFish hatchery workers (oft times known as software engineers in other parts of the world) have seen the pains that the security manager has wrought on developers. Since the goal of Java EE 5 is 'Ease of Development', they have decided to use a null default security manager...

This will make deployment and execution of applications that use many popular frameworks MUCH easier. Petr Blaha also discovered another benefit of running the application server without the security manager.

As Ludo commented, look for the this important EOD change in promoted build 39, which is coming soon. (2006-03-01 08:36:45.0) Permalink Comments [2]

Wednesday February 08, 2006

Custom client policies for JWS App Clients I noticed this thread in the GlassFish forums, this moring. I am sure that Tim will blog about this in greater detail, but this thread has a quick preview for the impatient. (2006-02-08 10:14:55.0) Permalink

Good news for WebWork users One of my co-workers has been able to deploy a large app built on WebWork to GlassFish.

He ran into some security policy issues during deployment and testing. His blog entry has the details. (2006-02-08 08:25:10.0) Permalink

Monday February 06, 2006

News for AppFuse-rs I had posted a quick note about using Equinox on GlassFish. Matt Raible saw it and figured that AppFuse should work, too.

I think it will soon, but not today. A couple other folks appear to have run into an issue in GlassFish related to the use of Acegi. Once the issue is resolved, I will write up an entry about integrating AppFuse into the GlassFish environment (which includes the Derby database). (2006-02-06 17:16:34.0) Permalink