'support' is a broad term. Can you describe want you want to do with it?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3938613#3938613
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3938613
That's a good descision. WS4EE already entered maintenance mode.
JBossWS 1.0 GA is going to be released end of month. It includes an update to
wstools. See
http://jira.jboss.com/jira/browse/JBWS?report=com.atlassian.jira.plugin.system.project:roadmap-panel.
Consuming JBossWS services from a
http://labs.jboss.com/portal/jbossws/user-guide/en/html/wssecurity.html
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3938618#3938618
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3938618
You should post these questions to an axis forum.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3938349#3938349
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3938349
---
Stub._setProperty(ENDPOINT_ADDRESS_PROPERTY,
http://tulip.imagine-com.local:12124;) should be working. You might have to
cast your Port to Stub though.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3938108#3938108
Reply to the post :
Thanks for pointing this out. Could you create JIRA issues for both cases?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3938109#3938109
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3938109
JAX-RPC 1.1 doesn't support collection types. You need to turn your collection
into an array: Collection.toArray()
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3938111#3938111
Reply to the post :
No it's not in 4.0.4CR2. It is fixed in head and will be included in 4.0.4 GA.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3937432#3937432
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3937432
JBossWS approaches 1.0.0 GA, which does focus on feature enhancements and bug
squashing. Subsequent releases will care about performance issues.
We do have a regression test suite in place that will cover the 1.0.0 release,
however it's more concerned about sanity checks then benchmarking:
It's already resolved for 1.0.0:
http://jira.jboss.org/jira/browse/JBWS-789
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3936819#3936819
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3936819
Yup, that's a bug. Feel free to create an issue for that.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3936195#3936195
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3936195
Can you supply the stacktrace?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3935743#3935743
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3935743
---
This SF.Net email
I do not know about any SOA stack. What's that supposed to contain?
- JAX-WS is on the raodmap, but will not be supported by JBossWS 1.0
- wstools will ship with subsequent releases.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3935746#3935746
Reply to the
soapenv:Client indicates that the web service client did something wrong and
should not resend the envelope. Whereas soapenv:Server means that an error
occured while processing an envelope, but it can be redelivered. It's usally
not a good idea to change these semantics, because they regarded a
Regarding your migration from JBoss 3.2.4 to JBoss 4.0.4:
What you like to share your experiences with the community?
The WIKI would be a good place for that:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWS404Compatibility
View the original post :
The example uses the JAX-WS API. It's scheduled for JBossWS 2.0:
http://weblogs.java.net/blog/jitu/archive/2006/01/web_service_end.html
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3935751#3935751
Reply to the post :
See http://hostname:port/jbossws
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3935150#3935150
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3935150
---
This SF.Net
Please check the userguide chapter and the examples:
- http://labs.jboss.com/portal/jbossws/user-guide/en/html/wssecurity.html
-
http://labs.jboss.com/portal/index.html?ctrl:id=page.default.downloadsproject=jbossws
View the original post :
Can you supply the relevant WSDL parts that describe the ports and your
webservice.xml? The WSDL type declarations would be interesting as well.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3935149#3935149
Reply to the post :
Can you post the SEI and the jaxrpc-mapping.xml?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3934648#3934648
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3934648
---
I would suggest that you migrate to JBossWS. JBossWS4EE was based on Axis,
which did not have Schema support and therefore suffered a lot from type
binding problems. These issues are resolved in the new stack, since it is fully
schema aware.
Both stacks use the same J2EE1.4 development model ,
The problem seems to be jbossws14: [synchronizeinfo] [52]: jboss/jbossws14.
Sometimes it happens that the anonymous cvs is not synchronoized (10min delay).
Did you try to run a cvs update again?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3934653#3934653
The service endpoint expect SOAP message via HTTP POST.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3934638#3934638
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3934638
HTTP GET is not the way to go. Axis (and thus the previous stack) used some RPC
hack where methodname and parameters were encoded as http parameters.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3934658#3934658
Reply to the post :
There is a 'standard-jbossws-endpoint-config.xml' within jbossws.sar/META-INF.
The security handler is configured there.
What jbossws version are you using?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3933193#3933193
Reply to the post :
Well, 'easy' is a broad term. It of course depends on your project ...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3931688#3931688
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3931688
The easiest would be to switch to jbossws and use ws-security to sign your
messages.
For detailed explanations visit:
-http://wiki.jboss.org/wiki/Wiki.jsp?page=WSDeployJBossWS
-http://wiki.jboss.org/wiki/Wiki.jsp?page=WSSecurity
View the original post :
See http://wiki.jboss.org/wiki/Wiki.jsp?page=WSClientAppl
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3931691#3931691
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3931691
The userguide will to be released soon. Until then dig the Wiki:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossWS
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3931692#3931692
Reply to the post :
I think this is fixed in Head: http://jira.jboss.org/jira/browse/JBWS-732
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3931693#3931693
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3931693
I think you got three options:
1.) use some TCP monitor
2.) provide a jaxrpc handler
3.) set the log level to DEBUG for org.jboss.ws.soap
The first option is always handy, the second one probably the most appropriate
whereas the last option is the easiest.
View the original post :
How do you deploy (package) that service? The failure looks similar to
http://jira.jboss.org/jira/browse/JBWS-669
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3927263#3927263
Reply to the post :
I guess you are talking about non-blocking RPC invocation on the client side.
The current web service stack supports JAX-RPC 1.0 which states:
anonymous wrote :
| JAX-RPC 1.0, R012
|
| A JAX-RPC runtime system is not required to support the non-blocking RPC
interaction
| mode. This
anonymous wrote : (Unsupported major.minor version 49.0)
The JDK und which you run the AS and the JDK which has been used to compile
your classes (probably the WSDP one) don't match. I think 49.0 is JDK 1.5.
- Search the forum for ways to set the WSDP JDK version, this has been
discussed
anonymous wrote : I also would like to know that when jboss is releasing
ws-notification implementation.
WS-Eventing is already supported since RC2. It addresses simliar requirements.
For further information take a look here:
http://wiki.jboss.org/wiki/Wiki.jsp?page=WSEventing
View the
Update to head, resetting any sticky tag (-A option) and then
rebuild jbossws for jdk 1.4:
| ant clean deploy-jbossws14
|
Does this answer your question?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3922247#3922247
Reply to the post :
Can you supply the WSDl aswell?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3922248#3922248
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3922248
---
This SF.net email
Take a look here:
http://www.jboss.org/index.html?module=bbop=viewtopict=75350
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3922371#3922371
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3922371
http://wiki.jboss.org/wiki/Wiki.jsp?page=WSDeployJBossWS
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3922016#3922016
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3922016
Why are you not using an EJB endpoint implementation?
It offers implicit pooling and lifecycle management.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3922019#3922019
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3922019
Switch to JBossWS.
Installation instructions can be found here:
http://wiki.jboss.org/wiki/Wiki.jsp?page=WSDeployJBossWS
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3920600#3920600
Reply to the post :
In J2EE 1.4 access to the handler registry is disallowed.
Take a look at this post:
http://www.jboss.org/index.html?module=bbop=viewtopict=75172
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3919294#3919294
Reply to the post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3878875
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3917952#3917952
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3917952
Look at this:
http://jira.jboss.com/jira/browse/JBWS-651
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3917475#3917475
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3917475
Are you Using Contact as parameter or return value within the webservice impl.?
Can you provide the source code for the webservice and the value objects?
I could imagine that, if you really have a circular dependency between Account
and Contact, schema generation might fail.
- Circular
You need to figure out if the problems occurs in the webservice stack or the
EJB/Entity part. In the latter case, this forum is probably not the right place.
Anyway the stacktrace would be useful.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3917111#3917111
46 matches
Mail list logo