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.

EAServer 6.2: Class folders

2 posts in Java J2EE specific Last posting was on 2009-01-28 20:02:39.0Z
Mattias Posted on 2009-01-27 10:34:49.0Z
Sender: 6fff.497e066c.1804289383@sybase.com
From: Mattias
Newsgroups: sybase.public.easerver.j2ee
Subject: EAServer 6.2: Class folders
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <497ee349.37a.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 27 Jan 2009 02:34:49 -0800
X-Trace: forums-1-dub 1233052489 10.22.241.41 (27 Jan 2009 02:34:49 -0800)
X-Original-Trace: 27 Jan 2009 02:34:49 -0800, 10.22.241.41
Lines: 20
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.easerver.j2ee:7903
Article PK: 208328

Hi,

We are in the process of testing EAServer 6.2 to replace our
existing 5.1 servers (all on Solaris). I have experienced
some problems with finding classes.
When I deploy components on 5.1, the classes, stubs,
skeletons, helper and holder classes are all automatically
placed under java/classes. This folder we used in the
classpath for our tomcat that accesses the EAServer and also
in the classpath for our build projects. I have seen on the
class loaders in 6.2 that they also points to ~/java/classes
(and ~/html/classes) but those folders don't exist. The only
way I have found to access the EJBs is to add all
/deploy/ejbjars/* folders to the classpaths (which also
means that the tomcat needs to be restarted to be able to
find a new EJB component). Is this how it's supposed to work
or is there some other recommended way to solve this?

Best regards,
Mattias


Evan Ireland [Sybase] Posted on 2009-01-28 20:02:39.0Z
Message-ID: <4980B9DE.1020102@sybase.com>
From: "Evan Ireland [Sybase]" <eireland@sybase.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
Newsgroups: sybase.public.easerver.j2ee
Subject: Re: EAServer 6.2: Class folders
References: <497ee349.37a.1681692777@sybase.com>
In-Reply-To: <497ee349.37a.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
Date: 28 Jan 2009 12:02:39 -0800
X-Trace: forums-1-dub 1233172959 10.22.241.152 (28 Jan 2009 12:02:39 -0800)
X-Original-Trace: 28 Jan 2009 12:02:39 -0800, vip152.sybase.com
Lines: 39
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.easerver.j2ee:7906
Article PK: 208329

Mattias,

It looks as if you have stumbled across an issue that hasn't been
reported before.

Since your tomcat server wants to see a single directory as the root for
stub classes etc, perhaps you can create a shell/batch script that
copies the classes from various deploy/... folders into ~/java/classes.

Probably we should add a "-jc" command line option to the deploy tool to
do this copying automatically (but just for the EJB-JAR being deployed).

If you are interested in the above, and happen to have a case number for
this issue, please forward the case number to me. (Without a case
number, we can't track this issue properly).

Thanks.

Mattias wrote:
> Hi,
>
> We are in the process of testing EAServer 6.2 to replace our
> existing 5.1 servers (all on Solaris). I have experienced
> some problems with finding classes.
> When I deploy components on 5.1, the classes, stubs,
> skeletons, helper and holder classes are all automatically
> placed under java/classes. This folder we used in the
> classpath for our tomcat that accesses the EAServer and also
> in the classpath for our build projects. I have seen on the
> class loaders in 6.2 that they also points to ~/java/classes
> (and ~/html/classes) but those folders don't exist. The only
> way I have found to access the EJBs is to add all
> /deploy/ejbjars/* folders to the classpaths (which also
> means that the tomcat needs to be restarted to be able to
> find a new EJB component). Is this how it's supposed to work
> or is there some other recommended way to solve this?
>
> Best regards,
> Mattias