[JBoss JIRA] (ARTIF-675) Define new "service" model
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-675?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-675:
------------------------------
Description:
Define a new, generic model to better encapsulate "services", discovery, and re-use. Arguably, some of this should probably be added to the core, base model as well.
Ideas (from various sources):
- Provides a catalog of information, what services exist and are available for use
- Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc.
- Provides information about the version of the services
- Allows you to record and retrieve multiple versions of the same service
- Allows you to dynamically refer to the latest version of the service
- Allows dynamically at runtime to search and select end-point chosen service
- Collects information who and what services are used
- Provides information that services are repeatedly used and which are not
- Determining the impact of changes the services to existing dependent services
- Providing information to consumers of the services about ongoing or planned changes to of the services
- Identify the environments (OS, app server, etc.) supported by the artifact
- Differentiate between front and back end artifacts
- Security: what version of SSL is used, etc. (extremely valuable for security audits)
was:
Define a new, generic model to better encapsulate "services", discovery, and re-use.
Ideas (from various sources):
- Provides a catalog of information, what services exist and are available for use
- Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc.
- Provides information about the version of the services
- Allows you to record and retrieve multiple versions of the same service
- Allows you to dynamically refer to the latest version of the service
- Allows dynamically at runtime to search and select end-point chosen service
- Collects information who and what services are used
- Provides information that services are repeatedly used and which are not
- Determining the impact of changes the services to existing dependent services
- Providing information to consumers of the services about ongoing or planned changes to of the services
- Identify the environments (OS, app server, etc.) supported by the artifact
- Differentiate between front and back end artifacts
> Define new "service" model
> --------------------------
>
> Key: ARTIF-675
> URL: https://issues.jboss.org/browse/ARTIF-675
> Project: Artificer
> Issue Type: Feature Request
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> Define a new, generic model to better encapsulate "services", discovery, and re-use. Arguably, some of this should probably be added to the core, base model as well.
> Ideas (from various sources):
> - Provides a catalog of information, what services exist and are available for use
> - Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc.
> - Provides information about the version of the services
> - Allows you to record and retrieve multiple versions of the same service
> - Allows you to dynamically refer to the latest version of the service
> - Allows dynamically at runtime to search and select end-point chosen service
> - Collects information who and what services are used
> - Provides information that services are repeatedly used and which are not
> - Determining the impact of changes the services to existing dependent services
> - Providing information to consumers of the services about ongoing or planned changes to of the services
> - Identify the environments (OS, app server, etc.) supported by the artifact
> - Differentiate between front and back end artifacts
> - Security: what version of SSL is used, etc. (extremely valuable for security audits)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 1 month
[JBoss JIRA] (ARTIF-686) HTML/CSS/JS artifacts
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-686:
---------------------------------
Summary: HTML/CSS/JS artifacts
Key: ARTIF-686
URL: https://issues.jboss.org/browse/ARTIF-686
Project: Artificer
Issue Type: Feature Request
Reporter: Brett Meyer
Assignee: Brett Meyer
If an HTML/JSP/etc, CSS, or JS file is uploaded (or discovered during expansion), support with a new ArtifactBuilder and new derivation. Powerful examples:
1.) Which HTML files import the given CSS
2.) Which HTML *elements* utilize the given CSS *class*
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 1 month
[JBoss JIRA] (ARTIF-675) Define new "service" model
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-675?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-675:
------------------------------
Description:
Define a new, generic model to better encapsulate "services", discovery, and re-use.
Ideas (from various sources):
- Provides a catalog of information, what services exist and are available for use
- Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc.
- Provides information about the version of the services
- Allows you to record and retrieve multiple versions of the same service
- Allows you to dynamically refer to the latest version of the service
- Allows dynamically at runtime to search and select end-point chosen service
- Collects information who and what services are used
- Provides information that services are repeatedly used and which are not
- Determining the impact of changes the services to existing dependent services
- Providing information to consumers of the services about ongoing or planned changes to of the services
- Identify the environments (OS, app server, etc.) supported by the artifact
- Differentiate between front and back end artifacts
was:
Define a new, generic model to better encapsulate "services", discovery, and re-use.
Ideas (from various sources):
- Provides a catalog of information, what services exist and are available for use
- Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc.
- Provides information about the version of the services
- Allows you to record and retrieve multiple versions of the same service
- Allows you to dynamically refer to the latest version of the service
- Allows dynamically at runtime to search and select end-point chosen service
- Collects information who and what services are used
- Provides information that services are repeatedly used and which are not
- Determining the impact of changes the services to existing dependent services
- Providing information to consumers of the services about ongoing or planned changes to of the services
- Differentiate between
> Define new "service" model
> --------------------------
>
> Key: ARTIF-675
> URL: https://issues.jboss.org/browse/ARTIF-675
> Project: Artificer
> Issue Type: Feature Request
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> Define a new, generic model to better encapsulate "services", discovery, and re-use.
> Ideas (from various sources):
> - Provides a catalog of information, what services exist and are available for use
> - Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc.
> - Provides information about the version of the services
> - Allows you to record and retrieve multiple versions of the same service
> - Allows you to dynamically refer to the latest version of the service
> - Allows dynamically at runtime to search and select end-point chosen service
> - Collects information who and what services are used
> - Provides information that services are repeatedly used and which are not
> - Determining the impact of changes the services to existing dependent services
> - Providing information to consumers of the services about ongoing or planned changes to of the services
> - Identify the environments (OS, app server, etc.) supported by the artifact
> - Differentiate between front and back end artifacts
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 1 month
[JBoss JIRA] (ARTIF-675) Define new "service" model
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-675?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-675:
------------------------------
Description:
Define a new, generic model to better encapsulate "services", discovery, and re-use.
Ideas (from various sources):
- Provides a catalog of information, what services exist and are available for use
- Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc.
- Provides information about the version of the services
- Allows you to record and retrieve multiple versions of the same service
- Allows you to dynamically refer to the latest version of the service
- Allows dynamically at runtime to search and select end-point chosen service
- Collects information who and what services are used
- Provides information that services are repeatedly used and which are not
- Determining the impact of changes the services to existing dependent services
- Providing information to consumers of the services about ongoing or planned changes to of the services
- Differentiate between
was:
Define a new, generic model to better encapsulate "services", discovery, and re-use.
Ideas (from various sources):
- Provides a catalog of information, what services exist and are available for use
- Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc.
- Provides information about the version of the services
- Allows you to record and retrieve multiple versions of the same service
- Allows you to dynamically refer to the latest version of the service
- Allows dynamically at runtime to search and select end-point chosen service
- Collects information who and what services are used
- Provides information that services are repeatedly used and which are not
- Determining the impact of changes the services to existing dependent services
- Providing information to consumers of the services about ongoing or planned changes to of the services
> Define new "service" model
> --------------------------
>
> Key: ARTIF-675
> URL: https://issues.jboss.org/browse/ARTIF-675
> Project: Artificer
> Issue Type: Feature Request
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> Define a new, generic model to better encapsulate "services", discovery, and re-use.
> Ideas (from various sources):
> - Provides a catalog of information, what services exist and are available for use
> - Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc.
> - Provides information about the version of the services
> - Allows you to record and retrieve multiple versions of the same service
> - Allows you to dynamically refer to the latest version of the service
> - Allows dynamically at runtime to search and select end-point chosen service
> - Collects information who and what services are used
> - Provides information that services are repeatedly used and which are not
> - Determining the impact of changes the services to existing dependent services
> - Providing information to consumers of the services about ongoing or planned changes to of the services
> - Differentiate between
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 1 month
[JBoss JIRA] (OVERLORD-147) Use the maven-bundle-plugin in WAR projects (overlord-commons)
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/OVERLORD-147?page=com.atlassian.jira.plug... ]
Gary Brown updated OVERLORD-147:
--------------------------------
Fix Version/s: Overlord-Commons-2.0.14.Final
(was: Overlord-Commons-2.0.12.Fina)
> Use the maven-bundle-plugin in WAR projects (overlord-commons)
> --------------------------------------------------------------
>
> Key: OVERLORD-147
> URL: https://issues.jboss.org/browse/OVERLORD-147
> Project: Overlord
> Issue Type: Task
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: Overlord-Commons-2.0.14.Final
>
>
> Right now in our WAR projects we are using the war plugin to configure the manifest for osgi. Instead we should use the bundle plugin.
> Links:
> https://ops4j1.jira.com/wiki/display/paxweb/OSGi-fy+your+WAR
> https://ops4j1.jira.com/wiki/display/ops4j/Getting+the+benefits+of+maven-...
> Here is an example of using it in overlord-commons-idp:
> {code}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <parent>
> <groupId>org.overlord</groupId>
> <artifactId>overlord-commons</artifactId>
> <version>2.0.3-SNAPSHOT</version>
> </parent>
> <artifactId>overlord-commons-idp</artifactId>
> <packaging>war</packaging>
> <name>Overlord Commons: IDP</name>
> <description>An identity provider using PicketLink SAML.</description>
> <dependencies>
> <!-- Third Party Dependencies -->
> <dependency>
> <groupId>org.picketlink</groupId>
> <artifactId>picketlink-federation</artifactId>
> </dependency>
> <dependency>
> <groupId>org.picketbox</groupId>
> <artifactId>picketbox</artifactId>
> </dependency>
> <dependency>
> <groupId>org.picketlink</groupId>
> <artifactId>picketlink-federation</artifactId>
> </dependency>
> <dependency>
> <groupId>org.jboss.logging</groupId>
> <artifactId>jboss-logging</artifactId>
> </dependency>
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>overlord-commons-auth</artifactId>
> </dependency>
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>overlord-commons-auth-jboss7</artifactId>
> </dependency>
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>overlord-commons-auth-jetty8</artifactId>
> </dependency>
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>overlord-commons-auth-tomcat7</artifactId>
> </dependency>
> <!-- Provided Dependencies -->
> <dependency>
> <groupId>org.jboss.spec.javax.servlet</groupId>
> <artifactId>jboss-servlet-api_3.0_spec</artifactId>
> <scope>provided</scope>
> </dependency>
> </dependencies>
> <build>
> <plugins>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>build-helper-maven-plugin</artifactId>
> <executions>
> <execution>
> <id>regex-property</id>
> <goals>
> <goal>regex-property</goal>
> </goals>
> <configuration>
> <name>project.version.osgi</name>
> <value>${project.version}</value>
> <regex>-SNAPSHOT</regex>
> <replacement>.Snapshot</replacement>
> <failIfNoMatch>false</failIfNoMatch>
> </configuration>
> </execution>
> </executions>
> </plugin>
> <!-- <plugin> -->
> <!-- <artifactId>maven-war-plugin</artifactId> -->
> <!-- <configuration> -->
> <!-- <failOnMissingWebXml>false</failOnMissingWebXml> -->
> <!-- <warName>${project.artifactId}</warName> -->
> <!-- <attachClasses>true</attachClasses> -->
> <!-- <classesClassifier>classes</classesClassifier> -->
> <!-- <archive> -->
> <!-- <manifestEntries> -->
> <!-- <Bundle-ManifestVersion>2</Bundle-ManifestVersion> -->
> <!-- <Bundle-SymbolicName>${project.artifactId}</Bundle-SymbolicName> -->
> <!-- <Bundle-Version>${project.version.osgi}</Bundle-Version> -->
> <!-- <Web-ContextPath>/overlord-idp</Web-ContextPath> -->
> <!-- <Webapp-Context>/overlord-idp</Webapp-Context> -->
> <!-- <Import-Package>org.apache.log4j,javax.servlet, javax.servlet.http,javax.security.auth.login,javax.xml.stream,javax.xml.stream.events,javax.xml.namespace,javax.xml.transform,javax.xml.transform.dom,javax.xml.transform.stream,javax.xml.parsers,javax.xml.datatype,javax.xml.crypto,javax.xml.crypto.dsig,javax.xml.bind,org.apache.karaf.jaas.boot.principal,org.eclipse.jetty.plus.jaas,org.xml.sax,org.w3c.dom,org.w3c.dom.ls,org.overlord.commons.auth.util,org.picketlink.identity.federation.core.interfaces -->
> <!-- </Import-Package> -->
> <!-- <Bundle-ClassPath>.,WEB-INF/classes,WEB-INF/lib/commons-logging-${version.commons-logging}.jar,WEB-INF/lib/jboss-logging-${version.org.jboss.logging}.jar,WEB-INF/lib/jbossxacml-2.0.8.Final.jar,WEB-INF/lib/picketbox-${picketbox.version}.jar,WEB-INF/lib/picketlink-common-${picketlink.version}.jar,WEB-INF/lib/picketlink-config-${picketlink.version}.jar,WEB-INF/lib/picketlink-federation-${picketlink.version}.jar,WEB-INF/lib/picketlink-idm-api-${picketlink.version}.jar,WEB-INF/lib/picketlink-idm-impl-${picketlink.version}.jar,WEB-INF/lib/xmlsec-1.5.1.jar -->
> <!-- </Bundle-ClassPath> -->
> <!-- </manifestEntries> -->
> <!-- </archive> -->
> <!-- </configuration> -->
> <!-- </plugin> -->
> <plugin>
> <artifactId>maven-war-plugin</artifactId>
> <configuration>
> <archive>
> <!-- add the generated manifest to the war -->
> <manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile>
> </archive>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.felix</groupId>
> <artifactId>maven-bundle-plugin</artifactId>
> <executions>
> <execution>
> <id>bundle-manifest</id>
> <phase>process-classes</phase>
> <goals>
> <goal>manifest</goal>
> </goals>
> </execution>
> </executions>
> <configuration>
> <failOnMissingWebXml>false</failOnMissingWebXml> -->
> <warName>${project.artifactId}</warName>
> <attachClasses>true</attachClasses>
> <classesClassifier>classes</classesClassifier>
> <instructions>
> <Bundle-ManifestVersion>2</Bundle-ManifestVersion>
> <Bundle-SymbolicName>${project.artifactId}</Bundle-SymbolicName>
> <Bundle-Version>${project.version.osgi}</Bundle-Version>
> <Web-ContextPath>/overlord-idp</Web-ContextPath>
> <Webapp-Context>/overlord-idp</Webapp-Context>
> <Import-Package>org.apache.log4j,javax.servlet, javax.servlet.http,javax.security.auth.login,javax.xml.stream,javax.xml.stream.events,javax.xml.namespace,javax.xml.transform,javax.xml.transform.dom,javax.xml.transform.stream,javax.xml.parsers,javax.xml.datatype,javax.xml.crypto,javax.xml.crypto.dsig,javax.xml.bind,org.apache.karaf.jaas.boot.principal,org.eclipse.jetty.plus.jaas,org.xml.sax,org.w3c.dom,org.w3c.dom.ls,org.overlord.commons.auth.util,org.picketlink.identity.federation.core.interfaces
> </Import-Package>
> <Bundle-ClassPath>.,WEB-INF/classes,WEB-INF/lib/commons-logging-${version.commons-logging}.jar,WEB-INF/lib/jboss-logging-${version.org.jboss.logging}.jar,WEB-INF/lib/jbossxacml-2.0.8.Final.jar,WEB-INF/lib/picketbox-${picketbox.version}.jar,WEB-INF/lib/picketlink-common-${picketlink.version}.jar,WEB-INF/lib/picketlink-config-${picketlink.version}.jar,WEB-INF/lib/picketlink-federation-${picketlink.version}.jar,WEB-INF/lib/picketlink-idm-api-${picketlink.version}.jar,WEB-INF/lib/picketlink-idm-impl-${picketlink.version}.jar,WEB-INF/lib/xmlsec-1.5.1.jar
> </Bundle-ClassPath>
> </instructions>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </project>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 1 month