"anders.hedstrom" wrote : Hi,
| I have a WSDL that defines a webservice with a couple of parameters. One
parameter is an OUT parameter and another one is an INOUT parameter. Both these
parameters are of the type xsd:unsignedLong.
|
Do you know if IN is affected to?
anonymous wrote :
| H
Change REPLACE_WITH_ACTUAL_URL to https://REPLACE_WITH_ACTUAL_URL, and JBoss
will rewrite it using https and the secure port.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872424#3872424
Reply to the post :
http://www.jboss.org/index.html?module=bb&
3. Don't use java2WSDL, use wscompile (included in the Sun JWSDP)
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872415#3872415
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872415
--
All JBoss.NET questions should go to the JBoss.NET forum.
Now that that is said, one way you list the services is to just go to
http://localhost:8080/jboss-net/services
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872414#3872414
Reply to the post
FYI,
I committed DataHandler support into the current 4.0 branch.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872273#3872273
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872273
-
"eykatz" wrote : Hi Jason,
| 1.
| why do I need ws4ee-deployment.xml ?
|
I should update the wiki on that, you most likely won't need it. Try it without
it first.
anonymous wrote :
| 2.
| this file is not J2EE 1.4 mandatory (and JBoss 4 is J2EE 1.4 compilant)
|
Containers are fr
You need to wrap your array in an object.
Take a look at the wiki:
http://www.jboss.org/wiki/Wiki.jsp?page=WSArrayTypeMapping
Thanks,
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871969#3871969
Reply to the post :
http://www.jboss.org/index.html?mo
Try gSOAP http://www.cs.fsu.edu/~engelen/soap.html. Its goal is to be WS-I
basic profile compliant.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871841#3871841
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3
I will try to look at the attachments support in the current code base again
tonight.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871721#3871721
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871721
-
Are you using a typed parameter on your SEI for the attachment, or are you
using Object? Currently you have to use object. I should get a fix for this in
soon.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871215#3871215
Reply to the post :
http://
Great. Well just so you know there is another configuration file that controls
the wsdl generated addresses. Take a look at
deploy/jboss-ws4ee.sar/META-INF/jboss-service.xml.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871217#3871217
Reply to the
JAX-RPC 1.1 does not support collections, so you have to use arrays.
The future specification addresses this.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871227#3871227
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=r
This could be many things. Does your webservice work on the normal port? Is
your apache proxy setup correct (double check your mod_proxy config)?
Also, are you refering the the http.proxyHost setting, because that is only
used when tomcat itself wants to make an http connection outbound. I am
as
Take a look at the wiki http://www.jboss.org/wiki/Wiki.jsp?page=WSAttachments
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871074#3871074
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871074
---
No, annotations is a TODO task in jira, that module needs to be written. Tools
is currently under development (but currrent implementation has no annotation
support). If you are interested in assisting/contributing email the tasks you
are interested in to Thomas Diesler.
Thanks!
-Jason
View t
Try not to reuse a thread for different topics it makes it harder for people
searching the forums to find an answer.
That being said. your answer is that you have 2 options:
1. Pass the hostname in as the -b option to run.sh so that jboss binds only to
one interface
-or-
2. Edit the jboss-servic
Take a look at this wiki for writing a client app
http://www.jboss.org/wiki/Wiki.jsp?page=WSClientAppl. Keep in mind that J2EE
client apps require a portion to be deployed on the server.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871070#3871070
R
There are two ways:
1. Emulate the auth headers. See
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=61328
2. Use HTTP basic auth. See
http://www.jboss.org/wiki/Wiki.jsp?page=WSSecureEndpoint
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871
"md5georg" wrote : Hello,
|
| thanks for the reply jasong!
|
| I am very sorry... the included WSDL part was not correct. It should not
| contain the "qualified" attributes should not be there. I did copy the part
| from the wrong WSDL file. The correct WSDL
"md5georg" wrote :
|
| |
| |http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
| |
| | http://bullen.com/fleet/api/types";>
| | heppadoda!
Set use="literal" in that config file.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870859#3870859
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870859
--
Did you generate a jaxrpc-mapping file?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870857#3870857
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870857
---
SF em
This forum is for J2EE style webservices (ws4ee), which is only available in
jboss 4.x.x. You probably want the JBoss.NET or JMX forum. Also, could you
provide more detailed information about your problem (like which method you are
calling, and what your mbean does)
Thanks,
-Jason
View the or
You must be running 4.0.0, upgrade your jboss to 4.0.1.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870830#3870830
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870830
-
In your jboss.xml file you can add a port component block in each session bean
block that defines the url that looks like this:
|
| Authentication
|
| Authentication
|
/mywebserivcelocation/Authentication
|
|
|
-Jason
View the original post :
http://www.jbo
anonymous cvs lags at least 4 hours behind current head
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870642#3870642
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870642
-
anonymous wrote :
| Will this ever come in non-beta state?
|
Yes, its planned to roll out with the release of Visual Studio 2005. Visual
Studio 2005 Beta 2 is supposed to be released end of this month, and the final
version will be released in September.
-Jason
View the original post :
"omatzura" wrote :
| why is the java-xml-type-mapping (or an equivilant typeMapping in
ws4ee-deployment.xml) also required by jbossws?
|
This is required by jsr109. Otherwise, there would be no way to map the member
variables in the exception.
For more information, take a look at jsr109
Sorry for the confusion, I updated the wiki. The reason Microsoft did not add
support for rpc/literal is because they have always been against rpc/literal
(for some very good reasons). The problem is that they were on the WS-I
profile 1.0 and 1.1 spec team, and that spec team decided to suppor
You could define a soap:header element in your wsdl but you would have to
define a schema element type that replicated the jbws tags exactly (including
the soap:actor attribute). However, the problem you are going to have is how
you actually bind to those parameters in whatever non-java client y
Interesting.
Did you open a bug with Microsoft on this, they should support any valid url
string as that is allowed by the schema?
Also, if you don't want to maintain your own tree of jbossws there is an option
you can add to your jboss.xml or jboss-web.xml called wsdl-publish-location. It
Hi,
Here is a list of things that will probably fix your problem.
1. You are using rpc/encoded style webservices which is not allowed by WS Basic
Profile 1.0, try using rpc/literal instead.
2. Try the latest version of jboss (4.0.1)
3. Don't use java2WSDL, use wscompile (included in the Sun JWS
Yes head is JBoss 5, which will be a J2EE 1.5 implementation, so it contains
ejb3. This is a development branch, so dont expect stability or completeness.
There is also a preview release of ejb3 you can get from the download page.
Thanks,
-Jason
View the original post :
http://www.jboss.org/in
Then yes, if you can replicate the headers with your non-java client it will
work.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870264#3870264
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870264
-
The wiki is about J2EE compatible webservices, which is only present in JBoss
4. If you are using JBoss 3, you are actually using jboss.net.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870263#3870263
Reply to the post :
http://www.jboss.org/index.
JBossWS uses tomcat internally to handler the webservice requests, so the
actual port that jbossws listens on is whatever your tomcat is configured to
listen on. The value WebServicePort is just used for rewriting the service
endpoint address in the wsdl. So basically you want to set the port th
I forgot to explain your error. Basically you can not write a pure standalone
client as you are doing. ServiceFactory is dying because it can not find the
internal jbossws implementation. Change your application to use the methodology
in the example and everything should work great!
Thanks,
-Ja
A J2EE web service client is actually a J2EE application client. This means
that a portion of the client is actually deployed on the server. Your
standalone program then accesses the "client" by using jndi to retrieve it.
Take a look at this step by step wiki, it walks you through the process us
Currently SOAP 1.1. The new JBossWS implementation (being worked on) will
support 1.1 and 1.2.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870127#3870127
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870127
No jboss does not provide its own compiler, although the new implementation
will include a set of tools supporting the new JAX-RPC2 standard. Currently we
recommend using the wscompile tool which is part of the Sun JWSDP. There is
alot of information about this available in the wiki, so I would
Are you using rpc/literal on the java side? Microsoft has not implemented
rpc/literal (though it is planned in the .NET framework 2.0 release, already
available in 2.0 beta). If using a microsoft beta framework is not an option,
you may need to switch to document/literal.
-Jason
View the ori
For better portability take a like at using HTTP basic auth. Take a look at the
wiki for how:
http://www.jboss.org/wiki/Wiki.jsp?page=WSSecureEndpoint
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869917#3869917
Reply to the post :
http://www.jboss
FYI,
Microsoft will incorporate rpc/literal in the 2.0 .NET framework release. It is
currently available in 2.0 Beta 1, although I haven't had time to test it out.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869741#3869741
Reply to the post :
htt
You can suppres their generation by using -define instead of -gen.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869247#3869247
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869247
--
This looks like your jboss is not bound to localhost. I am going to guess that
you had tcpmon running when you started jboss. Jboss by default binds to all ip
addresses on port 8080, but if something else has bound localhost:8080, jboss
will start fine, and just bind the rest of the addresses (
If you mean a standalone client:
http://www.jboss.org/wiki/Wiki.jsp?page=WSClientAppl
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866070#3866070
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866070
---
If you are using basic auth, then the credentials are going to be passed in
each and every http request, which means you dont need to cache them. When
using basic auth in JBossWS, it will authenticate you according to its security
zone, store the credentials, pass them to the EJB layer on invoca
Im sure there have been some people who have done this, but no one has taken
the time to contribute a wiki entry with step by step instructions. You won't
need to reinstall tomcat, because all that jwsdp does is generate a war for you
(when you use the wsdeploy command.) If you read through th
JAX-RPC 1.1 does not support mapping Collections as return types, so for now
you must use an array and wrap it in a JavaBean . The future spec may add
support for it.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865932#3865932
Reply to the post :
JBossWS does not currently support WS-Security, although it is on the road map.
It is probably possible to use jwsdp within jboss as you suggest, but you would
not be able to do J2EE 1.4 style web services. You would have to use their
generated stubs to call your EJB methods directly.
-Jason
V
If its a war you have to put it in the WEB-INF directory instead of META-INF.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865212#3865212
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865212
---
"gregcrider" wrote :
| In the SOAP envelope, you can see "cid:A9FCB00186FA6E4FFC4DB12F3B36CAFB";,
but in the MIME portion where the attachment lives, the Content-Id is wrapped
with < and >. I think this is causing the exception in my client.
|
| Any thoughts?
|
FYI, This is how cid l
The wiki should be updated, wscompile is the best approach. The main reason is
that axis can not generate jaxrpc-mapping.xml which leads to several problems.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861995#3861995
Reply to the post :
http://www
JBossWS is J2EE 1.4 compliant web services, J2EE 1.4 web services are
completely different than Axis (very different APIs and configuration).
However, JBossWS and Axis can not coexist because JBossWS uses a
specially modified version of Axis internally.
If you want portability (deploy on any a
With J2EE web services there is no "command" to deploy web services. You build
your package with the appropriate descriptors, which is what the tutorials are
showing you how to make. Then, when you deploy your war or jar, the web service
is deployed. Reread the wiki, it is quite clear about how
I also started a FAW in the wiki here:
http://www.jboss.org/wiki/Wiki.jsp?page=JBossWSFAQ
Its not much, but a start.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861470#3861470
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posti
FYI for those that don't know. Apache 2.1 is going to include a replacement for
JK called mod_proxy_ajp
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3855229#3855229
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=38552
nevermind it turns out that the build for the branch has identical configs for
server/default and server/standard.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3855009#3855009
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=re
Both of these are using the default scoping config. I am talking about the
difference between 4.0.0 and the latest in the 4.0 cvs branch.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3855008#3855008
Reply to the post :
http://www.jboss.org/index.html?module
I currently have a custom JAAS module inside a sar that is within an ear file.
I noticed a problem with this setup in 4.0.0, when attempting to use the same
security module for web authentication in an external war. If I for example, go
to the jmx-console and invoke isValid() on the JassSecurity
Are there any plans to backport jca 1.5 to the 3.x series?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3845942#3845942
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3845942
--
Sorry errors in my last post...
anonymous wrote :
| Hi,
| I looked at the wsdl that jboss-net creates and it does not denote anywhere that
the parameter should be nillable. I assumed it would figure this out itself - is
there a way to denote this in xdoclet or something?
|
This looks
"khelenek" wrote : Hi,
| I looked at the wsdl that jboss-net creates and it does not denote anywhere that
the parameter should be nillable. I assumed it would figure this out itself - is
there a way to denote this in xdoclet or something?
| [/quate]
|
| This looks like a bug, there is
I should clarify this, you must set the view type of the bean to remote (Adding
view-type="remote" to @ejb.bean)
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3836233#3836233
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=
Yes, the way this works is that the ejb provider first searchs for a local interface
to your bean, and then finally a remote interface. So, all you need to do is set your
view type to remote.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3836230#3836
This is a bug with the JMX wsdl genertor that has been fixed in cvs. If you are not
exposing JMX MBeans as web services, you can work around this problem by deleting the
jmx-net.wsr folder in the jboss-net.sar directory.
View the original post :
http://www.jboss.org/index.html?module=bb&op=vie
@jboss-net.wsdd-operation is a single tag. It is placed on a method and uses the java
method argument names as the soap message part labels (instead of the autogenerated
in0..inN)
It also has an optional returnQName parameter that allows you to name the return
message part.
View the original
67 matches
Mail list logo
