Its pretty good. My company uses it exclusively to
configure juniper routers.
Junoscript contains a subset of the "show command"
equivilent, that can be either a blessing or a curse
depending on what you are doing. parsing tags is a
lot easier than parsing non-xml'ed cli.
For configuration purposes, it rocks the house,
especially if you have to deal with other vendors cli.
You can not assume that JunoScript adheres to XML
Takes a little learning curve to figure out building
Debugging can be a pain because a lot of improperly
build tags will return "syntax error". but after a
while you get good at spotting bad tag building.
any junos command and pipe it to "display xml" is my
configuration locking, depends what you want to do,
it could be good, it could be bad.
junoscript overall will handle value validation when
you try to "commit" bad values.
What type of error handling do you seek?
Our stuff is mostly java, but i dont see what java
has to do with this. you can build tag in anything.
---- Jason Parsons <email@example.com>
wrote: > No responses here, so let's try broadening the
query. Is there anyone > with experience on JunOScript at all that would be
interested in > sharing their views? I'm specifically looking for
experiences with > error handling, configuration locking, and related
> Any issues you've encountered or tips would be
> Thank you.
> - Jason Parsons
> On Sunday, Sep 15, 2002, at 14:07 US/Eastern, Jason
Parsons wrote: > > Does anyone have experience talking to the JunOS
XML API with a Java > > client? I'm hoping someone would have sample
code and experiences > > they're willing to share.
> juniper-nsp mailing list firstname.lastname@example.org