[jboss-user] [JBossWS] - Re: http://org.jboss.ws/http#chunksize

2008-02-05 Thread centecbertl
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:


  | $ diff -U 5 server.xml~ server.xml
  | --- server.xml~ 2006-12-06 16:03:28.403259700 +0100
  | +++ server.xml  2006-12-16 10:18:38.265625000 +0100
  | @@ -11,16 +11,18 @@
  |!-- A HTTP/1.1 Connector on port 8080 --
  |Connector port=8080 address=${jboss.bind.address}
  |   maxThreads=250 strategy=ms maxHttpHeaderSize=8192
  |   emptySessionPath=true
  |   enableLookups=false redirectPort=8443 acceptCount=100
  | - connectionTimeout=2 disableUploadTimeout=true/
  | + connectionTimeout=2 disableUploadTimeout=true
  | +restrictedUserAgents=^.*MS Web Services Client Protocol.*$/
  |  
  |!-- Add this option to the connector to avoid problems with 
  |.NET clients that don't implement HTTP/1.1 correctly 
  |   restrictedUserAgents=^.*MS Web Services Client Protocol 
1.1.4322.*$
  |--
  | +
  | 
  |!-- A AJP 1.3 Connector on port 8009 --
  |Connector port=8009 address=${jboss.bind.address}
  |   emptySessionPath=true enableLookups=false redirectPort=8443 
  |   protocol=AJP/1.3/
  | @@ -29,11 +31,12 @@
  |Connector port=8443 address=${jboss.bind.address}
  | maxThreads=100 strategy=ms maxHttpHeaderSize=8192
  | emptySessionPath=true
  | scheme=https secure=true clientAuth=false 
  | keystoreFile=${jboss.server.home.dir}/conf/centec.keystore
  | -   keystorePass=centec sslProtocol = TLS /
  | +   keystorePass=centec sslProtocol = TLS 
  | +  restrictedUserAgents=^.*MS Web Services Client Protocol.*$/
  |!-- --
  |  
  |Engine name=jboss.web defaultHost=localhost
  |  
  |   !-- The JAAS based authentication and authorization realm 
implementation
  | 

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4126500#4126500

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4126500
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Protected Access to WSDL - How to define required Security R

2007-11-20 Thread centecbertl
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 Web-Services in a role 
based manner per Web-Service? 

Use case: We have a full web-service API for internal use. For Clients we want 
to make one or two of these services available without publishing the full API 
structure (services, data structures,...) related to internal web-services. So 
the idea is that access to internal web-services and their WSDL requires a 
security roles which are not granted to clients.

Kind Regards
Bertl


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4106292#4106292

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4106292

___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: Availability of Jbossws-2.1.0

2007-08-03 Thread centecbertl
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. 
XmlSeeAlso,..)


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4070510#4070510

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4070510
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: jbossws 1.2.1 error

2007-05-24 Thread centecbertl
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 : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4048409
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: creating new targetnamespace for complex types

2007-05-15 Thread centecbertl
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 
http://jira.jboss.com/jira/secure/ManageAttachments.jspa?id=12335583 
is fixed (scheduled for version 2.0.0 now).

Although the wsdl files are not correct, clients generated with .net 2.0 and
axis 1.4 tend towork at least when the parameter typ names are unique 
without looking at their package names. The client stub generators are
intelligent enough to remember the correct package names then.



View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4045790#4045790

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4045790
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: how to deal with unicode

2007-05-02 Thread centecbertl
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 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 installation (was iso latin 1 on my machine)

Has anyone found the correct way to configure the file encoding of
jbossws 1.2?



View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4042332#4042332

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4042332
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: how to deal with unicode

2007-05-02 Thread centecbertl
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. 
(is much easier than configuring an arbitrary linux console to show utf-8 :-)

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4042502#4042502

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4042502
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: JbossWS 1.2.1 and .Net 2.0 client

2007-04-27 Thread centecbertl
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.

Detail:
(i.e. autoboxing Long, Integer, Double types, Date types, BigDecimal,.

I was lucky, since I generate all these by using androMDA, thus it was easy to 
add XmlElement to several hundred data structures in the correct places.

It could help other JBossWS users to document the behaviour, and make it 
configurable (e.g. property nillablesAreRequired).

The situation is even worse on .net side: when a .net client reads a complex 
data structure it does not set the ...Required fields on its own. Thus 
something like


  | tradeService.updateTradePriceQuote(quotationService.getQuote(isin)) 
  | 

with a complex data structure Quote, carrying quotation detail as BigDecimals 
does not work any longer (what it used to do with JBossWS1.0.x and JSR 181 
annotations)


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4041469#4041469

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4041469
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: how to run the jbossws samples?

2007-04-21 Thread centecbertl
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] java.lang.SecurityException: Failed to authenticate 
principal=null, securityDomain=jmx-console
  | 
  | 

the JBossWS samples do not work when JMX authentication is activated (as it is 
when using the JBoss AS 4.0.5 installer per default, and as it anyway should 
always be!). For using the samples I had to disable JMX Authentication:

  | $ diff -u $JBOSS_HOME/server/default/deploy/jmx-invoker-service.xml~ 
jmx-invoker-service.xml
  | --- 
C:\Programme\jboss-4.0.5.GA/server/default/deploy/jmx-invoker-service.xml~  
2006-12-13 09:27:32.578125000 +0100
  | +++ jmx-invoker-service.xml 2007-03-07 19:52:39.132619900 +0100
  | @@ -102,8 +102,8 @@
  |  return-typejava.lang.Object/return-type
  |  descriptors
  | interceptors
  | -  interceptor 
code=org.jboss.jmx.connector.invoker.AuthenticationInterceptor
  | - securityDomain=java:/jaas/jmx-console/
  | +  !-- interceptor 
code=org.jboss.jmx.connector.invoker.AuthenticationInterceptor
  | + securityDomain=java:/jaas/jmx-console/--
  | /interceptors
  |  /descriptors
  |   /operation
  | 

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4039515#4039515

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039515
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: How to retrieve my WebServices' URLs?

2007-03-23 Thread centecbertl
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
  | ./jbossws-core/src/main/java/org/jboss/ws/core/CommonContextServlet.java
  | 

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4031001#4031001

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4031001
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: ClassCastException - jaxws webservice in jboss1.2.0

2007-03-22 Thread centecbertl
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 whether jboss runs the jbossws samples
  5. when 1...4 are running check your custom class wheter it
  fullfills all jaxb requirements (probably replace it by somthhing simplier

Hope this helps


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4030819#4030819

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4030819
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: charset encoding problem with the jsr181pojo sample : ec

2007-03-22 Thread centecbertl

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 installation (was iso latin 1 on my machine)

Has anyone found the correct way to configure the file encoding of
jbossws 1.2?

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4030830#4030830

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4030830
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: Do we actually need to download and install JBossWS?

2007-03-21 Thread centecbertl
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 no problems 
connecting .net clients to those samples.

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4030217#4030217

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4030217
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: Namespace for complex types

2007-03-14 Thread centecbertl
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, though. It works for simple complex types, 
but generates semantically incomplete wsdl when using real world classes with 
aggregation/inheriatnce from more 1 java packages.

In that case Webservice Client Generation from WSDL is complaining about the 
incorrect wsdl or even worse failing because of dis ambiguities (tried with 
.net 2.0; axis 1.4; Oracle)



View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4027861#4027861

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4027861
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: cannot call jboss ws from MS SOAP SDK

2007-03-14 Thread centecbertl
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 possible to use them in parallel?)


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4027863#4027863

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4027863
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: JBossWS-1.2.0.GA invalid wsdl generated when using @jXml

2007-03-07 Thread centecbertl
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://www.jboss.com/index.html?module=bbop=viewtopicp=4025995#4025995

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4025995
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: JBossWS-1.2.0.GA invalid wsdl generated when using @jXml

2007-03-07 Thread centecbertl
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
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - JBossWS-1.2.0.GA invalid wsdl generated when using @jXmlSche

2007-03-06 Thread centecbertl
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: 
webservice-test.ear/webservice-test.jar
  | 14:35:02,283 ERROR [JBossXSErrorHandler] 
[domain:http://www.w3.org/TR/xml-schema-1]::[key=src-resolve.4.2]::Message=src-resolve.4.2:
 Error resolving component 'ns1:aClass'. It was detected that 'ns1:aClass' is 
in namespace 'http://test.org/wsclient/a', but components from this namespace 
are not referenceable from schema document 'null'. If this is the incorrect 
namespace, perhaps the prefix of 'ns1:aClass' needs to be changed. If this is 
the correct namespace, then an appropriate 'import' tag should be added to 
'null'.


The Parameter classes causing this problem are a.AClass, b.Bclass defined in 
the packages a, and b with the following package-info.java  @XmlSchema  
annotations:

file a/package-info.java:

  | @javax.xml.bind.annotation.XmlSchema(namespace =  
http://test.org/wsclient/a; )
  | package a;
  | 

file a/AClass.java:

  | package a;
  | public class AClass {
  | int a;
  | 
  | public int getA() {
  | return a;
  | }
  | public void setA(int testInt) {
  | this.a = testInt;
  | }
  | }
  | 

file b/package-info.java:

  | @javax.xml.bind.annotation.XmlSchema(namespace =  
http://test.org/wsclient/b; )
  | package b;
  | 

file b/BClass.java

  | package b;
  | 
  | public class BClass extends a.AClass  {
  | String b;
  | 
  | public String getB() {
  | return b;
  | }
  | public void setB(String testString) {
  | this.b = testString;
  | }
  | }
  | 

The relevant part of the generated WSDL (which is visible under jbossws/service 
is:


  | xs:schema targetNamespace=http://test.org/wsclient/b; version=1.0
  |   xs:complexType name=bClass
  | xs:complexContent
  |   xs:extension base=ns1:aClass
  | xs:sequence
  |   xs:element minOccurs=0 name=b type=xs:string/
  | /xs:sequence
  |   /xs:extension
  | /xs:complexContent
  |   /xs:complexType
  | /xs:schema
  | xs:schema targetNamespace=http://test.org/wsclient/a; version=1.0
  |   xs:complexType name=aClass
  | xs:sequence
  |   xs:element name=a type=xs:int/
  | /xs:sequence
  | /xs:complexType
  | /xs:schema
  | 

where the declaration of bClass references the ns1 namespace without declaring 
it.

The same thing happens when aClass is aggreagated by bClass.

My Test Envrionment is
  JBossAS 4.0.5, JBossWS-1.2.0.GA  (compiled according to the Howto in the Wiki 
after checking out the sources from svn , installed using the projects 
deploy-jboss40 ant-target)

(PS: if this a a new issue I could provide you with the complete example 
code/maven project to reproduce the problem)

Best Regards,
Bertl

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025392#4025392

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4025392
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: (wstools/jbossws) problem generating WSDL from Java with

2007-02-06 Thread centecbertl
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 tree where some of the levels
do not add additional getter/setter properties (bug e.g. virtual methods)
will lead to a duplication of getter/setter properties in the derived levels.

Currently I am using a boolean dummy field (called jbossNoPropertyInClassBug) 
to avoid external client stub 
generators to fail on generatin valid stubs with the jboss generated 
wsdl.



View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=4011816#4011816

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4011816
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [EJB 3.0] - Re: @PrePersist @PreUpdate within @AroundInvoke results in c

2006-12-01 Thread centecbertl
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 executed on the Entity. (leaving out details on merging here! - 
thus your code shows prepersist before procedd

@PreUpdate is defined differently, though. It occurs before the database 
operation. The database operation is not exactly scheduled. It can occur due to 
a flush, or at the end of the transaction - which is after the try clause 
in your code - so the ordering of the preupdate and proceed messages in  
the result output is correct, but not guaranteed.

kr.
Bertl

View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3990476#3990476

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3990476
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: Problem using a .NET client with JBOSSWS 1.0.3

2006-10-17 Thread centecbertl
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 : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3978851#3978851

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3978851
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: Handling anyType

2006-09-13 Thread centecbertl
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 architectureand 
implementeaion of jbossws. It just adds without any checking the xmlns:xsi 
namespace to every single soap element which might go to
the Deserializer.

2. It is not checked whether the xmlns:xsi attribute is already there or worse 
pointing to a different name space already! - Clients providing a different 
xmlns:xsi uril will get bugged out!



  | Index: src/main/java/org/jboss/ws/soap/DOMEnvelopeBuilder.java
  | ===
  | --- src/main/java/org/jboss/ws/soap/DOMEnvelopeBuilder.java (revision 
942)
  | +++ src/main/java/org/jboss/ws/soap/DOMEnvelopeBuilder.java (working 
copy)
  | @@ -266,6 +266,7 @@
  |  
  | private static void redeclareNamespace(Element element)
  | {
  | +  element.setAttribute(xmlns:xsi, 
http://www.w3.org/2001/XMLSchema-instance;);
  |if(element.getPrefix()== null)
  |   element.setAttribute(xmlns, element.getNamespaceURI());
  |else
  | 
  | 

Use with care and have fun,
Bertl


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3971404#3971404

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3971404
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: Handling anyType

2006-09-12 Thread centecbertl
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 argument with nillable elements!

The problem was introduced with the update to jbossws 1.0.3 (jbossws 1.0.2 had 
no problem with the very same server and client code)

Before I start digging into the code or porting my services to a different 
web-service provider I would like to ask whethere there is any workaround/patch 
which could be applied until jbossws-1.1.0 for which the fix is scheduled is 
out? 

- downgrading to jbossws 1.0.2 is not an option due to other problems which 
were actually fixed with jbossws 1.0.3
- waiting until Oct. 31 (jbossws 1.1.0 release?) is also no option.

Many Thanks, 
Bertl


View the original post : 
http://www.jboss.com/index.html?module=bbop=viewtopicp=3971108#3971108

Reply to the post : 
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3971108
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user