You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (Created) (JIRA)" <ji...@apache.org> on 2012/02/27 00:46:48 UTC

[jira] [Created] (TOMEE-143) JAXB Performance boost via saving generated accessors

JAXB Performance boost via saving generated accessors
-----------------------------------------------------

                 Key: TOMEE-143
                 URL: https://issues.apache.org/jira/browse/TOMEE-143
             Project: TomEE
          Issue Type: Improvement
            Reporter: David Blevins


The JAXB RI itself will use reflection to generate accessor classes.  We use JAXB for reading all descriptors.  The result is a below 1 second startup is impossible unless JAXB can be optimized:

This call alone takes over 1 second:

        JAXBContextFactory.newInstance(
                Application.class,
                ApplicationClient.class,
                Beans.class,
                Connector.class,
                EjbJar.class,
                FacesConfig.class,
                HandlerChains.class,
                JavaWsdlMapping.class,
                Persistence.class,
                TldTaglib.class,
                WebApp.class,
                WebFragment.class,
                Webservices.class,
                ValidationConfigType.class,
                EntityMappings.class,
                OpenejbJar.class,
                org.apache.openejb.jee.jpa.unit.Persistence.class,
                PersistenceFragment.class
        );

Simply saving the generated JAXB classes maybe be the way to avoid this reflection overhead.




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (TOMEE-143) JAXB Performance boost via saving generated accessors

Posted by "David Blevins (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TOMEE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264772#comment-13264772 ] 

David Blevins commented on TOMEE-143:
-------------------------------------

2012-02-26 - http://svn.apache.org/viewvc?view=revision&revision=1293969 - dblevins
2012-02-26 - http://svn.apache.org/viewvc?view=revision&revision=1293977 - dblevins

                
> JAXB Performance boost via saving generated accessors
> -----------------------------------------------------
>
>                 Key: TOMEE-143
>                 URL: https://issues.apache.org/jira/browse/TOMEE-143
>             Project: TomEE
>          Issue Type: Improvement
>            Reporter: David Blevins
>            Assignee: Jonathan Gallimore
>
> The JAXB RI itself will use reflection to generate accessor classes.  We use JAXB for reading all descriptors.  The result is a below 1 second startup is impossible unless JAXB can be optimized:
> This call alone takes over 1 second:
>         JAXBContextFactory.newInstance(
>                 Application.class,
>                 ApplicationClient.class,
>                 Beans.class,
>                 Connector.class,
>                 EjbJar.class,
>                 FacesConfig.class,
>                 HandlerChains.class,
>                 JavaWsdlMapping.class,
>                 Persistence.class,
>                 TldTaglib.class,
>                 WebApp.class,
>                 WebFragment.class,
>                 Webservices.class,
>                 ValidationConfigType.class,
>                 EntityMappings.class,
>                 OpenejbJar.class,
>                 org.apache.openejb.jee.jpa.unit.Persistence.class,
>                 PersistenceFragment.class
>         );
> Simply saving the generated JAXB classes maybe be the way to avoid this reflection overhead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (TOMEE-143) JAXB Performance boost via saving generated accessors

Posted by "Jonathan Gallimore (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TOMEE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Gallimore reassigned TOMEE-143:
----------------------------------------

    Assignee: Jonathan Gallimore
    
> JAXB Performance boost via saving generated accessors
> -----------------------------------------------------
>
>                 Key: TOMEE-143
>                 URL: https://issues.apache.org/jira/browse/TOMEE-143
>             Project: TomEE
>          Issue Type: Improvement
>            Reporter: David Blevins
>            Assignee: Jonathan Gallimore
>
> The JAXB RI itself will use reflection to generate accessor classes.  We use JAXB for reading all descriptors.  The result is a below 1 second startup is impossible unless JAXB can be optimized:
> This call alone takes over 1 second:
>         JAXBContextFactory.newInstance(
>                 Application.class,
>                 ApplicationClient.class,
>                 Beans.class,
>                 Connector.class,
>                 EjbJar.class,
>                 FacesConfig.class,
>                 HandlerChains.class,
>                 JavaWsdlMapping.class,
>                 Persistence.class,
>                 TldTaglib.class,
>                 WebApp.class,
>                 WebFragment.class,
>                 Webservices.class,
>                 ValidationConfigType.class,
>                 EntityMappings.class,
>                 OpenejbJar.class,
>                 org.apache.openejb.jee.jpa.unit.Persistence.class,
>                 PersistenceFragment.class
>         );
> Simply saving the generated JAXB classes maybe be the way to avoid this reflection overhead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira