April 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Build System] - Re: Build System Meeting Agenda April 12, 2007

by pgier

The repository is now located at https://svn.jboss.org/repos/repository.jboss.org. The JBossBuild page is updated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038029#4038029 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038029

18 years, 11 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Finding the EPR for a provider from a notifier

by mark.little＠jboss.com

JCA support is a definite requirement http://jira.jboss.com/jira/browse/JBESB-415, it's more a case of how in 4.x, versus the 5.0 release of ESB. I'd like to see JCA in ESB 4.2, although it'll definitely be an easier integration path in 5.0. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038028#4038028 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038028

18 years, 11 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: JBossCX -- JBossJCA and Remoting

by weston.price＠jboss.com

anonymous wrote : | I hate acronyms. Name it JBoss Connectors or something. | No. anonymous wrote : | Would this include the rearchitecture around a more message-oriented approach (more to do with remoting, not JCA)? | Correct. That is part of the Remoting3 roadmap. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038026#4038026 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038026

18 years, 11 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: JBossCX -- JBossJCA and Remoting

by mark.little＠jboss.com

Would this include the rearchitecture around a more message-oriented approach (more to do with remoting, not JCA)? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038024#4038024 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038024

18 years, 11 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: JBossCX -- JBossJCA and Remoting

by bill.burke＠jboss.com

I hate acronyms. Name it JBoss Connectors or something. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038022#4038022 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038022

18 years, 11 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Finding the EPR for a provider from a notifier

by weston.price＠jboss.com

Also, please see http://www.jboss.com/index.html?module=bb&op=viewtopic&t=106571 This is a top level discussion about combing JBossRemoting and JCA into one project. One of the main goals would be to support JBossESB connectivity requirements both in terms of JCA as well as other aspect of connectivity as a whole. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038016#4038016 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038016

18 years, 11 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Finding the EPR for a provider from a notifier

by weston.price＠jboss.com

anonymous wrote : | I think using JCA would be a great idea. It would take care of a lot of things that need to be there like transactions, security, and connection management. | Well said :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038015#4038015 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038015

18 years, 11 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Finding the EPR for a provider from a notifier

by derek.adams

I think using JCA would be a great idea. It would take care of a lot of things that need to be there like transactions, security, and connection management. It would also allow JBossESB to integrate with all the existing EIS that already have resource adapters. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038014#4038014 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038014

18 years, 11 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - JBREM-63, configuration pojofication

by scott.stark＠jboss.org

"ron.sigal(a)jboss.com" wrote : | My interpretation is that I should just get rid of the code in Connector that parses the "config" element. It looks like JBossXB can unmarshal all of the constructs in the Connector mbean, so, with the right XML schema, we can leave the mbean in its current form. Is that your intention? | | Also, there are a couple of problems with ripping the parsing code out of Connector. | | 1. The Remoting documentation suggests the use of the Connector.setConfiguration() method. E.g., | | // Set xml configuration element. | StringBuffer buf = new StringBuffer(); | buf.append("<?xml version=\"1.0\"?>\n"); | buf.append(""); | buf.append(" <invoker transport=\"socket\">"); | buf.append(" <attribute name=\"serverBindAddress\">test.somedomain.com"); | buf.append(" <attribute name=\"serverBindPort\">8084"); | buf.append(" <attribute name=\"clientLeasePeriod\">10000"); | buf.append(" "); | buf.append(" "); | buf.append(" <handler subsystem=\"mock\">"); | buf.append(" org.jboss.remoting.transport.mock.SampleInvocationHandler"); | buf.append(" "); | buf.append(" "); | buf.append(""); | ByteArrayInputStream bais = new ByteArrayInputStream(buf.toString().getBytes()); | Document xml = DocumentBuilderFactory.newInstance().newDocumentBuilder().parse(bais); | connector.setConfiguration(xml.getDocumentElement()); | | This comes from a time before Connector accepted configuration maps, and it's no longer necessary, but there could be working code out there that expects the setConfiguration() method. | In my discussion with Tom the Connector object itself seemed superfluous as its just aggregating configuration and parsing. The first step is to ensure that every externalizable behavior has a pojo metadata object. Once that exists, the connector for a given transport should just be configured by specifying its bean descriptor along with its dependencies/properties. The Connector can be kept around for legacy uses, but it should be stripped down to just performing the legacy parsing to produce the new pojo metadata. In general this won't keep up the evolution of the pojos, so it should be deprecated. "ron.sigal(a)jboss.com" wrote : | 2. A number of Remoting unit tests (particularly older ones) use the setConfiguration() method. | What do you think of replacing the current do-it-yourself setConfiguration() method with one that calls JBossXB? | In general use of jbossxb is an improvement, so its a question of porting the testcase descriptors vs producing the pojo metadata using jbossxb parsing. Both should be done. If you look at the mc tests, there is typically a pure programmatic version that only uses the java spis without any descriptors, and a subclass version that produces the same metadata by parsing an external descriptor. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038010#4038010 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038010

18 years, 11 months

1
0
0 / 0

[Design of JBossCache] - Re: JDBC Cache Loader issues

by manik.surtani＠jboss.com

Yeah, there are some performance issues with the JDBC cache loader. Have you tried one of the 2.0.0 releases? It is in BETA at the moment and I'm about to release CR1, this has significant performance improvements there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038007#4038007 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038007

18 years, 11 months

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-dev-forums April 2007