[
https://issues.apache.org/jira/browse/CXF-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14618498#comment-14618498
]
Sergey Beryozkin commented on CXF-6481:
---------------------------------------
The problem is related to the way JAXB schema compiler treats elements of
ParameterizedBoolean (or other parameterized types found in
parameterized-types.xsd). It only affects elements and not attributes. So, the
following:
{code:xml}
<xs:element name="sessionSupport" type="ptp:ParameterizedBoolean"
minOccurs="0"/>
{code}
gets generated to:
{code:java}
public class JettyHTTPServerEngineConfigType {
@XmlSchemaType(name = "anySimpleType")
protected Boolean sessionSupport;
// other properies
{code}
and JAXB fails to read an httpj:sessionSupport context property into it.
While
{code:xml}
<xs:element name="sessionSupport" type="xsd:boolean" minOccurs="0"/>
{code}
gets generated to:
{code:java}
public class JettyHTTPServerEngineConfigType {
protected Boolean sessionSupport;
// other properies
{code}
and JettyHTTPServerEngineConfigType gets properly initialized by JAXB.
It is a strange issue indeed but at least I'm certain this is what the cause of
the problem is. Note this is not a problem with Spring as a different parsing
mechanism is used there.
> Jetty HTTPJ session manager configuration is not effective
> ----------------------------------------------------------
>
> Key: CXF-6481
> URL: https://issues.apache.org/jira/browse/CXF-6481
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Reporter: Sergey Beryozkin
> Fix For: 3.1.2
>
> Attachments: camel-context.xml, cxf-httpj-test.zip
>
>
> It appears a session manager is not available if activated from the httpj
> configuration starting from Jetty 8
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
