RHQ Java Client libraries question
John Sanda
jsanda at redhat.com
Sat Sep 10 01:23:35 UTC 2011
The web services interface is not well supported. In fact there are APIs
that have been added to the Java remote APIs that have not been added to
the web services APIs. There has been some work started on a REST
interface, but that is not fully developed. I believe it is not yet in
master. I would stick with the remote Java APIs at least for the time being.
We do make an effort to remain backwards compatible to the greatest
extent possible especially for minor releases. Can you provide examples
of the errors you are hitting?
- John
On 9/9/11 8:31 PM, Steven North wrote:
> Hi,
>
> We currently have a separate tool that connects to the RHQ server to get
> resource information and snapshots. We use the RHQ Java Client
> "interface" and bind our Java tool with the RHQ Java Client libraries.
> That was working fine while we developed on RHQ 4.0 and 4.0.1, but now
> that we are testing against an RHQ 4.1 server we can't seem to connect
> with the 4.0 client libraries. The documentation clearly warns us that
> we should use matching versions of the client libraries. ;-)
>
> We are trying to plot our course forward in terms of how we build
> versions of our tool. One way is to build different versions of our
> tool with different sets of libraries. Or we could try to include both
> (or all) sets of libraries and choose the right one (somehow). Or we
> can require users to point us to the right set of libraries. All those
> options seem to have pitfalls.
>
> Would it be better for us to switch to the Webservices interface? Would
> that give us better immunity to version changes? Or are there the same
> issues?
>
> Thoughts?
>
> Thanks in advance,
>
> Steve
>
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/rhq-devel
More information about the rhq-devel
mailing list