JBossWS provides the webservice features of JBossAS, which in turn is Java EE 5
compliant. So as long as you use the specs included in Java EE (jaxws for
instance) you should not be concerned about portability.
View the original post :
I've scanned the patch, thanks. I've just one concern, ie. whether it's a bit
too aggressive rewriting a file://foo-bar address with one using http
protocol, as theoretically that might refer to a jms binding.
So you might want to enhance the patch a bit scanning the model, getting the
binding
You can store the wsdl locally and point that copy instead of the remote one.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4262598#4262598
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4262598
That's probably because the tool would need to access other imported resources
(xsd/wsdl) which are protected too. A workaround is to download the wsdl and
the referenced resources, modify the links and consume the local version.
You basically need the same as the fix for
You can provide your own JAXBContextFactory, take a look at
org.jboss.ws.core.jaxws.CustomizableJAXBContextFactory for instance. This way
you can setup the property you need in the context at creation.
Then make sure your context factory is loaded by the JBossWS ServiceLoader
(basically you
INteresting link to better follow this topic:
http://blogs.sun.com/searls/entry/jaxb_custom_accessor_for_marshalling
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4257712#4257712
Reply to the post :
That's really good to know Andrew, thanks for the tests.
The GA version of 3.2.1 is coming around the end of October, btw.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4257411#4257411
Reply to the post :
Hi Daniel,
I'm sorry, the latest JBossWS version supporting AS 4.2.3.GA is JBossWS 3.1.1.
http://www.jboss.org/community/wiki/JBossWS-SupportedTargetContainers
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4256623#4256623
Reply to the post :
Depends on when the fix for that is ported to EAP branch. If you're allowed to,
verify there's a JBPAPP jira issue for porting that immediately as soon as it's
done upstream, otherwise create it.
If you're not allowed to just let me know.
View the original post :
Hi,
take a look at
http://www.jboss.org/community/wiki/JBossWS-UserGuide#Address_rewrite.
Besides that, you can force the endpoint address to use in the client, casting
the port to BindingProvider and then setting it there.
View the original post :
Hi Andrew,
any chance you can try with trunk or a SNAPSHOT/Beta1 of 3.2.1 I can produce
for you? Asking as a lot has changed in the mean time...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4256656#4256656
Reply to the post :
JBossWS-Native 3.2.1.Beta1 is in the repo now. Can you try with that please?
Thanks!
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4256703#4256703
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4256703
I'm happy to announce the release of JBossWS-Native 3.2.0 GA.
For a list of the new features, improvements and bug fixes, please refer the
release notes available here:
http://labs.jboss.com/file-access/default/members/jbossws/downloads/ReleaseNotes-jbossws-native-3.2.0.GA.txt
The supported
Have a look at the eardeployment sample in the jbossws testsuite, it does what
you're trying to do.
The forum is still active, but you might not get a lot of replies in this
period of the year ;-)
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4250354#4250354
Running wsprovide offline and including the generated classes as well as the
wsdl contract in the deployed archive (be sure it's correctly referenced in the
@WebService) might save some time as less processing is required to perform the
deployment.
View the original post :
Scheduled for 3.2.1.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4247159#4247159
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4247159
___
jboss-user mailing list
This reminds me of something related to CR/LF when dealing with signatures.
Where do you get the soap elements content from? are you reading them from file?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243822#4243822
Reply to the post :
See my reply on the other thread you opened on this.
Besides that, you can't use Sun's SAAJ implementation directly on JBoss AS with
JBossWS-Native.
If you really want to get rid of jbossws-native-saaj anyway, you can try
JBossWS-CXF and/or JBossWS-Metro.
View the original post :
The point here is SAAJ does not define an API for setting the timeout directly
using the SOAPConnection. So you need to use some kind of proprietary stuff.
Forget about Axis, you can't use it with JBossWS. Take a look at the
JBossWS-Native (I assume that's what you're using)
https://jira.jboss.org/jira/browse/JBWS-2697
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243835#4243835
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4243835
___
jboss-user
As a reference, I'd suggest you to take a look at the jbossws wsse sample
artifacts that are built for AS5 in jbossws testsuite. Basically AS 5 is strict
to standards regarding where to load resources from.
View the original post :
get/setTextContent has recently been implemented in NodeImpl. Something else is
simply not implemented yet. Feel free to create a jira issue for this and link
that here (btw this is an easy chance for contributing adding a small patch ;-)
).
View the original post :
Despite having a basic implementation of WS-Policy, JBossWS-Native does not
support policies for setting MTOM. This means you need to manually set mtom on
client side (please refer to the documentation) or switch to JBossWS-CXF /
JBossWS-Metro.
View the original post :
Sure, lots of people use JBossWS as client of Microsoft ws endpoints.
This said, there might be something weird with the wsdl. Can you try posting it?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243851#4243851
Reply to the post :
Btw there's been a timeframe in the past where the ant.properties.example was
missing (you had a custom ant.properties instead). This has already been fixed
anyway.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243852#4243852
Reply to the post :
Thanks Peter for spreading the right directions on this topic.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4243855#4243855
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4243855
There are many testscases showing usage of ejb3 webservice endpoints in the
jbossws testsuite, just take a look.
JSR109 is actually not supported with CXF, but that's most probably not an
issue for you, as you'd use jaxws for the ejb3 endpoints.
View the original post :
http://www.jboss.org/community/wiki/JBossWS-Authentication
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4237836#4237836
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4237836
___
Sure, 100% tests passing with all the supported target containers is a
requirement for release.
I suspect you're suffering from a installation issue. Did you properly
installed jbossws-metro using the ant deploy-jboss5xx target? Also double-check
you don't have jbossws-native jars in the
This thread and its contents are years old; please move to JAX-WS and follow
the user guide.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4233888#4233888
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4233888
If you want to run the Metro stack on AS 5.1.0.GA, either compile JBossWS-Metro
3.2.0-SNAPSHOT from sources or please wait for the 3.2.0.GA release.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4233889#4233889
Reply to the post :
Hi lafr,
first of all thanks for posting this. Is the exception stacktrace you posted
here complete? It's not clear to me when that serialization actually happen.
Knowing a bit more about the ws client might help understanding your specific
issue.
Also knowing what else you changed in the
Basically, you need to check your classpath:
http://www.jboss.org/index.html?module=bbop=viewtopict=136698
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4233899#4233899
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4233899
Which version of JBossWS are you using? Given the current lib configuration,
you're using the different jax-ws implementation when switching from JDK 1.5 to
1.6 (more specifically you use the Sun's one with JDK6 as you don't have
jbossws specific jars in endorsed dir).
Perhaps you might want to
Yes please, and link it to this thread. Thanks a lot for the analysis.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4233897#4233897
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4233897
The Username Token Profile is about setting username/pwd through SOAP Headers.
Specify the property auth type to prevent the username from being used in the
HTTP header:
((BindingProvider)port).getRequestContext().put(StubExt.PROPERTY_AUTH_TYPE,
StubExt.PROPERTY_AUTH_TYPE_WSSE);
SAML tokens
wsconsume is currently called in the jbossws-framework build to generate
classes for a couple of tests. Take a look at the sources.
Besides that, I've filled this: https://jira.jboss.org/jira/browse/JBWS-2650
View the original post :
Take a look at the src distribution; there're both tests using ws-security and
basic http auth.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4231543#4231543
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4231543
Please fill in a JIRA for this. Also trying with jbossws-cxf would be
interesting.
Afaik the MTOM spec is about optmizing what goes to the wire, but generally
speaking I agree on what you say regarding the way attachment are handled by
the stack.
View the original post :
Take a look at the JAX-WS spec regarding programmatically setting handlers on
client side.
Besides that, there's standand-jaxws-client-config-xml that can be used (as
well as any custom configuration file similar to that) to configure handlers on
client side.
View the original post :
Evaluate using JBossWS-CXF or JBossWS-Metro which support WS-SecurityPolicy.
That's currently the standard way of configuring and using WS-Security.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4231552#4231552
Reply to the post :
The need for setting the endorsed dir is already mentione din the doc, perhaps
we should clarify this better when talking about client side, thanks.
Btw the Sun's exception should generally a pointer to the fact the Sun's jaxws
impl is being used instead of the native one.
View the original
Please try directly using the Sun's tools. The exception you get comes from the
Sun's impl (the jbossws-native jaxws tooling is basically wrapper of the Sun's
one). If you still get the exception, please fill it directly to Sun. Othere
wise post here again and create the jira on the JBWS
The validation you turn on is a schema validation. Catching exception regarding
bad xml is something different. This said, please fill in a jira about this, we
might evaluate removing the ignoreParseErrors=true flag.
View the original post :
I'm happy to announce the release of JBossWS-Native 3.1.2 GA.
For a list of the new features, improvements and bug fixes, please refer the
release notes available here:
http://labs.jboss.com/file-access/default/members/jbossws/downloads/ReleaseNotes-jbossws-native-3.1.2.GA.txt
The supported
This might be useful too:
http://www.jboss.org/community/wiki/JBossWS-SetupYourIDE
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227730#4227730
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4227730
I'd need to double check what was available in AS 4.2.2, I think the -t 2.1
option was later disabled because the implementation of JAX-WS 2.1 was not
complete yet.
For sure you can use the 2.1 target starting from JBossWS Native 3.1.0.GA as
the JAX-WS 2.1 has been completed there.
Otherwise
Thanks Ales; btw I see you moved jboss AS Branch_5_x to using the 2.0.6.GA
deployers, can we do the same for AS trunk?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4226710#4226710
Reply to the post :
Hi,
I'm not sure to get what you mean exactly, anyway the documentation you should
refer to for WS-Security is the following:
http://jbossws.jboss.org/mediawiki/index.php?title=JAX-WS_User_Guide#WS-Security
http://jbossws.jboss.org/mediawiki/index.php?title=WS-Security_options
View the original
Do you have the jbossws-native libraries in you JBOSS_HOME/lib/endorsed as
you're using JDK 6?
Asking because the error message you get is most probably from Metro,
suggesting on client side you're actually using it instead of JBossWS Native
libraries.
Please double check the endorsed lib and
This is classloading issue; I'd say try looking for libraries providing
javax/xml/namespace/QName
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4221650#4221650
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4221650
Can you post here the SEI sources?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4221651#4221651
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4221651
___
jboss-user mailing list
What webservice stack are you using? It seems to me you're trying to deploy CXF
as is on JBoss AS... look at the JBossWS-CXF integration if that's the case.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4221652#4221652
Reply to the post :
Try looking at the testcase in package org.jboss.test.ws.jaxws.jbws1702 , it's
about inheritance.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4221656#4221656
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4221656
You need the schema, soap request/response are not enough to generate the wsdl.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4221661#4221661
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4221661
vdurbha wrote : But the server side endpoint still does not work if I use
@HandlerChain annotation instead of @EndpointConfig to set the security
handler. After digging into the source code of JBossWS and the log files for a
few hours, I understood that for the WS-Security handler to work
If you can see the wsdl from the console and can call the service for instance
with SoapUI, this is definitely a .NET issue. Please provide a java exception
you get on server side if any.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4221664#4221664
Reply to
Please read my last comments on JBWS-1309 issue on Jira. This should work since
August 2008, on AS 5 or later only. I've added 2 testcases showing that:
http://fisheye.jboss.org/changelog/JBossWS/?cs=9612
http://fisheye.jboss.org/changelog/JBossWS/?cs=9609
View the original post :
The documentation clearly says the Record Management is available starting from
version 2.0.3. Which version of JBossWS are you using? The version that comes
with JBoss 4.2.2.GA is 2.0.1.SP2, thus if you did not change anything about
that, you would simply need to upgrade to a more recent
I'm happy to announce the release of JBossWS 3.1.0 GA which includes Native,
CXF and Metro integration.
For a list of the new features, improvements and bug fixes, please refer the
release notes available here:
Profiling would probably help in understanding what's happing there. When wsdl
contracts with huge type models are involved, the port creation can be quite
time consuming because a lot of classes are created. Perhaps you could evaluate
re-using the port instance once it has been created.
In
https://jira.jboss.org/jira/browse/JBWS-2524
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4208459#4208459
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4208459
___
jboss-user
http://jbossws.jboss.org/mediawiki/index.php?title=Log4J
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4208465#4208465
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4208465
___
This has been fixed, branch5x now has JBossWS 3.1.0.CR2 including those
deprecated classes. Thanks for pointing this out.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4208471#4208471
Reply to the post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4208446#4208446
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4208472#4208472
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4208472
This most probably falls under this issue:
https://jira.jboss.org/jira/browse/JBWS-2074
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4208493#4208493
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4208493
That's in JAXWS 2.1 spec, section 3.7. Btw the upcoming 3.1.0 jbossws version
will also treat RuntimeException the same way because of the spec conformance
requirement.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4208499#4208499
Reply to the post :
Hi, could you please show us the structure of your deployment (iow, where is
the referenced bean actually declared). I'd like to add a testcase like this to
the jbossws-cxf testsuite, to try reproducing your issue.
View the original post :
@javax.xml.ws.soap.Addressing will be supported starting from JBossWS-Native
3.1.0.GA, that's scheduled for the end of February 2009.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4208550#4208550
Reply to the post :
Yes, you need to configure the transaction timeout on the server as you did.
Consider that value is in seconds, thus 30 might be really too much.
Perhaps you can better estimate the maximum tx length you might expect and set
that value accordingly.
Also consider taking a look at the
As you probably see in the jboss.org homepage, the JBoss Community Leadership
Awards votes have started.
Here is the list of people I've proposed as they actively contributed to
JBossWS (and related projects):
* Peter Johnson for his forum activity in the issue/Jira category.
* Stefano
Is there a reason why you're not using the WS-Security implementation provided
by jbossws (which of course offers signing functionalities) ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4201606#4201606
Reply to the post :
taral wrote : i tried with jboss ws metro 3.2.2.
| after installation it was giving me error jaxb-xjc.jar is alredy registered.
| can any body comment pl?
|
Btw this will be solved, but it's actually not a blocking issue, it doesn't
hurt. https://jira.jboss.org/jira/browse/JBWS-2385
View
sverker wrote :
| * Use the wsconsume ant task with maven-antrun-plugin. Should work fine but
is not a very elegant solution.
|
I'd saying this is the way to go giving what we have now.
In general, also consider including the jbossws native artifact instead of the
framework one, to be
To better understand, could you please post the exception you're getting please?
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4201616#4201616
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4201616
Since you're using EAP I'd say you get in touch with support so that they can
better help you with your configuration. Perhaps this is not a WS issue and the
max number of allowed connection has to be configured.
View the original post :
No, sorry, you need to configure the logging in jboss-log4j.xml.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4201623#4201623
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4201623
Which version of Wise are you using? did you try with the latest one? Could you
please provide further information on your environment and more logs?
Moreover, please post this on the Wise user forum.
Thanks
View the original post :
This could be the same as your issue:
http://www.jboss.com/index.html?module=bbop=viewtopicp=4073638#4073638
If not, please provide the full stacktrace you get.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4201626#4201626
Reply to the post :
JBossWS-Native does not support WS-Security Policy, so you're right, you need
to use JBossWS-Metro in your case.
This said, considering the error you get, your current installation is broken,
as the Metro stack seems to be looking for Native classes
(org.jboss.ws.core.jaxws.spi.ProviderImpl).
Yes, you need to use JBossWS-Metro, JBossWS native doesn't support that (and
there're currently no plans of supporting it)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4201633#4201633
Reply to the post :
How are you setting the security domain to be used?
Moreover, please note the username digestPassword=true useNonce=true
useCreated=true/ is to be set on client side (even if this is not the
reason of your issue).
Finally, as I suggestion, I'd say take a look at the
Yes, that has just been implemented on trunk and we'll included in the next
release. Getting the sources from svn, giving it a try and providing feedback
now could be usefu if you have some spare time. Thanks!
View the original post :
First of all take a look at this if you didn't already:
http://jbossws.jboss.org/mediawiki/index.php?title=Secure_transport
Then look at the following testcase:
org.jboss.test.ws.interop.nov2007.wsse.UsernameTokenHTTPSTestCase
This said, you can specify the target endpoint address using
OK, I've patched the sources to log that exception (which btw you should have
got in the soap fault anyway). This will be available in JBossWS 3.0.6.
Did you find the reason of your issue in the mean time?
View the original post :
Yes, the reason for this exception is most probably jdk6 being used with jboss
5 for jdk1.5.
Look at the release notes:
http://sourceforge.net/project/shownotes.php?release_id=645033group_id=22866
anonymous wrote :
| Compatibility Issues
| JBossAS 5.0.0.GA can be compiled with both Java5
Perhaps this is related to https://jira.jboss.org/jira/browse/JBWS-1309
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4198342#4198342
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4198342
This is provided through JBossTS http://www.jboss.org/jbosstm/
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4198341#4198341
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4198341
Right now statefull session beans cannot be exposed as webservice with
jbossws-native. You can nevertheless obtain a statefull endpoint through
ws-addressing, take a look at the tests and samples.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4198339#4198339
https://jira.jboss.org/jira/browse/JBWS-2439
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4198349#4198349
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4198349
___
jboss-user
https://jira.jboss.org/jira/browse/JBWS-1309
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4198343#4198343
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4198343
___
jboss-user
I'm happy to announce the release of JBossWS 3.0.5 GA which includes Native,
Metro and Apache CXF integration.
For a list of the new features, improvements and bug fixes, please refer the
release notes available here:
92 matches
Mail list logo
