Ratoo wrote :
| [EMAIL PROTECTED] wrote :
| | HTTP 1.0 Client Did you try that one?
| |
|
| Where is it? How can I configure it?
|
You can use the tomcat Connector configuration to achieve this. Example given
for jboss 4.0.5 restricts .net 2.0 clients to use HTTP 1.0:
| $
Hi,
according to JBWS-723 it is possible to protect access to the WSDL requests of
Web-Services. Looking at it in more detail it appears that access does require
only any valid login, but is not restricted to specific security roles.
Is it possible to restrict the access to WSDLôs of
ragr wrote : For couple of things:
| http://jira.jboss.com/jira/browse/JBWS-1591
|
| and support (plugging) for Sun's JAXB 2.1 support
I just replaced the jaxb libraries sith the 2.1.3 version in JBossWS 1.2.1 -
works like a charm with all JAXB 2.1. annotations I tried so far (esp.
see JBossWS 1.2.1 release announcement : jboss 4.0.5 is required
http://www.jboss.com/index.html?module=bbop=viewtopict=106898
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4048409#4048409
Reply to the post :
the package of complex parameters needs to be specified per java package within
a package-info.java file:
see http://www.jboss.com/index.html?module=bbop=viewtopict=103352
JBossWS 1.2.x generates buggy wsdl files, though unless
Actually I think this is a JBossWS (installer) bug ?
The WSDL and Soap headers default to UTF-8, but the characters sent are in the
machines java default encoding!
I did a hot fix to add the system property
| file.encoding=UTF-8
|
to the jvm running JBossWS, thus changing the
Well, it should work then (solved my problems, though).
Actually make sure that your console will handle UTF-8 correctly, alternatively
you might want to direct the output into a file and check it with an editor/hex
editor of your choice, or generate a html file to check it with a web-browser.
JBossWS is standard conforming, and per se this is not a JBossWS problem. But
it means that updating to new JBossWS versions breaks a lot of client code or
requires to put XMLElement on all generated DataStructures for
nillable non-complex Data fields. Thus it is a JBossWS users problem.
danielmesser wrote : Hi,
| I also get the following exceptions:
| tests-main:
| [mkdir] Created dir:
/home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/reports
| [junit] Running
org.jboss.test.ws.jaxrpc.samples.docstyle.bare.TrivialServiceDocBareTestCase
| [junit]
http://localhost:8080/jbossws/services
you might want to look at the regarding Servlet Implementation
in the jbossws source code generating the page
|
./integration-jboss42/src/main/java/org/jboss/ws/integration/jboss42/JBossContextServlet.java
|
Some steps I't try to make:
1. check that you are running jboss with jdk 1.5 (sun)
2. check that your system classpath is empty when starting jboss
(make sure that no non jboss jabxb, jaxws, classes are found
3. check that the endorsed dirs in jdk are not ... see 2.
4. check
I did a hot fix to add the system property
| file.encoding=UTF-8
|
to the jvm running JBossWS, thus changing the default file !? encoding
of the complete jboss installation. Afterwards UTF-8 handling worked
as expected (before that jbossws 1.2 used the default file encoding of
the
JBossAS 4.0.5 has got JBossWS 1.0.3.SP1 included.
You might want to update to as described here to JBossWS 1.2.0 to use JaxWS
style WebServices with JSR181 annotations. (There is only limited support for
JSR181 in JBossWS 1.0.3.SP1.
JSR181 examples are delivered in the JBossWS Samples. I had
You could find an example at
JBossWS-Forum http://www.jboss.com/index.html?module=bbop=viewtopict=103352
JIRA http://jira.jboss.com/jira/secure/ManageAttachments.jspa?id=12335583
The problem is that I got problems with the JBossWS namespace mapping when
using inherited/aggregated types,
Clients using the .net sdk 2.0 work for Services using doc-literal-wrapped
services generated by jbossws 1.0.x on jboss 4.0.5 for me so far. I did not try
the .net 3.0 sdk so far.
Your could try to switch to doc-literal (if you are not already using this
style) or using the .net 2.0 sdk (Is it
Hi,
http://jira.jboss.com/jira/secure/ManageAttachments.jspa?id=12335583
describes the issue, and provides a patch against the jbossws-samples
distributed with the biniary installer version of jbossws-1.2.0.GA
Best Regards,
Bertl
View the original post :
http://jira.jboss.com/jira/secure/ManageAttachments.jspa?id=12335583
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025996#4025996
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4025996
Hi,
While the @javax.xml.bind.annotation.XmlSchema annotation within the
package-info.java of an class not inheriting from other packages works
perfectly, JBossWS generates the following error for derived datatypes:
| 14:35:02,173 ERROR [ServiceEndpointPublisher] Cannot obtain waURL for:
The same thing happens with
jboss 4.0.5.GA (installed using JEMS installer - thus including
jbossws-1.0.3.SP1 (date=200609291417)
when defining WebServices using JSR 181 annotations applied to
EJB3 Stateless Session Beans. Seems like any parameter of
a type defined within an inheritence
Hi,
according to the specification (Ejb-3_0-spec-persistence.pdf chapter 3.5.2) the
behaviour of @PrePersist and @PreUpdate may be different.
in short words (trying to keep the meaning correct)
@PrePersist and @PreRemove are called before the EntityManger methods persist
and remove are
Hi,
this issue is already discussed in
http://www.jboss.org/index.html?module=bbop=viewtopict=89973
A service release is available (haven`t tested it yet since I am still using my
own work around though :-()
Bertl
View the original post :
Hi again,
the following patch (against jbossws 1.0.3) is a buggy! hotfix - better call it
hack :-) which works for me and maybe also for somebody else getting blocked
with the problem discussed here:
Description and Known issues:
1. This hotfix was done in a hurry without analysing the
Hi,
unfortunately I ran into the very same problem when using any of my
web-services providing methods consuming complexType ... arguments with
nillable elements of any type.
My Environment: JBoss 4.0.4.GA (EJB3-RC8 patch and update to JBossWS 1.0.3
applied/) which takes any web-mehtod
23 matches
Mail list logo
