[JBoss JIRA] Resolved: (JBAS-5826) Update dist build to include stax-api.jar and activation.jar copied to lib/endorsed
by Scott M Stark (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-5826?page=com.atlassian.jira.plug... ]
Scott M Stark resolved JBAS-5826.
---------------------------------
Resolution: Done
The endorsed lib dir now contains:
[585][valkyrie: bin]$ ls ../lib/endorsed/
activation.jar resolver.jar stax-api.jar xercesImpl.jar
jaxb-api.jar serializer.jar xalan.jar
The bootstrap-classloader path now only include the jaxb/stax impls:
<classloader name="bootstrap-classloader" xmlns="urn:jboss:classloader:1.0" export-all="NON_EMPTY" import-all="true">
<!-- FIXME Move to Deployers -->
<root>${jboss.lib.url}/jboss-deployers-core-spi.jar</root>
<root>${jboss.lib.url}/jboss-deployers-core.jar</root>
<root>${jboss.lib.url}/jboss-deployers-client-spi.jar</root>
<root>${jboss.lib.url}/jboss-deployers-client.jar</root>
<root>${jboss.lib.url}/jboss-deployers-structure-spi.jar</root>
<root>${jboss.lib.url}/jboss-deployers-spi.jar</root>
<root>${jboss.lib.url}/jboss-deployers-impl.jar</root>
<root>${jboss.lib.url}/jboss-deployers-vfs-spi.jar</root>
<root>${jboss.lib.url}/jboss-deployers-vfs.jar</root>
<!-- System -->
<root>${jboss.lib.url}/jboss-system.jar</root>
<!-- FIXME Move to JMX -->
<root>${jboss.lib.url}/jboss-j2se.jar</root>
<root>${jboss.lib.url}/jboss-mbeans.jar</root>
<root>${jboss.lib.url}/jboss-jmx.jar</root>
<root>${jboss.lib.url}/jboss-system-jmx.jar</root>
<root>${jboss.lib.url}/dom4j.jar</root>
<!-- JAXB impl here, api is in endorsed -->
<root>${jboss.lib.url}/jaxb-impl.jar</root>
<!-- STAX2 impl here, api is in endorsed -->
<root>${jboss.lib.url}/wstx.jar</root>
</classloader>
> Update dist build to include stax-api.jar and activation.jar copied to lib/endorsed
> -----------------------------------------------------------------------------------
>
> Key: JBAS-5826
> URL: https://jira.jboss.org/jira/browse/JBAS-5826
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System, ClassLoading
> Affects Versions: JBossAS-5.0.0.CR1
> Reporter: Scott M Stark
> Assignee: Scott M Stark
> Fix For: JBossAS-5.0.0.CR2
>
>
> For the updated jaxb 2.1 jars to be included and pass the tck signature tests, the stax-api.jar and activation.jar need to be in the server lib/endorsed.
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBAS-5841) Allow the JMS RAR to determine the destinationType at runtime
by Adrian Brock (JIRA)
Allow the JMS RAR to determine the destinationType at runtime
-------------------------------------------------------------
Key: JBAS-5841
URL: https://jira.jboss.org/jira/browse/JBAS-5841
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JCA service
Reporter: Adrian Brock
Assignee: Jesper Pedersen
Fix For: JBossAS-5.0.0.CR2
Currently the JMS RAR requries the destinationType in the activation config properties to be configured,
see required activation config properties in ra.xml
This is as per the spec recommendation in JCA 1.5 Appendix B
Instead, we try to determine the destinationType from the destination.
Proposed change:
1) Remove destinationType as a required activation config property from ra.xml
2) Rework org.jboss.resource.adapter.jms.inflow.JmsActivation::setupDestination()
to cater for not having destinationType, i.e. lookup the destination in jndi and determine its type
from the interfaces
3) Store the resulting type in JmsActivation and use it in setUpConnection() instead of spec.isTopic()
4) Remove the isTopic() helper from JmsActivationSpec since it is now potentially misleading
--
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
15 years, 7 months
[JBoss JIRA] Closed: (JBXB-5) Evolve the schema driven binding to that needed by the pojoserver
by Alexey Loubyansky (JIRA)
[ https://jira.jboss.org/jira/browse/JBXB-5?page=com.atlassian.jira.plugin.... ]
Alexey Loubyansky closed JBXB-5.
--------------------------------
Resolution: Out of Date
This is out of date now.
> Evolve the schema driven binding to that needed by the pojoserver
> -----------------------------------------------------------------
>
> Key: JBXB-5
> URL: https://jira.jboss.org/jira/browse/JBXB-5
> Project: JBoss XML Binding (JBossXB)
> Issue Type: Feature Request
> Environment: Usecase Resources: jboss-head/testsuite/src/resources/xml/pojoserver
> Reporter: Scott M Stark
> Assignee: Alexey Loubyansky
>
> Ok, so what I would like to see is that Adrian, myself and others provide as freakishly complex as needed xml documents and the associated object model as content that goes into the xml binding testsuite. We need to evolve the associated schema and if necessary, external binding metadata to the point that the xml to java binding is being completely driven by configuration outside of the micro-container.
> In terms of being completely ignorant of the java object model/schema interaction, yes its true that the previous jaxb like frameworks were so completely tied to single dtd/schemas there were not usable for the object models we need to deal with. I'm open to having to tweak our object model somewhat if needed to be completely schema driven. The key thing is that I'm not willing to be restricted to a jaxb compatibile approach if it requires an object model we are not willing to live with. Additional binding metadata through schema annotations or an external jbossxb is fine to move beyond the jaxb compatible model.
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBAS-5842) Fix the injection of mainDeployer, profileService in ProfileServiceBootstrap
by Scott M Stark (JIRA)
Fix the injection of mainDeployer, profileService in ProfileServiceBootstrap
----------------------------------------------------------------------------
Key: JBAS-5842
URL: https://jira.jboss.org/jira/browse/JBAS-5842
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Other
Affects Versions: JBossAS-5.0.0.CR1
Reporter: Scott M Stark
Assignee: Scott M Stark
Fix For: JBossAS-5.0.0.CR2
The ProfileServiceBootstrap is still looking up the mainDeployer and profileService beans rather than using injection:
public void start(Server server) throws Exception
{
shutdown.set(false);
KernelController controller = kernel.getController();
// Get the beans TODO injection!
profileService = getBean(controller, "ProfileService", ProfileService.class);
log.debug("Using ProfileService: " + profileService);
mainDeployer = getBean(controller, "MainDeployer", MainDeployer.class);
log.debug("Using MainDeployer: " + mainDeployer);
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBXB-149) Inconsistent jaxb api dependency
by Scott M Stark (JIRA)
Inconsistent jaxb api dependency
--------------------------------
Key: JBXB-149
URL: https://jira.jboss.org/jira/browse/JBXB-149
Project: JBoss XML Binding (JBossXB)
Issue Type: Feature Request
Affects Versions: JBossXB-2.0.0.CR11
Reporter: Scott M Stark
Fix For: JBossXB-2.0.0.CR13
The jbossxb jaxb api dependency is:
<dependency>
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
<version>2.1</version>
<scope>compile</scope>
</dependency>
but it needs to be updated to be consistent with what we are validating in jbossas as part of the tck:
<dependency>
<groupId>sun-jaxb</groupId>
<artifactId>jaxb-api</artifactId>
<version>2.1.4</version>
</dependency>
--
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
15 years, 7 months