PK93058: ENDPTENABLER MAY NOT FIND A JAX-WS WEBSERVICE WHEN A BEAN CLASS IS LOCATED IN AN EXTERNAL EJB JAR.

Fixes are available

APAR status

Closed as program error.

Error description

The endptEnabler tool may not find a JAX-WS Web Service
when a Java bean class is located in an external EJB jar.

When running this command:

endptEnabler.bat -CCtracefile=trace.log
-CCtrace=com.ibm.ws.websphere.*=all

The user may see the following message:

WSWS2021I: Skipping the enterprise bean module <name>.jar
because it contains no Web services.

Local fix

```
Candidate to be fixed in next release
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server            *
*                  administrators of JAX-WS                    *
****************************************************************
* PROBLEM DESCRIPTION: The endptenabler tool may fail to       *
*                      enable certain EJBs projects.           *
****************************************************************
* RECOMMENDATION:  Install a fixpack that contains this APAR   *
****************************************************************
The endptenabler tool may not detect the JAX-WS Web Service
application if all of the following are true:
  * The service implementation bean extends an abstract
class.
  * The abstract class is located in a different JAR within
the same EAR file.

When these conditions are met, the user will see the following
message:

WSWS2021I: Skipping the enterprise bean module <name>.jar
because it contains no Web services.

If trace is enabled, the following trace information may be
seen in the trace log:

ExceptionFact 1  org.apache.axis2.jaxws.ExceptionFactory
createWebServiceException Create Exception:

javax.xml.ws.WebServiceException:
EndpointInterfaceDescriptionImpl: cannot find super class that
was specified for this class.
at
org.apache.axis2.jaxws.ExceptionFactory.createWebServiceExceptio
n(ExceptionFactory.java:173)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:70)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:118)
at
org.apache.axis2.jaxws.description.impl.EndpointInterfaceDescrip
tionImpl.retrieveReleventMethods(EndpointInterfaceDescriptionImp
l.java:684)
at
org.apache.axis2.jaxws.description.impl.EndpointInterfaceDescrip
tionImpl.<init>(EndpointInterfaceDescriptionImpl.java:215)
at
org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
buildEndpointDescriptionFromAnnotations(EndpointDescriptionImpl.
java:634)
at
org.apache.axis2.jaxws.description.impl.EndpointDescriptionImpl.
buildDescriptionHierachy(EndpointDescriptionImpl.java:973)

Problem conclusion

The algorithm for determining dependent classes is changed
to ensure that abstract classes are considered.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.9.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK93058
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-04
Closed date
2009-09-09
Last modified date
2009-09-09

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PM12406

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK93058: ENDPTENABLER MAY NOT FIND A JAX-WS WEBSERVICE WHEN A BEAN CLASS IS LOCATED IN AN EXTERNAL EJB JAR.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?