Implement support for JMSType according JMS 1.1 specs paragraph 3.4.8. Provide
corresponding test cases (similar to
org.jboss.test.messaging.jms.message.JMSTimestampHeaderTest)
I have implemented this and done the corresponding unit tests also.
Code submittied to Ovidiu
View the original
Test passed but i could see some errors in message acknowledgement and
|
| [junit] org.jboss.remoting.HandleCallbackException: Error dispatching
callback to handler.
| [junit] at
The distributed test case framework for JMS using jgroups has been
implemented(Based on remoting DTF source base)
Scenario covered
1.One producer
2.One synchronous consumer
Its based on the distributed test framework developed by Tom for remoting
org/jboss/dtf/**
I copied it into
Ovidiu,
Spent last week on analysis of jgroups and the distributed testing framework
developed by Tom.
i developed the test clients with producer/consumers in separate VMs and
notifications through jgroups.
With 3 VMs its very slow and its not so predictable(may be i am doing somethign
In JMS the requirements are
1.Synchrnize the send receive in different JVMs
2.Message sent by the Producer has to be compared to the one consumed by the
consumer
The current DTF, provides mechanism only for remoteAssertions,our reuirements
are for passing objects back and forth between
sure, give me sometime to clear jgroup concepts.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3872069#3872069
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3872069
---
It will be a combination of the two
1. exec will spawn the processes
2. jgroups will choreagraph the events between these processes and the results
this mechanism i am planning to use for the performance tests also.
(remoting does the similar things!) and they have the infrastructure in place.
Hi Ovidiu,
Started working on the test suite last week end.
(Had some issues with compiling the jmx module,hence the delay)
Here is the brief of the test suite structure
Location
${jboss-head}/jms/tests
Package :
org.jboss.test.messaging.jmsapi
org.jboss.test.messaging.jmsapi.connection
Adrian,
My sourceforge id is: rajdeep_dua
My mail id is [EMAIL PROTECTED]
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3871138#3871138
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871138
As a first step towards compliance with 1.1, i have integrated the latest
testsuite from Joram which is for 1.1 compliance
This i tested with JBoss 4.0 release code since the latest jms server is still
not ready.
There are total of 186 tests in this test suite, 2 failed and there were errors
Waiting for the announcement! and the document
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3870842#3870842
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3870842
---
SF
a. got the reason--
org.jboss.messaging.jms.server.container.ServerConnectionInterceptor.invoke()
functionality still has to be imlpemented.
b.Would appreciate if the timelines when the JMSFacade would be in place,for
my testcases to run and do their job.
c.i am using the following way
First one is from sonic,not sure about the licensing issues.
http://www.sonicsoftware.com/products/sonicmq/performance_benchmarking/index.ssp
Second one is an open source performance testing framework for J2EE called
Grinder developed by folks at BEA
http://grinder.sourceforge.net/
I have
Hi
Is the development in a state where jms api client can be written.i thought of
start contribution by writing jms 1.1 compliance tests.
saw a JMSClient in org.jboss.messaging.jms.tools, but not sure where is it
going to pick up the initial context properties from(there is p2p.properties
in
i was able to run a simple jms api test client with this
Properties props = new Properties();
|
props.put(java.naming.factory.initial,org.jboss.messaging.util.StandaloneInitialContextFactory);
| ctx = new InitialContext(props);
please let me know if my writing test
Adrian objectwebs test cases you are talking about - are they same as the joram
test suite.
i had intergrated it with pramat's jms server 3 years back.
i think they have upgraded the test suite for 1.1 version also.
we can integrated those test cases.
My first test client failed yesterday
For check on compliance i am following the specification itself.
each api call has various senarios where things can bomb or atleast there is a
risk!
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3870702#3870702
Reply to the post :
This is the simple test case i was talking about in the previous
topic,connection.getClientID fails,
Is it a bug or a functionality to be implemented?
public void testClientID() {
| //log.info(inside testQueueConection);
| try {
| connection =
thanks, it worked
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3868992#3868992
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3868992
---
SF email is sponsored by - The
My intention is to get familiarised with jboss webservice module,not sure why
this is happening
Why are the calls going to axis impl? still
Any idea why this might be happening
Client side Exception :
Testsuite: org.jboss.test.ws.attachment.AttachmentDIITestCase
| Tests run: 5, Failures: 0,
Hi all
WSDL schema says that root element of a WSDL 2.0
document should be definition/Even the document published by Anil for mapping
from 1.1 to 2.0 shows the same.
http://www.w3.org/2004/08/wsdl
but WSDL 2.0 primer examples show it as description/
Would appreciate if any body could clarify?
WSDL : 1.1
SOAP : 1.1
JAX- RPC : 1.0
SAAJ (for SOAP 1.1)
WS-I Basic profile 1.0(or 1.1)
Has any formal compliance testing been done on interoperatability and WS-I
compliance?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3867222#3867222
Reply to the post :
Thomas,
There are tools available on ws-i.org for checking compliance, have those been
used?
http://ws-i.org/deliverables/index.aspx
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3867229#3867229
Reply to the post :
Found this on axis mailing lists
http://www.extreme.indiana.edu/xgws/soap_bench/
have we tried testing jboss's web service impl and how it compares to others
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3865900#3865900
Reply to the post :
i have been following this field for some time , it looks to me as if web
services is in a mess in terms of number of specs and duplication of
standards--e.g (i found jax rpc as a spec much more cryptic than any of the
main line j2ee specs because of cross references to so many other specs:
Is is possible to generate the java source file for the implementation of the
abstract ejb class files that we define at design time.
It will be really helpful to know what happens behind the scenes.And is it
possible to get hold of the final SQL query generated from the EJB QL?
i had posted a
Wanted to know the roadmap for supporting SOAP over JMS(JAXM).
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3856632#3856632
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3856632
you dont need to configure xdoclet explicitly , it gets configured when you
install jboss ide plugins
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3856052#3856052
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3856052
Ya i also go this error when i tried to use jboss version no as 4.0,when i
mobed to 3.0 it worked fine
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3856056#3856056
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3856056
org.apache.axis.message.SoapElementDirtyImpl class not found
Its not there is axis.jar
:\rajdeep\jboss\NewCheckOut\jboss-head\webservice\src\main\org\jboss\webservice\handler\HandlerChainBaseImpl.java:11:
cannot resolve symbol
| symbol : class SOAPElementDirtyImpl
| location: package
Getting th following compilation errors in jboss-head/varia,i didnot get this
org\jboss\jmx\adaptor\snmp\config package in co or update
I have embedded some of the errors.
E:\rajdeep on
i am doing a
cvs checkout -P jboss-head
still getting the thirdparty module with the following structure
| E:\rajdeep on hydhtc26844\jboss\NewCO\jboss-head\thirdpartydir /b
| .cvsignore
| apache
| beanshell
| bouncycastle
| CVS
| dom4j
| dreambean
| eclipse
| enhydra
|
Please ignore previous post
Scott u r right,i was using the HEAD tag also.
cvs co jboss-head
is the right command
So when is HEAD tag to be used for checking out?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3840439#3840439
Reply to the post :
Sorry for bugging on this again
I checked out everything using HEAD tag
I have been able to compile some modules
Changes i made
Since libraries.ent in tools assumes third party jars are in particular
folder(thirdparty/xdoclet-xdoclet/) but actualt thirdparty module has
Hi I am trying to build the JBossMQ from CVS.
Since the build file assumes the tools module to be in a particular hierarchy but the
actual module seems to be a different tree.
I am getting the following exceptions
configure:
Caught exception (org.apache.tools.ant.BuildException) while expanding
Hi
For getting the latest source code and the build what is the exact path as i want to
contribute to the JMS features.
Is there any path to the CVS?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3837319#3837319
Reply to the post :
36 matches
Mail list logo
