Thank you Alex for finding the workaround. :)
Meghana
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024700#4024700
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024700
___
Found a workaround. You can read it in the Jira issue.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024599#4024599
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024599
___
http://jira.jboss.com/jira/browse/JBWS-1553
Thanks,
Meghana
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024499#4024499
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024499
__
anonymous wrote : So I guess I need to file JIRA issue? Please let me know
which module is the correct one to file it - JBPM-BPEL or JBossWS. Also what is
the average turnaround time for fixing bugs, I know the answer depends on
various factors but some idea would be good.
Please file it under J
If operation details are not read into the javax.wsdl.Operation instance, then
the problem is neither jbpm-bpel nor jbossws, but wsdl4j. Thanks a lot for your
investigation. Now I can start with wsdl4j directly.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4
After much investigation and debugging I have confirmed that this is a bug in
JBPM-BPEL / JBossWS [ I am not sure exactly where it happens during building
partnerlinkTypes or internal to JBossWS]. It cannot read 'portType' correctly
if it comes from different namespace. I have verified this in b
I made little progress today. I downloaded branch for JBossAS 4.0.5 and trunk
for JBossWS. I built both on my machine by following instructions given here -
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQBuildAndInstall
Now when I deploy my hello process I get different exception with more deta
Hi Meghana,
I got it. Thanks for sending it.
-Alejandro
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024040#4024040
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024040
_
Hello Alex,
Since I did not hear back from you I just wanted to confirm that you received
the project file I sent you yesterday.
Thank you,
Meghana.
frostp,
Glad that I am not the only one getting that error :) Right now I am trying to
build JBossWS myself so that I can debug this problem bet
Hi,
meghanai_99, I have the same issue as you do, however I am using a schema
that's defined inside the WSDL. (Ironically I'm now thinking about using an XSD
to define my custom types!)
My project sounds pretty much like what you are trying to achieve as well
(hello world + WS call)
I have tr
I'll investigate the NPE. For JBossWS 1.0.3.SP1, the stack trace points here:
private void processOperationInput(Definition srcWsdl, Operation
srcOperation, WSDLInterfaceOperation destOperation, PortType srcPortType)
|{
| Input srcInput = srcOperation.getInput();
| if (sr
I could get wscompile to work on the client side by editing the
build.properties file in the \config folder. Only thing I had
to change war replacing with .
However on 'ant deploy' JBoss's bundled wstools takes over and I get the
exception I have posted at the start of the thread. How to I mak
If wstools fails (as in your case) please switch to wscompile and see what
happens.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4023332#4023332
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4023332
__
I tried latest release of JBossWS1.0.4GA on JBossAS 4.0.5. I followed these
installation instructions -
In order to install JBossWS the following steps are necessary:
1.) Copy lib/jbossws-client.jar to $JBOSS_HOME/client/
2.) Unzip lib/jbossws.sar to $JBOSS_HOME/server/default/deploy/
3.) Repla
Even tough JBossWS 1.0.4 is compatible with both AS branches (4.0.x and 5.0.x),
please stick to AS 4.0.5.GA for now. BPEL was not tested with AS 5.0.0.x.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022849#4022849
Reply to the post :
http://www.jboss.com/
Thank you for the reply.
Should I try new JBoss 5.0.0 Beta1? Looks like it has integrated support for
JBossWS. The reason I ask is because I don't know if the latest version of
JBossWS is compatible with JBoss 4.0.5GA. Please let me know.
Thank you,
Meghana
View the original post :
http://www
Looks like there is a bug in JBossWS. I will investigate it as soon as I have
some spare time. In the meantime, please install and test the latest JBossWS
release. You can find the distribution and installation instructions in
http://labs.jboss.com/portal/jbossws/.
View the original post :
htt
I started with 'hello' example this time and added my wsdl to that project. The
hello.wsdl looks like this
hello.wsdl
|
| http://jbpm.org/examples/hello";
| xmlns="http://schemas.xmlsoap.org/wsdl/";
| xmlns:tns="http://jbpm.org/examples/hello";
| xmlns:xsd="http://www.w3.org/200
Any idea why I am getting the null pointer exception there?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020704#4020704
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4020704
___
btw,
I could get the artifacts to generate when I replaced with
However when I run ant deploy, I get following exceptions from
JBoss. I wish it could give me more information about the operation it was
trying to read. Just operation name would have been enough to make sure if
there is someth
How do I make sure that wstools runs? The ant scripts is picking wscompile on
my machine and not running wstools. I have JBoss 4.0.5 so I was expecting it to
run wstools.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017119#4017119
Reply to the post :
http
Whenever possible use wstools instead of wscompile. We can fix the former, but
not the latter.
Bugs/feature requests specific to jax-rpc tools are more appropriately
addressed at the JBossWS or JWSDP forums.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4016
I could get wscompile to work by replacing with . But
my xsd is under same namespace as wsdl's schema so include would have been
correct choice here.
Is this a bug in wscomile?
Is this correct forum to ask this question?
Please let me know.
Thank you,
Meghana
View the original post :
http:
23 matches
Mail list logo
