Skip to main content

Sahoo

Sahoo is an engineer at Sun Microsystems, working in Java EE application server development engineering group. He contributes to glassfish project. Besides that he is also involved in writing a portability checking tool for Java EE applications. Prior experiences include working in C++ language binding for an object database management system, developing enterprise applications using CORBA & messaging middleware. Although his full name is Sanjeeb Kumar Sahoo, he prefers to be called by his last name *Sahoo*.

 

ss141213's blog

Should Class.getAnnotations fail if an annotation type is not available?

Posted by ss141213 on October 8, 2009 at 11:26 PM PDT

While evaluating a GlassFish bug, I discovered a discrepancy in behavior of Class.getAnnotations() between IBM JRE and Sun JRE. the complex GlassFish issue boiled down to a simple test case as discussed below.

autodeploy-bundles directory has been moved to autodeploy/bundles

Posted by ss141213 on October 4, 2009 at 7:37 PM PDT

autodpeloy-bundles directory has been moved to autodeploy/bundles. In my earlier blog titled Using filesystem operations to manage OSGi bundles in GlassFish, I had mentioned the directory name to be ${domain_dir}/autodeploy-bundles/.

Using a REST Console to administer OSGi runtime in GlassFish

Posted by ss141213 on September 4, 2009 at 4:58 AM PDT

Introduction

 

What are our options to administer OSGi runtime in GlassFish? We have already talked about

a) a command line tool, and

b) a web console.

OSGi Declarative Service bundle in GlassFish

Posted by ss141213 on July 24, 2009 at 12:02 AM PDT

Starting with build #56, GlassFish v3 now comes pre-installed with Apache Felix Service Component Runtime, which is an implementation of OSGi Declarative Service Specification.

btrace is now integrated in GlassFish v3

Posted by ss141213 on July 8, 2009 at 10:02 PM PDT

Expect a detailed message from Sreeni and/or other monitoring folks of GlassFish, but I just came to know that BTrace has found its way into GlassFish v3.

Our second hybrid application - EJB as OSGi Service

Posted by ss141213 on June 16, 2009 at 1:02 AM PDT

Last time, we talked about our first hybrid (Java EE + OSGi) application where we discussed not only about development of hybrid applications including kind of maven plugins to use, deployment steps, etc., but also about the lifecycle of OSGi bundle and Java EE artifacts.

Developing Hybrid (OSGi + Java EE) applications in GlassFish

Posted by ss141213 on June 14, 2009 at 1:02 AM PDT

(If you are in a hurry, then download the sample and jump to "build and test" section after doing the necessary set up.)

In my last blog, I mentioned about adding a new module in GlassFish

OSGi enabled web applications inGlassFish

Posted by ss141213 on June 4, 2009 at 3:29 PM PDT

Since the OSGi-fication of GlassFish started, the initial response was very encouraging, but we were often asked as to how we planned to expose the benefits of OSGi platform to end users in a more direct way.

Running GlassFish on other OSGi platforms

Posted by ss141213 on May 30, 2009 at 12:05 PM PDT

Although GlassFish v3 Preview comes with Felix pre-installed, it's pretty easy to make it run on Equinox and other platforms. Given below are the simple steps... 1. Download Equinox or if you have it, use that. 2.

Use of Framework Extension Bundles in GlassFish V3

Posted by ss141213 on May 29, 2009 at 8:49 AM PDT

When you run an application in a plain vanilla Java platform, your code can access publicly visible internal JDK classes. While I understand it is a bad thing, but I do understand that sometimes developers have genuine reasons to access those internal APIs. e.g., our security module in GlassFish has to use some of the JDK Security classes.