July 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-783) Cannot get bytes from InputStream for DEPLOYMENT_ROOT VirtualFile.openStream() on second call

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-783?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reopened WFLY-783: --------------------------------- > Cannot get bytes from InputStream for DEPLOYMENT_ROOT VirtualFile.openStream() on second call > --------------------------------------------------------------------------------------------- > > Key: WFLY-783 > URL: https://issues.jboss.org/browse/WFLY-783 > Project: WildFly > Issue Type: Bug > Components: OSGi, Server > Reporter: Thomas Diesler > > The effect is that the copy of a installed OSGi bundle is 0bytes in the data/osgi-store area > Digging into this shows that during the first call isDirectory() is false and the file gets mounted. The returned stream works fine. For the second call isDirectory() is true and e read() on the returned InputStream returns -1 > {code} > public InputStream openStream() throws IOException { > if(isDirectory()) { > return new VirtualJarInputStream(this); > } > final VFS.Mount mount = VFS.getMount(this); > return mount.getFileSystem().openInputStream(mount.getMountPoint(), this); > } > {code} > I assume that the root VirtualFile > {code} > VirtualFile virtualFile = deploymentUnit.getAttachment(Attachments.DEPLOYMENT_ROOT).getRoot(); > {code} > should be readable twice. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-1338) Remove support for legacy osgi subsystem namespaces

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1338?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1338: ---------------------------------- > Remove support for legacy osgi subsystem namespaces > --------------------------------------------------- > > Key: WFLY-1338 > URL: https://issues.jboss.org/browse/WFLY-1338 > Project: WildFly > Issue Type: Task > Components: OSGi > Affects Versions: 8.0.0.Alpha1 > Reporter: Thomas Diesler > -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-1280) Allow OSGi services to be registered as JAX-WS endpoints

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1280?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1280: ---------------------------------- > Allow OSGi services to be registered as JAX-WS endpoints > -------------------------------------------------------- > > Key: WFLY-1280 > URL: https://issues.jboss.org/browse/WFLY-1280 > Project: WildFly > Issue Type: Feature Request > Components: OSGi, Web Services > Reporter: Thomas Diesler > > It should be possible to register a WS endpoint similar to this > {code} > public void start(BundleContext context) { > HelloService helloService = new HelloServiceImpl(); > Dictionary props = new Hashtable(); > props.put("service.exported.interfaces", "*"); > props.put("service.exported.configs", "org.apache.cxf.ws"); > props.put("org.apache.cxf.ws.address", "http://localhost:8090/soap"); > registration = context.registerService(HelloService.class.getName(), helloService, props); > } > {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

1
0
0 / 0

[JBoss JIRA] (WFLY-1121) Complete support for OSGi JMX

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1121?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1121: ---------------------------------- > Complete support for OSGi JMX > ----------------------------- > > Key: WFLY-1121 > URL: https://issues.jboss.org/browse/WFLY-1121 > Project: WildFly > Issue Type: Feature Request > Components: JMX, OSGi > Reporter: Thomas Diesler > Labels: roadmap > > R5 TCK compliance for JMX -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-477) Provide a Bundle version of the javax.persistence API

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-477?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reopened WFLY-477: --------------------------------- Assignee: (was: Scott Marlow) > Provide a Bundle version of the javax.persistence API > ----------------------------------------------------- > > Key: WFLY-477 > URL: https://issues.jboss.org/browse/WFLY-477 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate, OSGi > Reporter: Thomas Diesler > > This API is currently provided by hibernate-jpa-2.0-api-1.0.1.Final > Here is an [example|http://mvnrepository.com/artifact/org.eclipse.persistence/javax.p...] -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-1153) Initial OSGi / CDI Integration

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1153?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1153: ---------------------------------- > Initial OSGi / CDI Integration > ------------------------------- > > Key: WFLY-1153 > URL: https://issues.jboss.org/browse/WFLY-1153 > Project: WildFly > Issue Type: Feature Request > Components: CDI / Weld, OSGi > Reporter: Thomas Diesler > Labels: roadmap > > Provide an example test that shows CDI integration -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-1233) Decouple naming & transaction from OSGi

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1233?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1233: ---------------------------------- > Decouple naming & transaction from OSGi > --------------------------------------- > > Key: WFLY-1233 > URL: https://issues.jboss.org/browse/WFLY-1233 > Project: WildFly > Issue Type: Task > Components: OSGi > Reporter: Thomas Diesler > > Currently the naming & transaction subsystem register services on behalf of OSGi > {code} > [tdiesler@tdvaio jboss-as]$ git grep "\"xservice\"" > naming/src/main/java/org/jboss/as/naming/subsystem/NamingSubsystemOSGiService.java: ServiceName serviceName = ServiceName.of("jbosgi", "xservice", regi > transactions/src/main/java/org/jboss/as/txn/service/TransactionManagerService.java: serviceBuilder.addAliases(ServiceName.of("jbosgi", "xservice", Tran > transactions/src/main/java/org/jboss/as/txn/service/UserTransactionService.java: serviceBuilder.addAliases(ServiceName.of("jbosgi", "xservice", UserTra > {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

1
0
0 / 0

[JBoss JIRA] (WFLY-1178) Complete support for OSGi JTA

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1178?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1178: ---------------------------------- > Complete support for OSGi JTA > ----------------------------- > > Key: WFLY-1178 > URL: https://issues.jboss.org/browse/WFLY-1178 > Project: WildFly > Issue Type: Feature Request > Components: OSGi, Transactions > Reporter: Thomas Diesler > Labels: roadmap > > R5 TCK compliance for JTA -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-1244) Dynamic dependencies for non OSGi deployments

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1244?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1244: ---------------------------------- > Dynamic dependencies for non OSGi deployments > --------------------------------------------- > > Key: WFLY-1244 > URL: https://issues.jboss.org/browse/WFLY-1244 > Project: WildFly > Issue Type: Task > Components: OSGi, REST > Reporter: Thomas Diesler > > Currently the RestEasyIntegrationTestCase deploys a JAXRS endpoint that integrates with an OSGi service. The endoint deployment does not trigger the OSGi subsystem to start up, but depends on the compendium being deployed. The compendium gets deployed during OSGi subsystem startup. > There is currently no way for deployment foo to declare a dependency on deployment bar when bar gets deployed during subsystem startup, which gets triggered by deployment foo. > OSGi has the notion of dynamic package import which seems to be required here for non-osgi deployments -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-1095) Complete support for OSGi JDBC

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1095?page=com.atlassian.jira.plugin.... ] Thomas Diesler reopened WFLY-1095: ---------------------------------- > Complete support for OSGi JDBC > ------------------------------ > > Key: WFLY-1095 > URL: https://issues.jboss.org/browse/WFLY-1095 > Project: WildFly > Issue Type: Feature Request > Components: JCA, OSGi > Reporter: Thomas Diesler > Labels: roadmap > > R5 TCK compliance for JDBC -- 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2013