[jira] Resolved: (AXIS2-4562) JAX-WS: JAXBContext construction in JAX-WS should avoid SessionBean

["Rich Scheuerle (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AXIS2-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rich Scheuerle resolved AXIS2-4562.
-----------------------------------

    Resolution: Fixed

> JAX-WS: JAXBContext construction in JAX-WS should avoid SessionBean
> -------------------------------------------------------------------
>
>                 Key: AXIS2-4562
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4562
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Background:
> The JAX-WS runtime inspects the JAX-WS artifacts to determine which packages or classes should be part of the JAXBContext.
> In most cases, the JAXBContext is constructed with a series of packages (which is relatively fast).
> However if a package does not contain JAXB ObjectFactory or package.info, then the JAXBUtils code must inspect individual classes in the package to see if they are actually JAXB tolerable.
> Problem:
> When the code falls down this secondary lookup path, it should avoid classes that implement javax.ejb.SessionBean.  Such classes are not JAXB classes and inspecting those classes can result in degraded performance.
> Solution:
> I have a design to inspect classes to see if they should be skipped over.  For example classes that implement SessionBean should be skipped.  This new code avoids loading the SessionBean objects (which may not be present).  
> I am testing the solution, and I am designing a unit test to verify the code.

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