I have migrated VAG Web Transaction to EGL Web Transaction generated to Cobol CICS and test in RBD V.9.1.1 with WTE.

On my first application worked fine but in the second application i got an error:

 

VGJ0604E - Uma exceção ocorreu enquanto tentava carregar o bean, SG001RUBean. Exceção: java.lang.ClassNotFoundException: SG001RUBean. Mensagem: SG001RUBean

 

comparing the first and second application no configuration differences:

 

in the First application, JSP definition:

"jsp:useBean id="FR900RU" scope="request" class="xxxxxxx.sfr.prgm.fr900p.webtrans.FR900RUBean"

and location package class bean

"...\WebContent\WEBINF\classes\xxxxxxx\sfr\prgm\fr900p\webtrans\FR900RUBean.class"

"...\WebContent\WEBINF\classes\xxxxxxx\sfr\prgm\fr900p\webtrans\FR900RURBundle.class"

 

in the Second application, JSP definition:

"jsp:useBean id="SG001RU" scope="request" class="xxxxxxx.ssg.prgm.sg001p.webtrans.SG001RUBean"

and location package class bean

"...\WebContent\WEBINF\classes\xxxxxxx\ssg\prgm\sg001p\webtrans\SG001RUBean.class"

"...\WebContent\WEBINF\classes\xxxxxxx\ssg\prgm\sg001p\webtrans\SG001RURBundle.class"

 

in the csogw.properties:

hptGateway.propertiesRefreshInterval=2
application.*.traceFlag = 1
application.*=CICSP1

serverLinkage.CICSP1.commtype=CICSECI

serverLinkage.CICSP1.contable=csoE037
serverLinkage.CICSP1.serverid=CPMI
serverLinkage.CICSP1.ctgLocation=localhost
serverLinkage.CICSP1.ctgPort=2006
serverLinkage.CICSP1.location=CICSP1

 

I didn't use the property "serverLinkage.xxxx.javaProperty" because i'm generating to COBOL.

 

Why the First application worked fine and the Second application not found the bean class ?

I could not see any difference and both applications use CONVERSE to display uirecord instead of XFER

 

Hsieh,

When you say the second application is failing....is the scenario as follows:

PROG1 starts -> Converse-> returns from converse -> transfer to program Prog2 -> Converse

 

And the error occurs during the Converse after the transfer?

 

If so, I seem to remember something that without a serverlinkage.xxx.javaProperty entry, the gateway servlet will try load the class using the same package as was used in the last access in the servlet.   But I may be wrong.

So a couple of things to do:

a.)  Turn on all tracing in the gw.properties and the csogw.properties.   This will show exactly what is being requested.

b.)  Make sure all the beans/UI records have been regenerated with EGL.

c.)  Try using the programPackageName build descriptor to see if that changes the result...(set the serverlinkage.xxx.javaProperty" to the same package as specified in the programPackageName).

d.) Create explicit entries with a javaProperty for each unique package name.

 

thanks.

 

Mark

Mark,

The two applications are registered in Vagen1EntryPage.jsp to start webapp.

When I start the fr900p webapp works fine

When I start the sg001p webapp doesn't Works

The sg001p does not find your class bean and it does not get to call the server tier.

But the parameter serverlinkage.xxx.javaProperty is only when I generate webapp to Java, correct !?

In my case I'm generating to COBOL VSECICS.

Hsieh,

I seem to remember that the javaProperty was also necessary to specify the location of the beans but that would not match up with the fact that it is working for fr900p.

 

My suggestion...

a.) Make sure "build automatically" is set.  If not, then the actual .class files will not be created in the project

b.) Regenerate the program

c.) Using the navigator view .. make sure the .class file is in the "classes" subfolder under WEB_INF

d.)  Turn on tracing in gw.properties and csogw.properties

e.)  Remove the web/ear project from the application server

f.) Restart the server

g.) Add the Web/Ear project back to the application server'

h.) Run both web transaction apps and see what happens

 

 

Hi Mark,

The web application worked fine after create a new workspace, import project and regenerated all.

Must had some defect in the workspace or wrong compilation must have taken place.

I did not change anything.

Well let's play again. :-)

 

Hsieh

Glad to hear it is working now.   Maybe something did not get compiled previously.