January 2008 - jboss-dev-forums - Jboss List Archives

[Design of JBoss ESB] - Re: Sending an Oracle JMS message to the ESB

by kurt.stam＠jboss.com

For Oracle AQ you can check the Administration Guide, and also the helloword_action quickstart has a oracle_aq directory with an example config. http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/docs/Administra... --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116759#4116759 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116759

17 years, 9 months

1
0
0 / 0

[Design of JBoss ESB] - Sending an Oracle JMS message to the ESB

by tschungelbuch

I would like to send an Oracle JMS messages to the ESB. Is there any documentation available to help me with this? Thanks for the support. Kind regards RH View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116756#4116756 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116756

17 years, 9 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1858 + JBWS-1797: when to generate wsdl?

by alessio.soldano＠jboss.com

OK, back to this issue after the vacation... "heiko.braun(a)jboss.com" wrote : IMO any container (or deployment) dependent meta data should be processed and massaged into the SPI artifacts before transitioning into the actual stack. So I'd say what you suggest makes perfect sense. Process those bits earlier and find a good representation in the SPI artifacts. I didn't look at it myself, but the stack shouldnt deal with container meta data directly at all: | I agree with you Heiko. Unfortunately after checking the code, I think the most proper place to read those bits is in the ContainerMetaDataDeploymentAspect that is part of the 4.0 & 4.2 AS code base; this of course could also be performed in another aspect (even an existing one, for example in the UnifiedMetaDataDeploymentAspect, before actually building the MD), but I don't like the idea of parsing the web.xml there... even if I tried it and of course it fixes JBWS-1797 with AS 4.2 ( I save the config name/file in 2 properties using the org.jboss.wsf.spi.deployment.Deployment then read them in the JAXWSServerMetaDataBuilder in case the same info is not available through the JSEArchiveMetaData) How should we proceed in this case? We can't change the AS4.2 code now, right? Please also consider that we could of course forget about JBWS-1797 with AS4.2 (as a matter of fact it is marked as resolved), but in that case I think JBWS-1858 should be marked as won't fix since generating the wsdl later is useless at least as far as the only reason for doing so is related to the endpoint config. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116752#4116752 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116752

17 years, 9 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: ClassNotFoundException on Server Startup

by flavia.rainone＠jboss.com

Yes, I have already packaged the release... the only thing that is not done is: -publish it at jboss.org (need svn access for that) -add it to buildthirdparty (because of the messaging issue I didn't know how to resolve) -and, finally, add it to the maven repo... If we can do a retagging, I think we should go for that. I am not sure, however, whether we should wait for the fix of JBAOP-499. But maybe we should include, also, the fixes JBAOP-500 (I'm about to commit it) and JBAOP-256 (I have already done it, but need to test before commiting. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116713#4116713 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116713

17 years, 9 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: ClassNotFoundException on Server Startup

by kabir.khan＠jboss.com

If the release has not been pushed out as a binary to the repository we can retag it in svn | $ svn remove https://svn.jboss.org/repos/jbossas/projects/aop/tags/JBoss_AOP_2_0_0_CR2/ | Obviously, this depends on if you have started packaging the release yet :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116691#4116691 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116691

17 years, 9 months

1
0
0 / 0

[Design of POJO Server] - migrating TransactionManager and Invokers to POJO

by jhalliday

For some time I've been trying to convert the TransactionManager integration for AS5 over to microcontainer from JMX, see http://www.jboss.com/index.html?module=bb&op=viewtopic&t=124499 for the story so far. We have arrived at a point where it looks like the best option may be to bite the bullet and move the TransactionManager plus anything that depends on it i.e. the invokers, out of jboss-service.xml and into deploy instead. Anyone from the AS side care to comment? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116685#4116685 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116685

17 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: NPE booting Embedded JBoss from trunk

by timfox

"anil.saldhana(a)jboss.com" wrote : | You have to ask Mr.Fox. Best to ask Clebert - he has been handling the AS5 integration :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116643#4116643 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116643

17 years, 9 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: some enhancements to jboss-test

by akostadinov

I guess your intention is to not leave the server running till ant exit but allow jboss test suite to complete. If that's correct, Martin's changes are sufficient since he made server process to be destroyed during stop task. So -H retry would not be needed. What I don't like with current implementation is that we will not notice shutdown issues in test suite runs. Unfortunately I can't think of a generic way to make the job execute to completion but fail if any servers failed to shutdown. What is easiest to implement is: 1. if server fails to shutdown and failonerror is false (the default), then set a project property "jboss.server.shutdown.fail" 2. have that line after all tests finish '' Do you want me to do make these changes: #1 in the ant task fine and #2 in the Jboss AS 5 testsuite/build.xml file? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116613#4116613 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116613

17 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: NPE booting Embedded JBoss from trunk

by anil.saldhana＠jboss.com

http://viewvc.jboss.org/cgi-bin/viewvc.cgi/messaging/trunk/src/main/org/j... The line 254 is | id = state.getDelegate().getID(); | You have to ask Mr.Fox. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116603#4116603 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116603

17 years, 9 months

1
0
0 / 0

[Design of JBossCache] - Re: Problem with after loading Huge data

by sanatmastan

I would also like to add the data volume of our application it would be around 70Gb which we are planning to cluster them on different VM on a single node. Thanks in Advance Sanat View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116600#4116600 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116600

17 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums January 2008