JAXWS: Handle packages with a mixture of JAXB and non-JAXB classes
------------------------------------------------------------------

                 Key: AXIS2-3814
                 URL: https://issues.apache.org/jira/browse/AXIS2-3814
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: jaxws
            Reporter: Rich Scheuerle
            Assignee: Rich Scheuerle


Scenario:
User intermingles JAXB and non-JAXB classes in a single package.  (This is not 
a good practice, but it does happen.)
The JAXWS engine attempts to create a JAXBContext from a list of packages.  If 
one or more of the packages do not contain an ObjectFactory, then 
the code falls back to a loading all of the classes in the packages.
Since some of the packages are non-JAXB classes, the JAXBContext construction 
fails...and the webservice fails.

Solution:
Change the fall back approach.  
Instead of constructing a JAXBContext with all of the classes (and failing), 
find the best set of classes.

I am working on the code and a validating unit test.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to