August 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMICROCONT-415) Comprehensive deployer framework documentation

by Thomas Diesler (JIRA)

Comprehensive deployer framework documentation ---------------------------------------------- Key: JBMICROCONT-415 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-415 Project: JBoss Microcontainer Issue Type: Task Components: Deployment Reporter: Thomas Diesler Fix For: JBossMC-2.2.x Please provide comprehensive documentation for the deployer framework. It should cover the individual types of deployers, deployment states, dependency items, modules, etc. Improved javadoc is also covered by this issue. For trunk it is possible to publish the javadoc in the hudson QA environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (JBXB-201) Cannot parse schema/jbxb_1_0.xsd

by Thomas Diesler (JIRA)

Cannot parse schema/jbxb_1_0.xsd -------------------------------- Key: JBXB-201 URL: https://jira.jboss.org/jira/browse/JBXB-201 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Reporter: Thomas Diesler This code String jbxbSchema = "schema/jbxb_1_0.xsd"; URL jbxbXSD = context.getBundle().getResource(jbxbSchema); if (jbxbXSD == null) throw new IllegalStateException("Cannot find: " + jbxbSchema); XSModel xsModel = Util.loadSchema(jbxbXSD.toExternalForm(), (SchemaBindingResolver)null); if (xsModel == null) throw new IllegalStateException("Cannot load schema: " + jbxbSchema); fails with Caused by: org.jboss.xb.binding.JBossXBRuntimeException: -1:-1 94:47 src-element.3: Element 'class' has both a 'type' attribute and a 'anonymous type' child. Only one of these is allowed for an element. at org.jboss.xb.binding.sunday.unmarshalling.XsdBinderTerminatingErrorHandler.handleError(XsdBinderTerminatingErrorHandler.java:40) at org.apache.xerces.impl.xs.XMLSchemaLoader.reportDOMFatalError(Unknown Source) at org.apache.xerces.impl.xs.XSLoaderImpl.loadURI(Unknown Source) at org.jboss.xb.binding.Util.loadSchema(Util.java:367) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBXB-251) Dependency on deprecated artifacts

by Thomas Diesler (JIRA)

Dependency on deprecated artifacts ---------------------------------- Key: JBXB-251 URL: https://jira.jboss.org/jira/browse/JBXB-251 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.2.Beta7 Reporter: Thomas Diesler Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.2.GA Missing: ---------- 1) apache-xerces:xml-apis:jar:2.9.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=apache-xerces -DartifactId=xml-apis -Dversion=2.9.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=apache-xerces -DartifactId=xml-apis -Dversion=2.9.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.jboss.osgi.bundles:jboss-osgi-xml-binding:bundle:2.0.2.Beta7-SNAPSHOT 2) org.jboss:jbossxb:jar:2.0.2.Beta7 3) apache-xerces:xml-apis:jar:2.9.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-263) Invalid dependency on apache-log4j:log4j:jar:1.2.14

by Thomas Diesler (JIRA)

Invalid dependency on apache-log4j:log4j:jar:1.2.14 --------------------------------------------------- Key: JBDEPLOY-263 URL: https://jira.jboss.org/browse/JBDEPLOY-263 Project: JBoss Deployers Issue Type: Bug Reporter: Thomas Diesler deployers/trunk does not build [INFO] Building JBoss Deployers Core ... [INFO] Failed to resolve artifact. Missing: ---------- 1) apache-log4j:log4j:jar:1.2.14 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=apache-log4j -DartifactId=log4j -Dversion=1.2.14 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=apache-log4j -DartifactId=log4j -Dversion=1.2.14 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.jboss.deployers:jboss-deployers-core:jar:2.2.0-SNAPSHOT 2) org.jboss.test:jboss-test:jar:1.1.1.GA 3) apache-log4j:log4j:jar:1.2.14 ---------- 1 required artifact is missing. for artifact: org.jboss.deployers:jboss-deployers-core:jar:2.2.0-SNAPSHOT from the specified remote repositories: jboss-developer-repository-group (https://repository.jboss.org/nexus/content/groups/developer/) Perhaps this is a deprecated dependency -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBXB-202) Incosistent initialization of XSImplementation

by Thomas Diesler (JIRA)

Incosistent initialization of XSImplementation ---------------------------------------------- Key: JBXB-202 URL: https://jira.jboss.org/jira/browse/JBXB-202 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Reporter: Thomas Diesler Fix For: JBossXB-2.0.1.GA In Util there is private static XSImplementation xsImpl; which gets initialized lazily in public static XSModel loadSchema(String xsdURL, SchemaBindingResolver schemaResolver) { if(xsImpl == null) { xsImpl = getXSImplementation(); } All other loadSchema method do not reuse the static property Also, private static XSImplementation getXSImplementation() relies on the thread context classloader, which is not available in an OSGi environment. Could you please provide an JBossXB initialization entry point that is public and does not make an assumption on the availability of the TCCL -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBCL-169) Support attribute matching from OSGi

by Thomas Diesler (JIRA)

Support attribute matching from OSGi ------------------------------------ Key: JBCL-169 URL: https://jira.jboss.org/browse/JBCL-169 Project: JBoss ClassLoader Issue Type: Task Reporter: Thomas Diesler Assignee: Ales Justin And another thing that needs to happen is to bubble the attribute matching from OSGi to jboss classloading. The only reason I originally created OSGi*Capability/Requirement was to implement the attribute matching without modifying jboss classloading so it could be used in older versions of jboss5. That restriction was broken by other changes a long time ago. We might never have got into this horrible situation if I hadn't done that. You should be able to do things like the following in jboss-classloading.xml: <capabilities> <package name="foo" attributes="a=b,c=d"/> </capabilities> <requirements> <package name="bar" match-attributes="(vendor=acme)"/> </requirements> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1282) Add jaxws test coverage

by Thomas Diesler (JIRA)

Add jaxws test coverage ----------------------- Key: EJBTHREE-1282 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1282 Project: EJB 3.0 Issue Type: Task Reporter: Thomas Diesler Assigned To: Heiko Braun Fix For: AS 5.0.0.CR1 Container issues for required WS functionality -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
13
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1284) jaxws handler access to ejb3 security context

by Thomas Diesler (JIRA)

jaxws handler access to ejb3 security context --------------------------------------------- Key: EJBTHREE-1284 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1284 Project: EJB 3.0 Issue Type: Sub-task Reporter: Thomas Diesler -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-225) Create ErrorHandler to DeploymentControllerContext

by Thomas Diesler (JIRA)

Create ErrorHandler to DeploymentControllerContext --------------------------------------------------- Key: JBDEPLOY-225 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-225 Project: JBoss Deployers Issue Type: Feature Request Reporter: Thomas Diesler The MC Framework incorrectly uninstalls the bundle if there is a failure in bundle.start() The controller context reached its required stage DESCRIBED after bundle install. A subsequent call to bundle.start() is supposed to transition to stages CLASSLOADER and then INSTALLED, which corresponds to the Bundle states RESOLVED and ACTIVE respectively. If the transition to INSTALLED fails, the controller context gets undeployed, which causes the bundle to transition to UNINSTALLED. The desired behaviour is: * on fail to resolve: remain in state INSTALLED * on fail to start: remain in state RESOLVED The proposed solution is to add an ErrorHandler to the DeploymentControllerContext if it is an OSGi deployment -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-234) Comprehensive classloading framework documentation

by Thomas Diesler (JIRA)

Comprehensive classloading framework documentation -------------------------------------------------- Key: JBDEPLOY-234 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-234 Project: JBoss Deployers Issue Type: Task Components: general Reporter: Thomas Diesler Assignee: Ales Justin Fix For: JBDEPLOY-2.2.x Please provide comprehensive documentation for the deployer framework. It should cover the individual types of deployers, deployment states, dependency items, modules, etc. Improved javadoc is also covered by this issue. For trunk it is possible to publish the javadoc in the hudson QA environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2010