Hello,

First off, this may just end up being a very noobish question, so please do 
excuse my utter lack of Java/Spring skills.

I’ve been using the Hackerbook’s Basic Cloudstack development section to get 
started with writing CloudStack plugins. I’ve managed to implement two basic 
endpoints - creating a coffee and listing coffees, with their Service classes. 
Unfortunately, while everything compiles just fine, the APIs themselves aren’t 
being registered by CloudStack. I’ve gone through the relevant sections in the 
Hackerbook about a dozen times, and checked if the new module is added to the 
CloudStack-plugins POM as well as the client POM, and I’ve also checked the 
plugin’s module properties and Spring loader module - everything seems as it 
should be. I’ve even removed all build artifacts and run clean builds, but it’s 
the same - whilst using the cs client to call the new endpoints, the client 
throws an exception stating the API discovery plugin was unable to find an API 
by that name.

Any tips/pointers here would be much appreciated! For context, you can find the 
code at https://github.com/rudimk/cloudstack, in the plugins/hackerbook/feature 
branch; the plugin itself resides at plugins/hackerbook/feature.

Thank you!


Best!

Rudraksh Mukta Kulshreshtha
Vice-President - DevOps & R&D
IndiQus Technologies
O +91 11 4055 1411 | M +91 99589 54879
indiqus.com

This message is intended only for the use of the individual or entity to which 
it is addressed and may contain information that is confidential and/or 
privileged. If you are not the intended recipient please delete the original 
message and any copy of it from your computer system. You are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited unless proper authorization has been obtained for such 
action. If you have received this communication in error, please notify the 
sender immediately. Although IndiQus attempts to sweep e-mail and attachments 
for viruses, it does not guarantee that both are virus-free and accepts no 
liability for any damage sustained as a result of viruses.

Reply via email to