Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Skeleton Generation has Changed without props File Change

2 posts in Java J2EE specific Last posting was on 2008-12-10 02:30:26.0Z
Donnie Love Posted on 2008-12-08 11:53:05.0Z
Sender: 1e2b.493d0565.1804289383@sybase.com
From: Donnie Love
Newsgroups: sybase.public.easerver.j2ee
Subject: Skeleton Generation has Changed without props File Change
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <493d0aa1.1e9f.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 8 Dec 2008 03:53:05 -0800
X-Trace: forums-1-dub 1228737185 10.22.241.41 (8 Dec 2008 03:53:05 -0800)
X-Original-Trace: 8 Dec 2008 03:53:05 -0800, 10.22.241.41
Lines: 46
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.easerver.j2ee:7897
Article PK: 208323

For some unknown reason, this past Friday my Java skeleton
file started being generated with different code than it was
earlier in the day. The change is causing compiler errors
from other baselined code.

I have not changed anything in the component property file,
nor the IDL that is being generated. It's like something in
my environment has changed that is causing the Jaguar
Manager to act differently. I've uninstalled and reinstalled
EAServer and it still generates the new code.

The component Instance Property checkboxes that are checked
are Concurrency, Pooling, and Sharing. The new code that is
generated has a "_singleton" member and a "getInstance()"
method to return it.

This makes sense to me, as the property file has
"sharing=true". However, the code that was generated prior
to Friday never had this member nor method. I've compared my
property file against the one that we use on our Solaris
build platform, and they are identical. The generated code
on the Solaris platform does not have the member nor method.
Both generated files (new and old) have a reference to the
property file - stating that it was generated from it.

I am certain that my Windows XP client did not generate this
new code prior to Friday. So, what would make the code
generation do this? It is possible that our PC
administrators pushed out some OS changes that might be
affecting this.

The underlying problem is that the implemenation file throws
an exception in the constructor that the skeleton doesn't
catch. I could change the baseline code to not do this, but
I want to know why things have changed and how to get back
to our original baseline. I'm working on a major software
release and I don't want to make changes to code that has
been working for years and is not part of the release.
That's too risky at this point.

Any ideas?

Thanks,

-Donnie
EAServer 5.0


Evan Ireland [Sybase] Posted on 2008-12-10 02:30:26.0Z
From: "Evan Ireland [Sybase]" <eireland@sybase.com>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
Newsgroups: sybase.public.easerver.j2ee
Subject: Re: Skeleton Generation has Changed without props File Change
References: <493d0aa1.1e9f.1681692777@sybase.com>
In-Reply-To: <493d0aa1.1e9f.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <493f29c2@forums-1-dub>
Date: 9 Dec 2008 18:30:26 -0800
X-Trace: forums-1-dub 1228876226 10.22.241.152 (9 Dec 2008 18:30:26 -0800)
X-Original-Trace: 9 Dec 2008 18:30:26 -0800, vip152.sybase.com
Lines: 51
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.easerver.j2ee:7898
Article PK: 208326

Donnie,

Try changing the "sharing" property to false and regenerating the skeleton.

Donnie Love wrote:
> For some unknown reason, this past Friday my Java skeleton
> file started being generated with different code than it was
> earlier in the day. The change is causing compiler errors
> from other baselined code.
>
> I have not changed anything in the component property file,
> nor the IDL that is being generated. It's like something in
> my environment has changed that is causing the Jaguar
> Manager to act differently. I've uninstalled and reinstalled
> EAServer and it still generates the new code.
>
> The component Instance Property checkboxes that are checked
> are Concurrency, Pooling, and Sharing. The new code that is
> generated has a "_singleton" member and a "getInstance()"
> method to return it.
>
> This makes sense to me, as the property file has
> "sharing=true". However, the code that was generated prior
> to Friday never had this member nor method. I've compared my
> property file against the one that we use on our Solaris
> build platform, and they are identical. The generated code
> on the Solaris platform does not have the member nor method.
> Both generated files (new and old) have a reference to the
> property file - stating that it was generated from it.
>
> I am certain that my Windows XP client did not generate this
> new code prior to Friday. So, what would make the code
> generation do this? It is possible that our PC
> administrators pushed out some OS changes that might be
> affecting this.
>
> The underlying problem is that the implemenation file throws
> an exception in the constructor that the skeleton doesn't
> catch. I could change the baseline code to not do this, but
> I want to know why things have changed and how to get back
> to our original baseline. I'm working on a major software
> release and I don't want to make changes to code that has
> been working for years and is not part of the release.
> That's too risky at this point.
>
> Any ideas?
>
> Thanks,
>
> -Donnie
> EAServer 5.0