Bug 779795 (SOA-2158)
Summary: | JAXB Accessor Optimisation lost for SOA-P supplied endpoints when using signed jars | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Darran Lofthouse <darran.lofthouse> |
Component: | JBossWS | Assignee: | Nobody <nobody> |
Status: | NEW --- | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.0.0 GA | CC: | rwagner |
Target Milestone: | --- | ||
Target Release: | FUTURE | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://jira.jboss.org/jira/browse/SOA-2158 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
The JAXB Accessor Optimization disappears when using SOA-P supplied endpoints with signed jars. An exception is thrown and JAXB will fall back to using Reflection. As a result, optimization is lost.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Darran Lofthouse
2010-07-14 11:24:18 UTC
Is there a possibility of pregenerating these accessors in juddiv3 (Kurt Stam) as part of the SOA build? There is no solution to dynamic classes being generated under the same package as signed classes. I don't believe JAXB does allow pre-generation of these accessors. Alternatively what issues would there be if the classes in the package 'org.uddi.api_v3' were in an unsigned jar? These classes are only used to be passed into the endpoint and not perform privileged actions so could they be left unsigned? This will not be considered for soa-5.1.0 This issue was triaged for SOA 5.1, decision was to leave it in Future. Link: Added: This issue depends JBWS-3267 RJW, reviewing old cases. Depends JBWS-3267, still valid. Opened JBPAPP-8015 to bring this to EAP's attention. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The JAXB Accessor Optimization disappears when using SOA-P supplied endpoints with signed jars. An exception is thrown and JAXB will fall back to using Reflection. As a result, optimization is lost. |