[jira] [Created] (AXIS2-5607) FVDCodeBaseImpl cannot be cast to CodeBase
Jürgen Weber created AXIS2-5607: --- Summary: FVDCodeBaseImpl cannot be cast to CodeBase Key: AXIS2-5607 URL: https://issues.apache.org/jira/browse/AXIS2-5607 Project: Axis2 Issue Type: Bug Components: corba Affects Versions: 1.6.2 Environment: Java 7 Reporter: Jürgen Weber Priority: Minor I tried the Exposing CORBA Services as Web Services - Introduction to the Axis2 CORBA Module sample from http://wso2.com/library/2807/ using Yoko 1.3 There seems to be an incompatibility between Yoko 1.3 and the Java 1.7 Orb, the client shows the stack trace below. I configured the corba module to use the sun orb, too, then the sample works: com.sun.corba.se.impl.orb.ORBImpl com.sun.corba.se.impl.orb.ORBSingleton Exception in thread "main" org.apache.axis2.AxisFault: com.sun.corba.se.impl.io.FVDCodeBaseImpl cannot be cast to org.omg.SendingContext.CodeBase at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:375) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165) at test.MycorbaserverStub.concat(MycorbaserverStub.java:209) at test.Client.main(Client.java:18) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
Axis2 Release Status
Hi Folks, Any idea when we can get an Axis2 release out? If Sandesha is going to take time, can we at least get Axis2 and Rampart releases soon? I believe at least Rampart release work is already well under way. Thanks, Hiranya -- Hiranya Jayathilaka Mayhem Lab/RACE Lab; Dept. of Computer Science, UCSB; http://cs.ucsb.edu E-mail: hira...@cs.ucsb.edu; Mobile: +1 (805) 895-7443 Blog: http://techfeast-hiranya.blogspot.com
[jira] [Commented] (AXIS2-5607) FVDCodeBaseImpl cannot be cast to CodeBase
[ https://issues.apache.org/jira/browse/AXIS2-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773456#comment-13773456 ] Martin Gainty commented on AXIS2-5607: -- so we can debug in the same location of the *.idl place this service definition in NameOfService.xml where NameOfService is the actual name of the service DescriptionGoesHere NameOfService.idl example::calculator corbaloc::localhost:900/NameService calculator please display contents of the following files: idl service.xml > FVDCodeBaseImpl cannot be cast to CodeBase > -- > > Key: AXIS2-5607 > URL: https://issues.apache.org/jira/browse/AXIS2-5607 > Project: Axis2 > Issue Type: Bug > Components: corba >Affects Versions: 1.6.2 > Environment: Java 7 >Reporter: Jürgen Weber >Priority: Minor > > I tried the Exposing CORBA Services as Web Services - Introduction to the > Axis2 CORBA Module > sample from http://wso2.com/library/2807/ using Yoko 1.3 > There seems to be an incompatibility between Yoko 1.3 and the Java 1.7 Orb, > the client shows the stack trace below. > I configured the corba module to use the sun orb, too, then the sample works: > com.sun.corba.se.impl.orb.ORBImpl > name="orbSingletonClass">com.sun.corba.se.impl.orb.ORBSingleton > Exception in thread "main" org.apache.axis2.AxisFault: > com.sun.corba.se.impl.io.FVDCodeBaseImpl cannot be cast to > org.omg.SendingContext.CodeBase > at > org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531) > at > org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:375) > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421) > at > org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229) > at > org.apache.axis2.client.OperationClient.execute(OperationClient.java:165) > at test.MycorbaserverStub.concat(MycorbaserverStub.java:209) > at test.Client.main(Client.java:18) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (RAMPART-331) Unreachable code in org.apache.rahas.STSMessageReceiver.invokeBusinessLogic() - "dispatcher" is never null at end of try
[
https://issues.apache.org/jira/browse/RAMPART-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Attanayake updated RAMPART-331:
--
Attachment: deadcode.png
True enough, Eclipse shows it too as a dead code.
> Unreachable code in org.apache.rahas.STSMessageReceiver.invokeBusinessLogic()
> - "dispatcher" is never null at end of try
>
>
> Key: RAMPART-331
> URL: https://issues.apache.org/jira/browse/RAMPART-331
> Project: Rampart
> Issue Type: Bug
> Components: rampart-trust
>Affects Versions: 1.5.1
> Environment: Linux / Eclipse
>Reporter: David Tonhofer
>Priority: Minor
> Attachments: deadcode.png
>
>
> At the end of "org.apache.rahas.STSMessageReceiver.invokeBusinessLogic()":
>
> if(dispatcher != null) {
> SOAPEnvelope responseEnv = dispatcher.handle(inMessage,
> outMessage);
> outMessage.setEnvelope(responseEnv);
> } else {
> throw new TrustException("missingDispatcherConfiguration");
> }
> This code is run at a point where dispatcher cannot be null; the else branch
> is dead code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (RAMPART-331) Unreachable code in org.apache.rahas.STSMessageReceiver.invokeBusinessLogic() - "dispatcher" is never null at end of try
[
https://issues.apache.org/jira/browse/RAMPART-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Attanayake updated RAMPART-331:
--
Attachment: RAMPART-331.patch
Attaching a simple patch.
> Unreachable code in org.apache.rahas.STSMessageReceiver.invokeBusinessLogic()
> - "dispatcher" is never null at end of try
>
>
> Key: RAMPART-331
> URL: https://issues.apache.org/jira/browse/RAMPART-331
> Project: Rampart
> Issue Type: Bug
> Components: rampart-trust
>Affects Versions: 1.5.1
> Environment: Linux / Eclipse
>Reporter: David Tonhofer
>Priority: Minor
> Attachments: deadcode.png, RAMPART-331.patch
>
>
> At the end of "org.apache.rahas.STSMessageReceiver.invokeBusinessLogic()":
>
> if(dispatcher != null) {
> SOAPEnvelope responseEnv = dispatcher.handle(inMessage,
> outMessage);
> outMessage.setEnvelope(responseEnv);
> } else {
> throw new TrustException("missingDispatcherConfiguration");
> }
> This code is run at a point where dispatcher cannot be null; the else branch
> is dead code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
