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

[Design of JBoss ESB] - Re: jbossesb-properties.xml filters

by tfennelly

Daniel, this looks fine, but I suspect you may run into problems if you have variable length CSV rows (i.e. with multiple line items as with the quickstart you added). Perhaps this isn't an issue for you in the real world. This has prompted me with an idea however... The EdiSax parser is like the CSVParser in that it converts a non-xml stream (EDI stream) into a stream of SAX events, which are then used to build a DOM (intermediate XML as you've called it). However, the EdiSax parser is more powerful in that it can be configured to handle repeating segments etc (i.e. variable length segments like the line-items). It can also be configured to handle message formats with different delimiter types etc. What I'm thinking is that it might be possible to use the EdiSax parser to parse CSV - just configure the field delimiter to be "," and the segment delimiter to be "& #10;" (linefeed). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041314#4041314 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041314

17 years, 5 months

1
0
0 / 0

[Design of OSGi Integration] - Re: OSGi Bundle Repository

by Kevin.Conner＠jboss.com

Okay, the last sounds good. I'll look at it later today. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041311#4041311 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041311

17 years, 5 months

1
0
0 / 0

[Design of Security on JBoss] - SecurityAssociation no loger valid in remote client

by thomas.diesler＠jboss.com

My test clients have code like this | InitialContext iniCtx = getInitialContext(); | OrganizationHome home = (OrganizationHome)iniCtx.lookup("ejb/RoleSecuredSLSB"); | | OrganizationRemote bean = null; | try | { | bean = home.create(); | fail("Security exception expected"); | } | catch (Exception e) | { | // all cool, now try again with valid credentials | SecurityAssociation.setPrincipal(new SimplePrincipal(USERNAME)); | SecurityAssociation.setCredential(PASSWORD); | bean = home.create(); | } | This no longer works. How is the client now supposed to provide valid principal/credential cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041299#4041299 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041299

17 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: Beta3 roadmap items

by alesj

The same post - with links enabled: + Merge and document the unified metadata work into the mc trunk. http://jira.jboss.com/jira/browse/JBAS-63,JBMICROCONT-177 + Update deployers to utilize the management metadata to describe the management interfaces. + Update the ObjectModelBuilder to build the ManagedObject graphs from the management metadata. http://jira.jboss.com/jira/browse/JBAS-4376 + Add aspects for mapping updates of properties with runtime support so that both the persistent view and live bean property are updated. http://jira.jboss.com/jira/browse/JBMICROCONT-178 + Expand the profile service ManagementView supported component types and CRUD usecases. http://jira.jboss.com/jira/browse/JBAS-4378 + Revise the MainDeployer/Deployer interfaces to support the OSGi model requirements. http://jira.jboss.com/jira/browse/JBOSGI-4 + Replace the UCL class loader with an OSGi bundle consistent class loader and expand the class loading metadata to support proper scoping via import/export/version metadata. http://jira.jboss.com/jira/browse/JBOSGI-7 + Pull the jbossweb container class loader creation outside of the web deployer/tomcat service classes. http://jira.jboss.com/jira/browse/JBAS-4215 + Complete the profile service deployment repository spi to support the jsr88 and OSGi repository notions/usecases. http://jira.jboss.com/jira/browse/JBAS-4363 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041294#4041294 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041294

17 years, 5 months

1
0
0 / 0

[Design of JBoss Admin Console] - hsqldb-jdbc2-service.xml, HighMemoryMark and MaxMemoryMark

by dearemi

Hi, this is a snhapshot of my hsqldb-jdbc2-service.xml configuration file: 0 0 jboss.mq:service=PersistenceManager . I set HighMemoryMark and MaxMemoryMark to '0' value in order to see my localDB.data file growing up. I know, watching the hsqldb log file localDB.log, that the MessageCache write jms messages in the hsqld but localDB.data file size is always 0. I am using jboss3.2.7 with jvm1.4.2. I made the same test with jboss4.0 and jvm5 and localDB.data grew up as I expected. Am I missing something? Thanks. emiliano View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041280#4041280 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041280

17 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Remoting is throwing unrecognized listener ID: blah blah

by ron.sigal＠jboss.com

Ok, with help from Andrew on the related thread http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041276#4041276 I see why this message is appearing. When a callback handler is registered, the client side creates a control connection, and when the handler is unregistered, the control connection is destroyed. However, the creation and destruction is somewhat asymmetric: the connection is created when BisocketClientInvoker.transport() sees an ADDLISTENER message go by, and it is destroyed when the callback BisocketServerInvoker.handleInternalInvocation() gets a REMOVECLIENTLISTENER message. Originally, the treatment was symmetric, but in the case of "quick shutdown" with no network i/o, BisocketClientInvoker is bypassed, which caused a leak. Now, the problem occurs when the Messaging connection is created in a single JVM. Even though the transport is specified as "bisocket", a LocalClientInvoker is used, which makes direct method calls on the server invoker, and so, appropriately, the bisocket control connection isn't created. But the REMOVECLIENTLISTENER message still goes to the callback BisocketServerInvoker, which tries to destroy the non-existent control connection. I'll reduce the message's log level in Remoting 2.2.0.SP3, which I'll create in time for the Messaging 1_2_0_SP2 release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041278#4041278 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041278

17 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Beta3 roadmap items (Repost)

by scott.stark＠jboss.org

The main Beta3 roadmap items for me include the following: + Merge and document the unified metadata work into the mc trunk. http://jira.jboss.com/jira/browse/JBAS-63,JBMICROCONT-177 + Update deployers to utilize the management metadata to describe the management interfaces. + Update the ObjectModelBuilder to build the ManagedObject graphs from the management metadata. http://jira.jboss.com/jira/browse/JBAS-4376 + Add aspects for mapping updates of properties with runtime support so that both the persistent view and live bean property are updated. http://jira.jboss.com/jira/browse/JBMICROCONT-178 + Expand the profile service ManagementView supported component types and CRUD usecases. http://jira.jboss.com/jira/browse/JBAS-4378 + Revise the MainDeployer/Deployer interfaces to support the OSGi model requirements. http://jira.jboss.com/jira/browse/JBOSGI-4 + Replace the UCL class loader with an OSGi bundle consistent class loader and expand the class loading metadata to support proper scoping via import/export/version metadata. http://jira.jboss.com/jira/browse/JBOSGI-7 + Pull the jbossweb container class loader creation outside of the web deployer/tomcat service classes. http://jira.jboss.com/jira/browse/JBAS-4215 + Complete the profile service deployment repository spi to support the jsr88 and OSGi repository notions/usecases. http://jira.jboss.com/jira/browse/JBAS-4363 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037768#4037768 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037768

17 years, 5 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JIRA mailing list

by sergeypk

Right, I should have thought of that. Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041261#4041261 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041261

17 years, 5 months

1
0
0 / 0

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

by scott.stark＠jboss.org

"ron.sigal(a)jboss.com" wrote : | 3. | I suppose the goal is to configure the server invokers as independent pojos, but a problem is that server invokers are created by a factory method in org.jboss.remoting.InvokerRegistry, which is called by Connector. In this particular case, I could change things so that server invokers are created by constructors that register the new invoker with InvokerRegistry, but it seems like a general issue, and I'm wondering if there is a general solution. | There are various ways one can register a bean with another bean in the mc without having to code such a dependency. For example, you can use something like this: | <bean name="BisocketInvoker" | class="..."> | <install bean="InvokerRegistry" method="addInvoker"> | <parameter> | <this/> | </parameter> | </install> | ... | </bean> | this says that the BisocketInvoker bean should be added to the InvokerRegistry bean by calling its addInvoker method with the BisocketInvoker bean instance passed as the argument. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041239#4041239 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041239

17 years, 5 months

1
0
0 / 0

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

by scott.stark＠jboss.org

"ron.sigal(a)jboss.com" wrote : | 2. I've used a "filename" namespace, "http://www.jboss.org/remoting/connector.xsd", which works for org.jboss.xb.binding.sunday.unmarshalling.DefaultSchemaResolver, and I've put the schema in jboss-remoting.jar. Is that OK? | should be fine. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041238#4041238 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041238

17 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2007