Hi all,
I wrote an ant script to precompile the jmx-console jsps for Jboss 3.2.6. It
processes without error, (after I jarred the class files), but when I deploy my
new jmx-console.war, I can't seem to browse to the default page
(http://localhost:8080/jmx-console/), I get the "Cannot find serv
Hello,
I noticed that JBoss-net.sar is different in JBoss 3.2.6 final (axis.jar has
been replaced with axis-ws4ee.jar). I was able to get my RPC-style webservice
(.ear) to work correctly, however I am having difficulties with my
Message-style/Java Web Service webservice (.wsr).
I think I need
Look at "Discover SOAP encoding's impact on Web service performance"
(http://www-106.ibm.com/developerworks/webservices/library/ws-soapenc/ )
which not only explains the performance impact of different encoding styles:
rpc/encoded, rpc/literal, document/literal but also offers free test suite to
Check out
http://www.csd.abdn.ac.uk/~bscharla/teaching/mtp_software/jboss/jboss-net-HelloWorld.shtml
which talks about how to tweak simple Axis webservices to work with JBOSS.NET.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844731#3844731
Reply to the p
try:
phoneappend.wsr
/org
in your application.xml. The context-root may be incorrect
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844730#3844730
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p
See post "Performance with large SOAP messages" in this forum. You could try
switching from an ejb exposed as a webservice to a simple webservice described in that
post. This may or may not help with the response time.
View the original post :
http://www.jboss.org/index.html?module=bb&op=view
See the posting in "Is it possible to use JMS instead of HTTP with Web Services?" The
Axis download has a sample.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844727#3844727
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=rep
JBOSS.NET is actually the Apache Axis engine and there is a JMS example in the Axis
download (http://ws.apache.org/axis/releases.html). If you want a stable non alpha
release, try 1.1rc2. After downloading, look in the \samples\jms directory. There is
a AxisJMSSample.pdf file that describes
xmlns:Axis="http://localhost:8080/axis/services/Axis"; after targetNamespace (line 5)
maybe.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844722#3844722
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844722
--
Sorry, half my message seems to get truncated:
"parameter name="beanJndiName" value="UserManagerLocal""
in your web-service.xml may be incorrect. Are you using jndi-name=""
in your @ejb:bean tag?(I am assuming you are using XDoclets to generate the home and
remote ejb interface).
Also check yo
in your web-service.xml may be incorrect. Are you using jndi-name="" in your @ejb:bean tag?(I am assuming you are using XDoclets to generate the
home and remote ejb interface).
Also check your @jboss-net:web-service urn= tag.
View the original post :
http://www.jboss.org/index.html?module=bb&
Any possibility of moving to a more recent level of JBOSS (3.2.6 perhaps). It supports
a newer level of Tomcat (5 I beleive) as well as using Axis 1.1 (JBoss.NET). I am not
sure what 3.2.1 used. You might have better luck with suggestions in the forum using
the newer levels. I have seen atlea
1 -yes
2 - yes (3.2.4)
3 - yes
4 - no but
I have taken wsdl from a webservice (not deployed in JBOSS) and used it to generate a
.NET client AWHILE ago. Can you use the WSDL to generate a .NET client?
I don't think your issue is the local vs remote interface. Since you are exposing
your
JBOSS does not understand deploy.wsdd files even though it use Axis as it's soap
engine. It understands web-service.xml. This link describes how to tweak a simple
axis webservice to deploy in JBOSS:
http://www.csd.abdn.ac.uk/~bscharla/teaching/mtp_software/jboss/jboss-net-HelloWorld.shtml
Vie
Your correct, there is no hot deploy for simple webservices (.wsr archives). I have
been searching to discover whether this will be supported soon. JBOSS uses the Apache
Axis Soap implementation and from what I had last seen, it does not support hot
deployment.
View the original post :
http:
http://www.csd.abdn.ac.uk/~bscharla/teaching/mtp_software/jboss/jboss-net-HelloWorld.shtml
describes the changes needed to deploy a simple Axis webservice in JBOSS (a non ejb
implementation). Most JBOSS examples illustrate exposing an ejb as a webservice
(which I assume is what you refer to as
1. How can I find out what version of SOAP v1.1 or v1.2 does JBoss support ?
Search the forum for Jboss.net or read thru the messages in the section you posted.
JBOSS 4.0 according to this forum now uses Axis 1.2 which supports SOAP v1.2.
2. How to deploy web services in to JBoss 3.2.5 Server
Can you share your SOAP message sizes: average size vs large size? Also what platform
you are running JBOSS on? I am interested in the performance impact of JBOSS.NET on
large soap messages.
I think you may be correct in that the parsing is not scaling well on the larger
messages.
I'm assu
It may have to do with the fact that .NET uses document/literal wrapped style of WSDL
whereas JBOSS by and large uses RPC/encoded. You may have some problems if you are
taking the WSDL generated in JBOSS and attempting to use it in .NET.
http://www-106.ibm.com/developerworks/webservices/librar
For information about Hibernate, you could try either their website:
http://www.hibernate.org/, or Bruce Tate [EMAIL PROTECTED](www.2life.com). He has
been giving seminars on Hibernate through the "No Fluff Just Stuff Java Symposium"
(http://www.nofluffjuststuff.com/index.jsp). I attended the
20 matches
Mail list logo
