Troubleshooting
Problem
There are two methods to create a JAXBContext when the client uses JAXB: 1. Provide the list of packages that contain JAXB classes. 2. Provide a list of potential JAXB classes. The client application may be logging errors similar to the ones listed below: - JAXBUtils 1 org.apache.axis2.jaxws.message.databinding.JAXBUtils checkPackage looking for xyz/package/framework/webservice/exception/jaxb.index - JAXBUtils 1 org.apache.axis2.jaxws.message.databinding.JAXBUtils checkPackage jaxb.index file Not Found: xyz/package/framework/webservice/exception/jaxb.index - JAXBUtils 1 org.apache.axis2.jaxws.message.databinding.JAXBUtils createJAXBContextValue Package xx.bpm.framework.webservice.exception does not contain an ObjectFactory or package-info class. Searching for JAXB classes - javax.xml.bind.JAXBException: xyz.package.finxxx.xxp.webservices.xxyyzz is not known to this context" Creating a JAXBContext to make sure the package can be seen should resolve this problem.
Symptom
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
03 March 2025
UID
swg21634869