axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shameera Rathnayaka (JIRA)" <>
Subject [jira] [Commented] (AXIS2-5515) ObjectSuplier doesn't provide a way to instantiate object in runtime which is not a POJO.
Date Sat, 04 May 2013 17:32:16 GMT


Shameera Rathnayaka commented on AXIS2-5515:

Hi Andreas,
Yes , agree on your points, it is not an good idea to provide custom ObjectSuppliers to access
XML data in runtime. This instantiate problem arise with Java UUID objects, as an alternative
we can handle java UUID as same as what we does with java  Enum, Map , List etc , but before
that need to realized, should we support UUID in that way? 
> ObjectSuplier doesn't provide a way to instantiate object in runtime which is not a POJO.

> ------------------------------------------------------------------------------------------
>                 Key: AXIS2-5515
>                 URL:
>             Project: Axis2
>          Issue Type: Improvement
>          Components: kernel
>    Affects Versions: 1.6.2, 1.7.0
>            Reporter: Shameera Rathnayaka
>            Assignee: Shameera Rathnayaka
>             Fix For: 1.7.0
>         Attachments: ObjectSupplier.patch
> Currently ObjectSupplier interface doesn't provide a way to instantiate Objects in runtime
which doesn't has nullary constructor. it only define one method which takes 
> only class object as method parameter. There is no way to instantiate a non POJO in runtime.
Even we doesn't need to provide such a feature with DefaultObjectSupplier , 
> it is good to provide a API to do that. Then user can provide their own implementation
this. Adding new method(Object getObject(Class clazz , OMElement beanElement) throws AxisFault;)
>  to ObjectSupplier would provide this. We don't need to implement this method in our
> One use case for this is Java.util.UUID , this class doesn't has nullary constructor
which only has UUID(long mostSigBits, long leastSigBits) , in such a case user can writer

> their own implementation of ObjectSupplier and use it. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message