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

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

by dimitris＠jboss.org

Can you please create a JBAS jira to track this change with fix version AS 4.2.3.GA? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118074#4118074 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118074

18 years, 2 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, thanks. I've commited a change to the ContainerMetaDataAdapter in the 4.2 branch of the AS codebase; it reads the jbossws configuration from the web.xml and enriches the container independent JSEArchiveMetaData with the missing information. This way no changes has to be done neither on the spi or on the native stack code base. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118050#4118050 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118050

18 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: ClassLoader isolation issue with ObjectMessage

by clebert.suconic＠jboss.com

We already talked about this privately... so this is just to complete the thread. Jeff pointed me that he was de-serializing when the message was received, instead of when the user/testcase called getObject on the ObjectMessage, what caused StreamUtils to use the wrong classLoader (passed by Thread.currentContextClassLoader()). After Jeff used Lazy serialization the test was fixed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118029#4118029 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118029

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: NoCopyNestedJarHandler usage

by alesj

"alesj" wrote : "scott.stark(a)jboss.org" wrote : The testULRClassloading and testURLClassLoader work with the proper classpath for the no copy case. When adding tests for ?useNoCopyJarHandler=true, its failing with java.lang.IllegalArgumentException: URI has a query component. | | | Where do I find all these tests? OK, couldn't find my own test. :-) For some reason my svn update was silently failing, not being able to update the SeamVFSClassloadingTestCase, since it already existed, but wasn't added to svn. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118017#4118017 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118017

18 years, 2 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Using JBoss AS mavenized components

by pgier

Looks like the asintegration project did not have the periodic builds configured correctly so it wasn't doing a regular deployment. I'll deploy those and set up a weekly build for it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117999#4117999 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117999

18 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - ClassLoader isolation issue with ObjectMessage

by jmesnil

in the trunk, ObjectMessageTest.testClassLoaderIsolation() is failing: | junit.framework.AssertionFailedError: expected not same | at org.jboss.test.messaging.util.ProxyAssertSupport.assertNotSame(ProxyAssertSupport.java:478) | at org.jboss.test.messaging.jms.message.ObjectMessageTest.testClassLoaderIsolation(ObjectMessageTest.java:100) | The test sends an object message with the normal classloader and receives the message with another classloader set as the current thread's class loader. It then checks that the two objects have different classes (since they should belong to 2 different classloaders) I tried to reuse JBM Stable StreamUtils to unmarshall the object with the right context class loader but it did not work: | Index: /home/jmesnil/workspace/jboss-messaging/src/main/org/jboss/jms/message/JBossObjectMessage.java | =================================================================== | --- /home/jmesnil/workspace/jboss-messaging/src/main/org/jboss/jms/message/JBossObjectMessage.java (revision 3545) | +++ /home/jmesnil/workspace/jboss-messaging/src/main/org/jboss/jms/message/JBossObjectMessage.java (working copy) | @@ -23,8 +23,6 @@ | | import java.io.DataInputStream; | import java.io.DataOutputStream; | -import java.io.ObjectInputStream; | -import java.io.ObjectOutputStream; | import java.io.Serializable; | | import javax.jms.JMSException; | @@ -124,9 +122,7 @@ | | protected void writePayload(DataOutputStream daos) throws Exception | { | - ObjectOutputStream oos = new ObjectOutputStream(daos); | - oos.writeObject(object); | - oos.flush(); | + StreamUtils.writeObject(daos, object, false, true); | } | | protected void readPayload(DataInputStream dais) throws Exception | @@ -131,8 +127,7 @@ | | protected void readPayload(DataInputStream dais) throws Exception | { | - ObjectInputStream ois = new ObjectInputStream(dais); | - object = (Serializable)ois.readObject(); | + object = (Serializable)StreamUtils.readObject(dais, true); | } | | // Private ------------------------------------------------------- | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117998#4117998 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117998

18 years, 2 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Using JBoss AS mavenized components

by ALRubinger

Thanks for your help, Paul. There were 6, a run today revealed now only 1 missing (perhaps you've put up the other 5 already? :) ) Remaining: org.jboss:jboss-classloading-spi:jar:5.0.0-SNAPSHOT "mvn deploy" wasn't working in many cases yesterday, including "connector" and "aspects" module due to unresolved dependencies. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117996#4117996 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117996

18 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2.0 JDBCPersistenceManager - volunteers?

by max.andersen＠jboss.com

my 2 cent: Afaik from the talks I had with Tim and others from messaging you guys basically have 1 or 2 tables you are doing data inserts into - nothing fancy at all and you don't really have any "state" to carry around except single messages. For that StatelessSession is the right thing to use if you want to use hibernate. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117986#4117986 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117986

18 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2.0 JDBCPersistenceManager - volunteers?

by jhowell＠redhat.com

Tim, correct me if I'm wrong.... The db persistence interface is only there so we can work out of the box. The "real" persistence that we are recommending to customers will be the file based persistence utilizing Oracle's Berkeley DB. That is going to be the persistence that we will recommend to customers, if they call and say that the db persistence runs slow. Because of licensing constraints, we can't ship Berkeley DB, so we ship with a db persister that utilizes hypersonic. Since we are shipping with a db persister, the thinking is that we should ship with something that plugs into many DBs. Since we have to work out of the box, with hypersonic, then we should just make a jdbc persister that can use all databases. So then we would have to maintain scripts, so we use an abstraction that will keep us from maintaining scripts. I agree that using hibernate, the performance may be slower. It usually is when you introduce an abstraction. But what we get for the possible performance hit is that the the messaging team doesn't have to write and maintain a script for each database. The question that I have is, since the db persistence manager is not the manager that will will eventually recommend to our customers, should we really need to worry about any other database, other than the one we ship with? Why would anyone use Oracle, or Mysql for JMS persistence, when it will be slower than the Berkeley DB file persister. I guess what I'm saying is that I think the DB persistence manager is not really that important since the recommended persistence manager will be Berkeley DB. So why are we putting work into making a cross db persistence mechanism in the first place. We could keep the current code base(with only one script) and just support the internal db that we ship with, hypersonic(yuck). The messaging team wouldn't have to do any work and one script would be easy to keep up with. When users say, Hypersonic is bad, we tell them to use Berkeley DB. It seems much simpler to have two choices and much easier to support. I'd definitely vote to throw out cross db persistence in JBM. Jay:) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117954#4117954 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117954

18 years, 2 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Using JBoss AS mavenized components

by pgier

The snapshots get deleted after 30 days. If there are specific ones that you need, just let me know and I'll upload some new ones. I've been setting up more hudson builds to automatically deploy snapshots so that we always have up to date snapshots. But for now, just let me know which ones you need, or if you have the dependency project already checked out then just do "mvn deploy". View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117944#4117944 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117944

18 years, 2 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 January 2008