May 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1786) Create endpoint deployers

by Carlo de Wolf (JIRA)

Create endpoint deployers ------------------------- Key: EJBTHREE-1786 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1786 Project: EJB 3.0 Issue Type: Task Components: endpoint-deployers Reporter: Carlo de Wolf Assignee: Carlo de Wolf -- 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

17 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1772) Create an endpoint SPI

by Carlo de Wolf (JIRA)

Create an endpoint SPI ---------------------- Key: EJBTHREE-1772 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1772 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assignee: Carlo de Wolf -- 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

17 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-6666) Option to disable auto discovery at the client VM level

by Galder Zamarreño (JIRA)

Option to disable auto discovery at the client VM level ------------------------------------------------------- Key: JBAS-6666 URL: https://jira.jboss.org/jira/browse/JBAS-6666 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering, Naming Reporter: Galder Zamarreño Assignee: Galder Zamarreño Add an option to disable auto discovery at the client VM level via system property, i.e. -Dglobal.jnp.DisableDiscovery This would complement existing jnp.DisableDiscovery property that can be passed to InitialContext() on creation. The system property can be overriden by per InitialContext() jnp.DisableDiscovery property. Example: - If no system propery is defined or is set to false: - If jnp.DisableDiscovery not present or is defined as false, auto discovery will be attempted. - If jnp.DisableDiscovery is present and is set to true, auto discovery will NOT be attempted (override default value). - If system property is defined as true: - If jnp.DisableDiscovery not present, auto discovery will NOT be attempted. - If jnp.DisableDiscovery is present and is set to true, auto discovery will NOT be attempted. - If jnp.DisableDiscovery is present and is set to false, auto discovery will be attempted (override default value). -- 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

17 years, 2 months

3
11
0 / 0

[JBoss JIRA] Assigned: (JBAS-2282) JBossEntityResolver is not using schemaLocation URIs that are valid non-file URLs

by Richard Opalka (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-2282?page=com.atlassian.jira.plug... ] Richard Opalka reassigned JBAS-2282: ------------------------------------ Assignee: Richard Opalka (was: Alexey Loubyansky) > JBossEntityResolver is not using schemaLocation URIs that are valid non-file URLs > --------------------------------------------------------------------------------- > > Key: JBAS-2282 > URL: https://jira.jboss.org/jira/browse/JBAS-2282 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XML services > Affects Versions: JBossAS-4.0.3RC2 > Reporter: Scott M Stark > Assignee: Richard Opalka > Fix For: JBossAS-5.1.0.GA > > Attachments: jboss-entity-resolver.zip > > > The org.jboss.util.xml.JBossEntityResolver is not dealing with systemIDs that are valid non-file URLs. For example, this xml fragment from a testcase which uses the jboss resource URL: > <?xml version="1.0" encoding="UTF-8"?> >  > <jaas:policy > xsi:schemaLocation="urn:jboss:security-config resource:security-config_4_1.xsd" > xmlns:jaas="urn:jboss:security-config" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > > > does map to a valid URL which can be loaded, but the parsing of this URL by the getLocalEntityName ends up throwing away the full path info to produce a resource name of schema/security-config_4_1.xsd. This would work inside the jboss server provided the security-config_4_1.xsd is bundled into a classpath location following the location conventions expected by the JBossEntityResolver, but does not work in the testsuite where this is not the case, and would not work for user defined schemas located elsewhere. It would seem we should try to load the schema from systemIDs that are valid URLs before defaulting to the jboss specific logic. -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-2038) Need to externalize the JBossEntityResolver configuration and support namespace to schema resolution

by Richard Opalka (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-2038?page=com.atlassian.jira.plug... ] Richard Opalka reassigned JBAS-2038: ------------------------------------ Assignee: Richard Opalka (was: Alexey Loubyansky) > Need to externalize the JBossEntityResolver configuration and support namespace to schema resolution > ---------------------------------------------------------------------------------------------------- > > Key: JBAS-2038 > URL: https://jira.jboss.org/jira/browse/JBAS-2038 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: XML services > Reporter: Scott M Stark > Assignee: Richard Opalka > Attachments: catalog.xsd > > > With the increased use of JBossXB and its leveraging of the JBossEntityResolver as a means for locating element schemas, we need support for externalizing the configuration of the JBossEntityResolver. We also need to have the notion of resolving a namespace to a schema URI since in general there is no publicID for an element, and a generally unsable systemID since it can be a function of the deployment and server run dir. > Implementing the javax.xml.transform.URIResolver resolve method: > public javax.xml.transform.Source resolve(String href, String base) > throws javax.xml.transform.TransformerException > might be a better api for resolving namespaces. > I have tried integrating the apache commons xml catalog resolver but have not been happy with its semantics and configuration support as yet. We certainly could at least use the catalog.xml schema for representing the externalized mappings. -- 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

17 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMETA-194) tests for jboss_5_1.xsd and 5.1 EJB metadata

by Alexey Loubyansky (JIRA)

tests for jboss_5_1.xsd and 5.1 EJB metadata -------------------------------------------- Key: JBMETA-194 URL: https://jira.jboss.org/jira/browse/JBMETA-194 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 1.0.0.GA jboss_5_1.xsd is not tested. -- 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

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (GPD-316) show problems in problems view

by Tom Baeyens (JIRA)

show problems in problems view ------------------------------ Key: GPD-316 URL: https://jira.jboss.org/jira/browse/GPD-316 Project: JBoss jBPM GPD Issue Type: Task Reporter: Tom Baeyens Assignee: Koen Aers Fix For: jBPM jPDL Designer 4.0.0.CR1 Can you see if you can add this in ? @see JpdlParser static JpdlParser jpdlParser = new JpdlParser(); List<Problem> problems = jpdlParser.createParse() .setResource(...) .execute() .getProblems(); -- 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

17 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (GPD-311) subelements of transition are removed when saving

by Tom Baeyens (JIRA)

subelements of transition are removed when saving ------------------------------------------------- Key: GPD-311 URL: https://jira.jboss.org/jira/browse/GPD-311 Project: JBoss jBPM GPD Issue Type: Bug Reporter: Tom Baeyens Assignee: Koen Aers Fix For: jBPM jPDL Designer 4.0.0.beta2 when saving a process with a transition with subelements, the subelements are removed. at least this was the case with event-listener. since this is an unknown element in the current version of the designer, it should be left in as is. -- 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

17 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (GPD-319) timer configuration

by Koen Aers (JIRA)

timer configuration ------------------- Key: GPD-319 URL: https://jira.jboss.org/jira/browse/GPD-319 Project: JBoss jBPM GPD Issue Type: Sub-task Reporter: Koen Aers Assignee: Koen Aers Fix For: jBPM jPDL Designer 4.0.0.beta2 -- 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

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (GPD-318) event listener configuration

by Koen Aers (JIRA)

event listener configuration ---------------------------- Key: GPD-318 URL: https://jira.jboss.org/jira/browse/GPD-318 Project: JBoss jBPM GPD Issue Type: Sub-task Reporter: Koen Aers Assignee: Koen Aers Fix For: jBPM jPDL Designer 4.0.0.beta2 -- 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

17 years, 2 months

1
1
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 May 2009