APAR status |
Closed as program error.
| Error description
From Admin Console -> Tasks -> Create -> Application Server
at the enterprise bean list, deploy Enterprise Bean froma jar
file. Browse and select the appropriate JAR file which contains
the beans. Accept the default names, click on Finished. Once
everything is created expand the container and the new beans wil
l have Bean added to the end of the names. So mySession becomes
mySessionBean etc. If you add the Beans into the container
once the application server has already been created the word
Bean is not appended to the name.
defect 83450 Local fixProblem summary
jar vs. an individual bean in the jar browser, the bean name put
in the Name field for the bean differs. For example, if Foo.jar
contains one bean named FooBean, selecting Foo.jar in the jar
browser will set the Name field in the Create EnterpriseBean
dialog to "FooBean", but selecting the bean itself in the jar
browser sets the Name field to "FooHome". Problem conclusion
PTF 1 for 3.5. Temporary fixComments
APAR information | APAR number | PQ41199 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2000-09-01 | Closed date | 2000-11-06 | Last modified date | 2000-11-06 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED SU | Fixed component ID | 5648C8402 |
Applicable component levels | R350 PSY | UP |
|