[jira] Commented: (XBEAN-94) Need newest qdox version.... existing one freaks out on <.

[alex322 (JIRA)]

[ 
https://issues.apache.org/jira/browse/XBEAN-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536366
 ] 

alex322 commented on XBEAN-94:
--

QDox often fails on perfectly legitimate source files.
Whould it be feasible to have the MappingGeneratorTask implemented as a 
standard doclet?
It would then be invoked by  Need newest qdox version existing one freaks out on <.
> --
>
> Key: XBEAN-94
> URL: https://issues.apache.org/jira/browse/XBEAN-94
> Project: XBean
>  Issue Type: Bug
>  Components: maven-plugin
>Affects Versions: 3.1
>Reporter: David Jencks
>Assignee: David Jencks
> Fix For: 3.2
>
>
> Qdox 1.6.1 can't handle x < y in field initializations.  1.6.3 can.  Apache 
> ds needs this :-)

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

[jira] Updated: (XBEAN-97) default-lazy-init is ignored

[alex322 (JIRA)]

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

alex322 updated XBEAN-97:
-

Component/s: spring

> default-lazy-init is ignored
> 
>
> Key: XBEAN-97
> URL: https://issues.apache.org/jira/browse/XBEAN-97
> Project: XBean
>  Issue Type: Bug
>  Components: spring
>Reporter: alex322
>
> lazyInit is always false.
> Adding this snippet to 
> org.apache.xbean.spring.context.v2c.XBeanNamespaceHandler.parseBeanFromExtensionElement
>  should solve the problem :
>   BeanDefinition def = result.getBeanDefinition();
>   if (def instanceof AbstractBeanDefinition) {
>   AbstractBeanDefinition adef = 
> (AbstractBeanDefinition) def;
>   if 
> (!element.hasAttribute(BeanDefinitionParserDelegate.LAZY_INIT_ATTRIBUTE)) {
>   
> adef.setLazyInit(parserContext.isDefaultLazyInit());
>   }   
>   }
> Also checking for top-level bean definition can be simplified:
> if (!parserContext.isNested())

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

[jira] Created: (XBEAN-96) Enum properties appear as elements not attributes in the xsd schema

[alex322 (JIRA)]

Enum properties appear as elements not attributes in the xsd schema
---

 Key: XBEAN-96
 URL: https://issues.apache.org/jira/browse/XBEAN-96
 Project: XBean
  Issue Type: Bug
  Components: spring
Reporter: alex322


XsdGenerator makes a decision on whether a property is going to be an attribute 
or an element  based on Util.isSimpleType
isSimpleType doesn't have a specific check for Enums.
Moreover I think it may make sense to allow attributes for complex properties 
to support references:



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