Aegis, Proxies & Interfaces

[Lee Theobald <Le...@openobjects.com>]

Hi,

Bit of a newbie question this but asking the question is the only way I'm
going to learn :)  I'm using Aegis databindings with my service.  At the
moment, the inputs to my service methods are handed over as Proxy objects. 
I've been taking a read of the Aegis documentation and in particular 
http://xfire.codehaus.org/Aegis+and+Interfaces this page: Aegis & Interfaces
.  According to that page I can specify an implementing class for my service
to use instead of a Proxy using code similar to below:

Service service = ...;

service.setProperty("com.acme.User.implementation", "com.acme.UserImpl");
Is it possible for me to declare this implementing class via either
annotations or in my beans.xml?  At the moment the only place I ever use the
Service class is the client that accesses my service.  I don't really want
to have to declare the implementing classes everytime a piece of code wants
to use my service.

Thanks in advance for any input

Lee



-- 
View this message in context: http://www.nabble.com/Aegis%2C-Proxies---Interfaces-tf4297824.html#a12233094
Sent from the cxf-user mailing list archive at Nabble.com.

Re: Aegis, Proxies & Interfaces

[Lee Theobald <Le...@openobjects.com>]

Hi Dan,

Cheers for letting me know.  I've got a workaround in my code for now so
I'll be waiting for the snapshot or the 2.0.2 release.  Thanks for looking
into it for me,

Regards,
Lee


Dan Diephouse-2 wrote:
> 
> Hi Lee,
> 
> Looks like we got ourselves a bug. I've implemented a fix for this which 
> I'll commit today. To get this to work you can either wait for us to 
> publish a new snapshot (this weekend? we really need to automate this), 
> build CXF yourself, or try the 2.0.2 release which will probably happen 
> in two weeks.
> 
> Cheers,
> - Dan
> 
> Lee Theobald wrote:
>> A bit of a bump to this topic as I'm still having issues.  I'm trying
>> things
>> like below:
>>
>> <!-- Service endpoint -->
>> <jaxws:endpoint id="searchlogger"
>>     implementor="com.oobjects.logging.SearchLogger"
>>     address="/SearchLogger">
>>     <jaxws:properties>
>>         <entry
>> key="com.oobjects.logging.tables.ILogEntry.implementation"
>> value="com.oobjects.logging.tables.LogEntry"/>
>>         <entry
>> key="com.oobjects.logging.tables.IPathWalker.implementation"
>> value="com.oobjects.logging.tables.PathWalker"/>
>>     </jaxws:properties>
>>     <jaxws:serviceFactory>
>>         <ref bean="serviceFactory" />
>>     </jaxws:serviceFactory>
>> </jaxws:endpoint>
>>
>> This hasn't worked though.  I'm still getting proxy objects though. 
>> Anyone
>> out there got any ideas on how I can add these implementing classes?
>>   
> 
> 
> -- 
> Dan Diephouse
> MuleSource
> http://mulesource.com | http://netzooid.com/blog
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Aegis%2C-Proxies---Interfaces-tf4297824.html#a12458267
Sent from the cxf-user mailing list archive at Nabble.com.

Re: Aegis, Proxies & Interfaces

[Dan Diephouse <da...@mulesource.com>]

Hi Lee,

Looks like we got ourselves a bug. I've implemented a fix for this which 
I'll commit today. To get this to work you can either wait for us to 
publish a new snapshot (this weekend? we really need to automate this), 
build CXF yourself, or try the 2.0.2 release which will probably happen 
in two weeks.

Cheers,
- Dan

Lee Theobald wrote:
> A bit of a bump to this topic as I'm still having issues.  I'm trying things
> like below:
>
> <!-- Service endpoint -->
> <jaxws:endpoint id="searchlogger"
>     implementor="com.oobjects.logging.SearchLogger"
>     address="/SearchLogger">
>     <jaxws:properties>
>         <entry key="com.oobjects.logging.tables.ILogEntry.implementation"
> value="com.oobjects.logging.tables.LogEntry"/>
>         <entry
> key="com.oobjects.logging.tables.IPathWalker.implementation"
> value="com.oobjects.logging.tables.PathWalker"/>
>     </jaxws:properties>
>     <jaxws:serviceFactory>
>         <ref bean="serviceFactory" />
>     </jaxws:serviceFactory>
> </jaxws:endpoint>
>
> This hasn't worked though.  I'm still getting proxy objects though.  Anyone
> out there got any ideas on how I can add these implementing classes?
>   


-- 
Dan Diephouse
MuleSource
http://mulesource.com | http://netzooid.com/blog

Re: Aegis, Proxies & Interfaces

[Lee Theobald <Le...@openobjects.com>]

A bit of a bump to this topic as I'm still having issues.  I'm trying things
like below:

<!-- Service endpoint -->
<jaxws:endpoint id="searchlogger"
    implementor="com.oobjects.logging.SearchLogger"
    address="/SearchLogger">
    <jaxws:properties>
        <entry key="com.oobjects.logging.tables.ILogEntry.implementation"
value="com.oobjects.logging.tables.LogEntry"/>
        <entry
key="com.oobjects.logging.tables.IPathWalker.implementation"
value="com.oobjects.logging.tables.PathWalker"/>
    </jaxws:properties>
    <jaxws:serviceFactory>
        <ref bean="serviceFactory" />
    </jaxws:serviceFactory>
</jaxws:endpoint>

This hasn't worked though.  I'm still getting proxy objects though.  Anyone
out there got any ideas on how I can add these implementing classes?
-- 
View this message in context: http://www.nabble.com/Aegis%2C-Proxies---Interfaces-tf4297824.html#a12424129
Sent from the cxf-user mailing list archive at Nabble.com.