Rechercher

Question
· Oct 30, 2024

Sonatype Nexus as IPM repository?

It's not supported at the moment but is it possible to implement the Sonatype Nexus (or JFrog Artifactory) support based on the current (or upcoming) IPM version?

In repo command help I see there is a support for filesystem repositories (which I have not yet tried) and my current (hopefully not far-fetched) interpretation is the IPM is designed to be able to support different repositories:

zpm:IPMTEST1>help repo
[...]
  ■ Filesystem repository:
    ∙ -filesystem, -f, -fs : Create/update a filesystem repository
    ∙ -depth, -d <value> : For filesystem repositories, specifies the depth (number of folders underneath the root) to search for files named module.xml
    ∙ -path, -p <value> : For filesystem repositories, specifies the path to the root directory
[...]
  ■ Examples
    ∙ repo -name LocalFiles -snapshots 1 -fs -depth 2 -path C:\MyWorkspace\RootModuleDir\
      Create a repository pointing to the filesystem with name LocalFiles, accepting snapshots, looking for files named module.xml up to 2 directories deep in C:\MyWorkspace\RootModuleDir\

The motivation: we already have a repository implementation used for Java and Docker builds and we would like to reuse that instead introducing a new component. I believe we're not the only ones here with this setup.

5 Comments
Discussion (5)4
Connectez-vous ou inscrivez-vous pour continuer
Article
· Oct 30, 2024 10m de lecture

Production IRIS pilotée par une base de données avec des adaptateurs entrants personnalisés

L'utilisation traditionnelle d'une production IRIS consiste, pour un adaptateur entrant, à recevoir des données d'une source externe, à envoyer ces données à un service IRIS, puis à faire en sorte que ce service envoie ces données par l'intermédiaire de la production.

Discussion (0)2
Connectez-vous ou inscrivez-vous pour continuer
Question
· Oct 30, 2024

IPM package command failure: <VALUE OUT OF RANGE>zConstructTar+19^%ZPM.Utils.FileBinaryTar.1

I'm trying package IPM command but I'm getting the following error:

zpm:IPMTEST1>package -verbose -only -path /home/irisowner/ osex-ipm-hello

[IPMTEST1|osex-ipm-hello]       Package START
Exporting 'OSEX.ipm.hello.Hello.cls' to '/home/irisowner/src/OSEX/ipm/hello/Hello.cls'
Exported to /home/irisowner/module.xml
Module exported to:
        /home/irisowner/

[osex-ipm-hello]        Package FAILURE
ERROR! ObjectScript error: <VALUE OUT OF RANGE>zConstructTar+19^%ZPM.Utils.FileBinaryTar.1

What's wrong here?

I can see all the correct module files created:

$ pwd
/home/irisowner
$ ll module.xml src/OSEX/ipm/hello/Hello.cls
-rwxr-xr-x 1 irisowner irisowner 494 Oct 30 09:12 module.xml*
-rwxr-xr-x 1 irisowner irisowner 111 Oct 30 09:12 src/OSEX/ipm/hel

I'm running:

zpm:IPMTEST1>version

%SYS>     zpm          0.7.3
IPMTEST1> zpm-registry 1.3.2
https://pm.community.intersystems.com - 1.0.6
http://localhost:52773/registry/ - 1.3.2
2 Comments
Discussion (2)1
Connectez-vous ou inscrivez-vous pour continuer
Question
· Oct 30, 2024

Running a routine by name in a non-conventional way?

So I know we can run routines using both XECUTE or @ 
However both of them run slower than just running the routine without it. (that is because as far as i understand, XECUTE command for example will re-compile before running?)

the question is: how can I run a routine by name - and keeping the performance as good as possible?

1 Comment
Discussion (1)2
Connectez-vous ou inscrivez-vous pour continuer
Question
· Oct 29, 2024

dynaTree doesn't expand completely

Hi Guys,

I'm calling the expandAll() method to expand the whole tree structure but for some reason its only expanding the root folders but not all elements under those folders ?

var tree zenPage.getComponentById( "MyTree");
tree.expandAll(true);
 

 

Thanks

3 Comments
Discussion (3)2
Connectez-vous ou inscrivez-vous pour continuer