Guten Tag Andrew DeFaria,
am Mittwoch, 26. März 2014 um 19:50 schrieben Sie:
> Name a way then.
I did and you already know some.
> However when I say
> Bugzilla::Webservice::Bug I cannot do cpan Bugzilla::Webservice::Bug
> and get code because cpan says it can't find anything listed under
> Bugzilla::Webservice::Bug. Now I know that it's not part of CPAN so
> what is it part of and how do I get the code?
It's a web service API implementing XML-RPC and JSON-RPC, use it
with which ever client you want. BZ::Client is one possible way, but
you can use others as well, XML::RPC for example.
http://www.bugzilla.org/docs/4.4/en/html/api/Bugzilla/WebService.html
http://search.cpan.org/~daan/XML-RPC-0.9/lib/XML/RPC.pm
Because it's a serve side API and doesn't provide any client side
code. I provided the link because I thought you are using it as an
entry point to read the docs for the API.
> Not exactly a bastion of functionality! The Wiki could anticipate
> that I might need a bit more functionality for any functional use
> case! Just my opinion of course :-).
The wiki'S purpose is to provide pointers to tools or solutions, no
documentation on how to use those.
> It looked like you were telling me that BZ::Client was not an
> official project and that I shouldn't be using it.
I didn't tell you not to use it, I just gave a hint that this is the
support mailing list for Bugzilla and not BZ::Client, therefore it's
less likely you will get help for very specific questions like your
regarding BZ::Client. Of course there are some devs around Bugzilla
reading and answering on this list and some may use BZ::Client as
well, but that doesn't change anything regarding that it's more likely
to get your kind of support from the original project.
> It's just I thought there
> would be some sort of official or at least full featured way to
> access the functionality of Bugzilla from scripts,
There's a documented web service API describing the functionality
available for remote clients, which is not everything Bugzilla is able
to do, but the most important and most frequently requested parts.
Patches welcome of course! ;-)
Besides that and depending on your use case, if you don't need remote
client access you have some additional choices like accessing Bugzilla
natively using it's native "full featured" API and even this can be
done with different ways.
> specifically Perl
> scripts as from what I can tell Bugzilla is largely written in Perl.
> And as it is quite old in Internet terms I find it surprising there
> isn't a full featured Perl module that everybody's using already.
But that's the way it is, simply a matter of resources and other
peoples use cases.
> I see this Bugzilla::Webservice::Bug but have no idea on how to download the code.
There's nothing to download, you need to implement or use a web
service client with the help of a lib of your choice in a language of
your choice.
> I also see this BzAPI thing but it appears to be server side only.
BzAPI is a server side REST API to be able to access Bugzilla remotely
by clients using a REST API instead of XML-RPC or JSON-RPC, which is
what Bugzilla only supports oob. So yes, BzAPI is server side in terms
of installation/administration, but can be used remotely by clients
because it provides a REST service. An no, you can't download code for
BzAPI clients as well, you need to choose how and with what etc. you
want to implement your own REST client capable of using BzAPI.
> One thing I'm trying to accomplish: We have a number of saved
> searches. One process we have here executes a number of these and
> saves the results to .csv files. This is done manually through the
> web UI.
Which is not uncommon, there are quite some tutorials and stuff out
there just automating the web ui for specific tasks.
> Another Perl script gathers a bunch of these .csv files and
> produces another .csv file in the form of a report that is useful to
> management. I'd like to change this Perl process to simply
> interrogate the Bugzilla database directly, possibly utilizing the
> saved searches directly and produce the final .csv file directly (or
> perhaps make a web page instead). There are also many other scripts
> I could imagine Perl doing by having full functioned access to Bugzilla.
None of this sound like you need remote client access, but the logic
might as well run on the same server as Bugzilla does. If this is the
case you might want to access the native Bugzilla API, not the web
service API.
> I don't particularly care if it's WebServices or not. I just want
> to interact with the functionality of Bugzilla programmatically
> through Perl. The backend can be WebServices, client/server socket stuff or a direct API.
You need to care because it makes a huge difference if you are a
remote client or not and have access to the local Bugzilla
installation.
Web services are always something a server provides and a client
consumes, which doesn't necessarily say anything about where server
and client are situated, how they communicate etc.
> You make the incorrect assumption that 1) I understand enough about
> the code base to make contributions,
You should contribute to the docs, not the code, because the docs are
what you seem to think needs improvement.
> 2) I have that time and 3) I wish to work for free.
Others created Bugzilla or answer your mails for free. ;-)
> Not necessarily. Somebody else could have already implemented this
> or there may be another solution. That's why I'm posting here. I'm
> shocked that such a mature technology has such a lack of an interface, supported or not...
As I already said, not everyone has your use case.
> I see it as more of a matter of professionalism.
Calm down, you're throwing nonsense like "server side technology"
regarding the web service API, want to download code for or from it or
whatever and don't care how you can access Bugzilla, which is
essentially in knowing which interfaces are available to use. You
really shouldn't tell people here about professionalism if you don't
understand the technologies you want to use and ask for.
> I know that I
> would not release code, open source or not, unless it was not at
> least reasonably feature complete.
Feature complete for whom?
> There's never any good examples of real code, they
> often don't describe what data is returned other than to say that
> it's of XML or JSON format - how are multiple records indicated? How
> empty fields handled? Different field data types? How are exceptions
> handled? These questions are often not answered.
Bugzilla's docs answer most of those, if not all.