Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Actions not being generated #20

Open
hshorter opened this issue May 20, 2013 · 3 comments
Open

Actions not being generated #20

hshorter opened this issue May 20, 2013 · 3 comments

Comments

@hshorter
Copy link

Action elements in the Yang are not being generated into Java objects. I would expect an object for the Action input so these can be created and passed to session.action() and one for the output which this method would return.

The Yang looks like:

tailf:action backup {
tailf:info " Backs up Config database";
tailf:exec "/opt/database" {
tailf:args "-c $(context) -p $(path)";
}
input {
leaf to {
type inet:uri;
mandatory true;
description "Destination to which db backup file is sent";
tailf:info "Destination URL";
}
}
output {
list dbbackup {
tailf:cli-drop-node-name;
leaf response {
type string;
description "Response";
}
}
}
}

@joagre
Copy link

joagre commented May 23, 2013

AFAICS your current option is to create a plainc Element object and then use that as action input parameter. No classes are generated for actions at this time.

@hshorter
Copy link
Author

Yes using Elements would be a short term workaround we are looking at, but we need generated objects (like for standard containers etc) so that we can retain type safety and compile time errors if the model changes in an incompatible way.

@joagre
Copy link

joagre commented May 29, 2013

Hi,
This is a good enhancement request but at the moment it is not on the JNC
roadmap.

/Jocke

tail-f

28 maj 2013 kl. 17:06 skrev hshorter:

Yes using Elements would be a short term workaround we are looking at, but we need generated objects (like for standard containers etc) so that we can retain type safety and compile time errors if the model changes in an incompatible way.


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants