[JBoss JIRA] (AS7-6004) Inconsistent tab completion behaviour between commands and arguments
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/AS7-6004?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil commented on AS7-6004:
----------------------------------
Using the CLI on the master branch after Aesh 0.26 has been integrated, I don't see the expected fix:
{noformat}
[standalone@localhost:9999 /] deployment-overlay a<CURSOR><TAB>
=> autocompletes to ./deployment-overlay add<CURSOR>
and not the expected ./deployment-overlay add<WHITESPACE><CURSOR>
{noformat}
Beside, I think we have some regressions wrt to completions:
{noformat}
[standalone@localhost:9999 /] ./deployment-<CURSOR><TAB>
=> this does not autocomplete to ./deployment-overlay=<CURSOR>
while
[standalone@localhost:9999 /] ./deployment-o<CURSOR><TAB>
=> *does* autocomplete to ./deployment-overlay=<CURSOR>
{noformat}
I am not sure this was the observed behaviour before Aesh 0.26
> Inconsistent tab completion behaviour between commands and arguments
> --------------------------------------------------------------------
>
> Key: AS7-6004
> URL: https://issues.jboss.org/browse/AS7-6004
> Project: Application Server 7
> Issue Type: Bug
> Components: CLI
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Minor
>
> When tab is used for completion, the behavior changes when there is only 1 remaining candidate.
> For commands, when the completion leads to a single candidate, a whitespace is appended and we can proceed to the arguments
> For arguments using a TabCompleter, when the completion leads to a single candidate, no whitespace is appended and we have to type it to be able to proceed to the next argument
>
> Example:
> * deployment-over<TAB>
> => will complete to deployment-overlay<WHITESPACE><CURSOR> (a whitespace is appended to the single candidate)
> * deployment-overlay a<TAB>
> => will complete to deployment-overlay add<CURSOR> (no whitespace appended even though add is the only candidate matched)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-6109) JndiPermission to secure access to naming
by Lukas Krejci (JIRA)
[ https://issues.jboss.org/browse/AS7-6109?page=com.atlassian.jira.plugin.s... ]
Lukas Krejci updated AS7-6109:
------------------------------
Git Pull Request: (was: https://github.com/jbossas/jboss-as/pull/3596)
> JndiPermission to secure access to naming
> -----------------------------------------
>
> Key: AS7-6109
> URL: https://issues.jboss.org/browse/AS7-6109
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Naming
> Affects Versions: 7.1.1.Final
> Reporter: Lukas Krejci
> Assignee: Eduardo Martins
>
> The naming subsystem defines the JndiPermission permission class that gives the impression that it could be potentially used to secure the access to various parts of the JNDI tree. This is not true though because that permission is not enforced.
> (It is enforced in the InMemoryNamingStore but that implementation of the naming store is not used inside a running AS7 instance (it seems to be a default for testing purposes).
> Having this ability would greatly simplify the situation where some application (like RHQ/JBoss ON) allows user-defined scripts to be executed in a running server but wants to restrict access to JNDI tree to those scripts (so that the scripts for example cannot access the database by looking up the datasource and thus circumvent any authz within the application that was given to the scripts).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-6109) JndiPermission to secure access to naming
by Lukas Krejci (JIRA)
Lukas Krejci created AS7-6109:
---------------------------------
Summary: JndiPermission to secure access to naming
Key: AS7-6109
URL: https://issues.jboss.org/browse/AS7-6109
Project: Application Server 7
Issue Type: Feature Request
Components: Naming
Affects Versions: 7.1.1.Final
Reporter: Lukas Krejci
Assignee: Eduardo Martins
The naming subsystem defines the JndiPermission permission class that gives the impression that it could be potentially used to secure the access to various parts of the JNDI tree. This is not true though because that permission is not enforced.
(It is enforced in the InMemoryNamingStore but that implementation of the naming store is not used inside a running AS7 instance (it seems to be a default for testing purposes).
Having this ability would greatly simplify the situation where some application (like RHQ/JBoss ON) allows user-defined scripts to be executed in a running server but wants to restrict access to JNDI tree to those scripts (so that the scripts for example cannot access the database by looking up the datasource and thus circumvent any authz within the application that was given to the scripts).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5476) Complete support for OSGi JPA
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-5476?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler commented on AS7-5476:
-------------------------------------
The idea is that [osgi/integration/jpa|https://github.com/jbossas/jboss-as/tree/master/osgi...] is the JPA Provider. i.e. AS provides the services that can be used by a persistence bundle.
You could start with the items above top to bottom. It should be relatively easy to add EntityManagerFactory service properties and add corresponding test coverage. As we go along we both get a better understanding of the JPA integration. David is working on the TCK setup - when this is done we get additional test coverage.
> Complete support for OSGi JPA
> -----------------------------
>
> Key: AS7-5476
> URL: https://issues.jboss.org/browse/AS7-5476
> Project: Application Server 7
> Issue Type: Feature Request
> Components: JPA / Hibernate, OSGi
> Reporter: Thomas Diesler
> Assignee: Scott Marlow
> Fix For: 7.2.0.CR1
>
>
> h6. 127.3.1 Services
> _Entity Manager Factory Builder service_ - The Entity Manager Factory Builder service provides the capability of creating an EntityManagerFactory object with additional configuration properties
> Add EntityManagerFactory service properties
> * osgi.unit.name - The name of the Persistence Unit (done)
> * osgi.unit.version - The version of the associated Persistence Bundle
> * osgi.unit.provider - The implementation class name of the JPA Provider
> h6. 127.3.4 Custom Configured Entity Manager
> If a Client Bundle needs to provide configuration properties for the creation of an Entity Manager Factory it should use the Entity Manager Factory Builder service. This can for example be used to provide the database selection properties when the Persistence Unit is incomplete or if the database selection needs to be overridden.
> Once an Entity Manager Factory is created the specified Data Source becomes associated with the Entity Manager Factory. It is therefore not possible to re-associate an Entity Manager Factory with another Data Source by providing different properties. A JPA Provider must throw an Exception when an attempt is made to re-specify the database properties.
> h6. 127.4.2 Meta Persistence Header
> Support non-default persistence descriptors through the Meta-Persistence header
> For example: _Meta-Persistence: META-INF/jpa.xml, persistence/jpa.xml_
> h6. 127.4.3 Processing
> The JPA Provider must validate the Persistence Bundle. A valid Persistence Bundle must:
> * Have no parsing errors of the Persistence Descriptors
> * Validate all Persistence Descriptors against their schemas
> * Have at least one assigned Persistence Unit
> * Have all entity classes mentioned in the assigned Persistence Units on the Persistence Bundles JAR.
> If any validation fails, then this is an error and should be logged. Such a bundle is ignored completely even if it also contains valid assigned Persistence Units. Only a bundle update can recover from this
> state.
> h6. 127.4.8 Stopping
> If a Persistence Bundle is being stopped, then the JPA Provider must ensure that any resources allocated on behalf of the Persistence Bundle are cleaned up and all open connections are closed. This cleanup must happen synchronously with the STOPPING event. Any Exceptions being thrown while cleaning up should be logged but must not stop any further clean up.
> If the JPA Provider is being stopped, the JPA Provider must unregister all JPA Services that it registered through the Persistence Bundles and clean up as if those bundles were stopped.
> h6. 127.5.3 Data Source Factory Service Matching
> Providers must use the javax.persistence.jdbc.driver property, as defined in JDBC Access in JPA on page 406, to obtain a Data Source Factory service. The Data Source Factory is specified in JDBC Service Specification on page 375. The javax.persistence.jdbc.driver property must be matched with the value of the Data Source Factory service property named osgi.jdbc.driver.class.
> h6. 127.5.4 Rebinding
> In this specification, the Entity Manager Factory service is only registered when the Persistence Unit is complete and a matching Data Source Factory service is available. However, the API of the Entity
> Manager Factory allows the creation of an Entity Manager with configuration properties. Those configuration properties could contain the JDBC properties to bind to another Data Source Factory service than it had already selected.
> This case must not be supported by a JPA Provider, an Illegal Argument Exception must be thrown.
> h6. 127.6 Static Access
> A Static Persistence Bundle must provide static access from the Persistence class to the JPA Services.
> This issue is complete when the TCK passes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-3694) Allow management client to associate metadata with DeploymentUnit
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-3694?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler updated AS7-3694:
--------------------------------
Fix Version/s: 7.2.0.CR1
(was: 7.2.0.Alpha1)
> Allow management client to associate metadata with DeploymentUnit
> -----------------------------------------------------------------
>
> Key: AS7-3694
> URL: https://issues.jboss.org/browse/AS7-3694
> Project: Application Server 7
> Issue Type: Feature Request
> Components: OSGi, Server
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Priority: Critical
> Fix For: 7.2.0.CR1
>
>
> Currently there is no way to pass some metadata through the deployment API such that they could show up with the DU.
> As a client I'd like to say autostart=false and in my DUP I'd like to pick that up and not start a deployment (i.e. a bundle) automatically
> Generally it should be possible for the client to set some properties for the deployment in a generic way such that they get associated with the DeploymentUnit
> For an OSGi deployment it would be necessary to be able to define that start behaviour and the start level.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-4292) Invalid bundle deployment does not fail in domain
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-4292?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler commented on AS7-4292:
-------------------------------------
Waiting on [#3230|https://github.com/jbossas/jboss-as/pull/3230]
> Invalid bundle deployment does not fail in domain
> -------------------------------------------------
>
> Key: AS7-4292
> URL: https://issues.jboss.org/browse/AS7-4292
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, OSGi
> Reporter: Thomas Diesler
> Priority: Minor
> Fix For: 7.2.0.CR1
>
>
> Running org.jboss.as.test.integration.domain.suites.OSGiBundleLifecyleTestCase
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 35.653 sec <<< FAILURE!
> on the server I see
> {code}
> 15:20:28,619 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit.bad-bundle.STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit.bad-bundle.STRUCTURE: Failed to process phase STRUCTURE of deployment "bad-bundle"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29]
> Caused by: java.lang.NumberFormatException: For input string: "bogus"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) [rt.jar:1.6.0_29]
> at java.lang.Integer.parseInt(Integer.java:449) [rt.jar:1.6.0_29]
> at java.lang.Integer.parseInt(Integer.java:499) [rt.jar:1.6.0_29]
> at org.osgi.framework.Version.<init>(Version.java:125)
> at org.osgi.framework.Version.parseVersion(Version.java:218)
> at org.jboss.osgi.spi.BundleInfo.validateBundleManifest(BundleInfo.java:204)
> at org.jboss.osgi.spi.BundleInfo.isValidBundleManifest(BundleInfo.java:153)
> at org.jboss.as.osgi.deployment.OSGiManifestStructureProcessor.deploy(OSGiManifestStructureProcessor.java:63)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5948) Bundle undeploy does not remove storage state
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-5948?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler updated AS7-5948:
--------------------------------
Fix Version/s: 7.2.0.Alpha1
> Bundle undeploy does not remove storage state
> ---------------------------------------------
>
> Key: AS7-5948
> URL: https://issues.jboss.org/browse/AS7-5948
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: 7.2.0.Alpha1
>
>
> {code}
> 08:44:19,541 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=53,rev=0,startlevel=1,started=true,location=test-bundle]
> 08:44:19,542 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=45,rev=0,startlevel=1,started=true,location=auto-start]
> 08:44:19,543 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=15,rev=0,startlevel=1,started=true,location=test-bundle]
> 08:44:19,544 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=59,rev=0,startlevel=1,started=true,location=static-logservice]
> 08:44:19,545 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=76,rev=0,startlevel=1,started=true,location=osgi-ws-test]
> 08:44:19,545 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=42,rev=0,startlevel=1,started=true,location=bundle-c.wab]
> 08:44:19,546 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=111,rev=0,startlevel=1,started=true,location=deferred-bundle-a.jar]
> 08:44:19,546 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=105,rev=0,startlevel=1,started=true,location=deferred-bundle-b.jar]
> 08:44:19,549 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=73,rev=0,startlevel=1,started=false,location=org.jboss.netty:main]
> 08:44:19,549 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=32,rev=0,startlevel=1,started=true,location=complex-cdi.jar]
> 08:44:19,550 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=63,rev=0,startlevel=1,started=true,location=nested-bundle.jar]
> 08:44:19,550 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=39,rev=0,startlevel=1,started=true,location=osgi-rest-test]
> 08:44:19,551 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=79,rev=0,startlevel=1,started=true,location=bundle-c.wab]
> 08:44:19,551 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=93,rev=0,startlevel=1,started=true,location=bundle-d.wab]
> 08:44:19,552 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=94,rev=0,startlevel=1,started=true,location=bundle-e.jar]
> 08:44:19,552 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=12,rev=3,startlevel=1,started=true,location=org.jboss.osgi.logging]
> 08:44:19,553 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=104,rev=0,startlevel=1,started=true,location=deferred-bundle-a.jar]
> 08:44:19,553 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=50,rev=0,startlevel=1,started=true,location=ejb3-osgi.jar]
> 08:44:19,554 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=121,rev=0,startlevel=1,started=false,location=version-range-a]
> 08:44:19,554 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=23,rev=0,startlevel=1,started=true,location=optional-import-a]
> 08:44:19,555 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=116,rev=0,startlevel=1,started=true,location=startlevel-testcase]
> 08:44:19,555 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=80,rev=0,startlevel=1,started=true,location=bundle-c.wab]
> 08:44:19,556 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=83,rev=0,startlevel=1,started=true,location=osgi-ear-test]
> 08:44:19,556 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=127,rev=0,startlevel=1,started=true,location=osgi-configadmin-tests]
> 08:44:19,557 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=30,rev=0,startlevel=1,started=true,location=osgi-cdi-test]
> 08:44:19,558 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=57,rev=0,startlevel=1,started=true,location=deploymentmarker-bundle-b]
> 08:44:19,559 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=36,rev=0,startlevel=1,started=true,location=ejb3-bundle-a.jar]
> 08:44:19,559 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=66,rev=0,startlevel=1,started=false,location=test-bundle]
> 08:44:19,560 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=129,rev=0,startlevel=1,started=true,location=config-admin-pid-b]
> 08:44:19,560 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=86,rev=0,startlevel=1,started=true,location=xpath-test.jar]
> 08:44:19,561 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=51,rev=0,startlevel=1,started=true,location=legacy-bundle]
> 08:44:19,561 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=71,rev=0,startlevel=1,started=true,location=org.apache.felix.eventadmin]
> 08:44:19,562 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=88,rev=0,startlevel=1,started=true,location=osgi-webapp-test]
> 08:44:19,562 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=34,rev=0,startlevel=1,started=true,location=visa-bundle.jar]
> 08:44:19,563 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=108,rev=0,startlevel=1,started=true,location=deferred-bundle-a.jar]
> 08:44:19,564 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=97,rev=0,startlevel=1,started=true,location=good-bundle.jar]
> 08:44:19,564 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=13,rev=3,startlevel=1,started=true,location=org.apache.felix.configadmin]
> 08:44:19,565 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=46,rev=0,startlevel=1,started=true,location=redeploy]
> 08:44:19,565 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=14,rev=3,startlevel=1,started=true,location=org.jboss.as.osgi.configadmin]
> 08:44:19,566 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=92,rev=0,startlevel=1,started=true,location=bundle-c.wab]
> 08:44:19,566 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=112,rev=0,startlevel=1,started=true,location=deferred-bundle-b.jar]
> 08:44:19,566 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=135,rev=0,startlevel=1,started=true,location=bundle-deployment-casetwo]
> 08:44:19,567 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=77,rev=0,startlevel=1,started=true,location=bundle-a.war]
> 08:44:19,567 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=123,rev=0,startlevel=1,started=true,location=example-bundle]
> 08:44:19,568 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=122,rev=0,startlevel=1,started=true,location=version-range-c]
> 08:44:19,568 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=16,rev=0,startlevel=1,started=false,location=test-fragment]
> 08:44:19,568 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=40,rev=0,startlevel=1,started=true,location=bundle-a.war]
> 08:44:19,569 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=140,rev=0,startlevel=1,started=true,location=simple-bundle.wab]
> 08:44:19,569 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=28,rev=0,startlevel=1,started=false,location=arquillian-deployer-test-bundle]
> 08:44:19,570 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=27,rev=0,startlevel=1,started=true,location=example-arquillian-deployer]
> 08:44:19,570 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=126,rev=0,startlevel=1,started=true,location=example-xservice-bam-client-bundle]
> 08:44:19,571 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=37,rev=0,startlevel=1,started=true,location=ejb3-bundle-a.jar]
> 08:44:19,571 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=98,rev=0,startlevel=2,started=true,location=good-bundle.jar]
> 08:44:19,572 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=141,rev=0,startlevel=1,started=true,location=updated-bundle.wab]
> 08:44:19,572 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=68,rev=0,startlevel=1,started=true,location=persistence-bundle-a.jar]
> 08:44:19,573 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=87,rev=0,startlevel=1,started=true,location=example-jaxb]
> 08:44:19,573 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=113,rev=0,startlevel=1,started=true,location=dynamic-logservice]
> 08:44:19,574 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=136,rev=0,startlevel=1,started=false,location=test-bundle-two]
> 08:44:19,574 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=74,rev=0,startlevel=1,started=true,location=org.projectodd.stilts:main]
> 08:44:19,574 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=38,rev=0,startlevel=1,started=true,location=bundle-a.wab]
> 08:44:19,575 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=107,rev=0,startlevel=1,started=true,location=deferred-bundle-b.jar]
> 08:44:19,575 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=41,rev=0,startlevel=1,started=true,location=bundle-b.war]
> 08:44:19,576 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=47,rev=0,startlevel=1,started=true,location=redeploy]
> 08:44:19,576 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=25,rev=0,startlevel=1,started=true,location=optional-import-a]
> 08:44:19,577 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=55,rev=0,startlevel=2,started=true,location=deploymentmarker-bundle-c]
> 08:44:19,577 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=70,rev=0,startlevel=1,started=true,location=osgi-repository-bundle]
> 08:44:19,578 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=33,rev=0,startlevel=1,started=true,location=paypal-bundle.jar]
> 08:44:19,578 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=43,rev=0,startlevel=1,started=true,location=bundle-c.wab]
> 08:44:19,579 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=103,rev=0,startlevel=1,started=true,location=bad-bundle.jar]
> 08:44:19,579 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=110,rev=0,startlevel=1,started=true,location=good-bundle.jar]
> 08:44:19,580 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=133,rev=0,startlevel=1,started=true,location=example-xservice-mab-target-bundle]
> 08:44:19,580 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=137,rev=0,startlevel=1,started=true,location=osgi-bundlecontext-test]
> 08:44:19,581 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=62,rev=0,startlevel=1,started=true,location=example-jta]
> 08:44:19,581 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=72,rev=0,startlevel=1,started=true,location=stomplet-server-provider]
> 08:44:19,582 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=22,rev=0,startlevel=1,started=true,location=optional-import-a]
> 08:44:19,582 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=75,rev=0,startlevel=1,started=true,location=simple-stomplet]
> 08:44:19,583 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=95,rev=0,startlevel=1,started=true,location=sax-parser.jar]
> 08:44:19,584 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=20,rev=0,startlevel=1,started=true,location=optional-import-a]
> 08:44:19,584 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=65,rev=0,startlevel=1,started=true,location=bundle-deployment-case-one]
> 08:44:19,585 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=128,rev=0,startlevel=1,started=true,location=config-admin-pid-a]
> 08:44:19,585 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=102,rev=0,startlevel=2,started=true,location=bad-bundle.jar]
> 08:44:19,586 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=106,rev=0,startlevel=1,started=true,location=deferred-bundle-a.jar]
> 08:44:19,586 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=35,rev=0,startlevel=1,started=true,location=osgi-ejb3-test]
> 08:44:19,587 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=100,rev=0,startlevel=1,started=true,location=bad-bundle.jar]
> 08:44:19,588 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=96,rev=0,startlevel=1,started=true,location=deferred-resolve-tests]
> 08:44:19,588 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=60,rev=0,startlevel=1,started=true,location=bundleA]
> 08:44:19,589 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=90,rev=0,startlevel=1,started=true,location=bundle-a.war]
> 08:44:19,589 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=21,rev=0,startlevel=1,started=true,location=optional-import-b]
> 08:44:19,590 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=58,rev=0,startlevel=1,started=true,location=example-jndi]
> 08:44:19,591 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=85,rev=0,startlevel=1,started=true,location=war-structure-bundle.war]
> 08:44:19,591 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=24,rev=0,startlevel=1,started=false,location=optional-import-b]
> 08:44:19,592 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=132,rev=0,startlevel=1,started=true,location=xservice-module-access]
> 08:44:19,592 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=131,rev=0,startlevel=1,started=true,location=config-admin-bundle-b]
> 08:44:19,593 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=119,rev=0,startlevel=1,started=false,location=version-range-a]
> 08:44:19,593 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=11,rev=3,startlevel=1,started=true,location=org.apache.felix.log]
> 08:44:19,594 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=48,rev=0,startlevel=1,started=true,location=simple-client.jar]
> 08:44:19,594 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=81,rev=0,startlevel=1,started=false,location=resource-injection.jar]
> 08:44:19,595 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=52,rev=0,startlevel=1,started=true,location=http-service-example]
> 08:44:19,596 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=64,rev=0,startlevel=1,started=true,location=arq466-bundle]
> 08:44:19,596 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=117,rev=0,startlevel=3,started=true,location=osgi-startlevel-a]
> 08:44:19,597 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=101,rev=0,startlevel=1,started=true,location=bad-bundle.jar]
> 08:44:19,598 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=0,rev=0,startlevel=0,started=false,location=System Bundle]
> 08:44:19,598 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=69,rev=0,startlevel=1,started=true,location=persistence-bundle-a.jar]
> 08:44:19,599 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=99,rev=0,startlevel=1,started=true,location=good-bundle.jar]
> 08:44:19,599 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=89,rev=0,startlevel=1,started=true,location=bundle-c.wab]
> 08:44:19,600 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=115,rev=0,startlevel=1,started=true,location=ejb-client-descriptor-bundle.jar]
> 08:44:19,601 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=114,rev=0,startlevel=1,started=true,location=bundleA]
> 08:44:19,601 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=124,rev=0,startlevel=1,started=true,location=xservice-module-access]
> 08:44:19,602 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=49,rev=0,startlevel=1,started=true,location=ejb3-osgi-target]
> 08:44:19,603 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=84,rev=0,startlevel=1,started=true,location=echo-bundle.jar]
> 08:44:19,603 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=67,rev=0,startlevel=1,started=true,location=osgi-jpa-test]
> 08:44:19,604 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=78,rev=0,startlevel=1,started=true,location=bundle-b.war]
> 08:44:19,604 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=120,rev=0,startlevel=1,started=true,location=version-range-b]
> 08:44:19,605 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=130,rev=0,startlevel=1,started=true,location=config-admin-pid-c]
> 08:44:19,605 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=44,rev=0,startlevel=1,started=true,location=example-bundle]
> 08:44:19,606 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=61,rev=0,startlevel=1,started=true,location=osgi-configadmin]
> 08:44:19,607 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=29,rev=0,startlevel=1,started=true,location=dom-parser.jar]
> 08:44:19,607 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=56,rev=0,startlevel=1,started=true,location=deploymentmarker-bundle-a]
> 08:44:19,608 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=91,rev=0,startlevel=1,started=true,location=bundle-b.war]
> 08:44:19,608 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=17,rev=0,startlevel=1,started=true,location=test-bundle2]
> 08:44:19,609 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=109,rev=0,startlevel=1,started=true,location=deferred-bundle-b.jar]
> 08:44:19,610 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=54,rev=0,startlevel=1,started=true,location=deploymentmarker-tests]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months