Re: [Dev] WSO2 Identity Server 5.4.0 Alpha 8 Released !!!

[Johann Nallathamby]

The Public JIRA version still says Alpha-8 "unreleased". Can we fix this?
And if we are planning for Alpha-9 can we add that as new version?

Regards,
Johann.

On Fri, Nov 10, 2017 at 1:26 AM, Jayanga Kaushalya 
wrote:

> The WSO2 Identity and Access Management team is pleased to announce the
> release of WSO2 Identity Server 5.4.0 Alpha 8.
>
> You can build the distribution from the source tag
> https://github.com/wso2/product-is/releases/tag/v5.4.0-alpha8 following
> the steps below.
>
>
> *Building from the source*
>
>1. Install Java8 or above
>2. Install Apache Maven 3.x.x(https://maven.apache.org/download.cgi#)
>3. Get a clone from https://github.com/wso2/product-is.git and
>checkout to v5.4.0-alpha8 tag or you can directly download the source for
>the tag from https://github.com/wso2/product-is/releases/tag/v5.4.
>0-alpha8
>4. Run the one of the below maven commands from product-is directory,
>   - *mvn** clean install* (To build the binary and source
>   distributions with the tests)
>   - *mvn** clean install -Dmaven.test.skip=true* (To build the binary
>   and source distributions, without running any of the unit/integration 
> tests)
>5. You can find the wso2is-5.4.0-alpha8.zip binary distribution in
>product-is/modules/distribution/target directory.
>
> The following list contains all the features, improvements, and bug fixes
> available with the WSO2 Identity Server 5.4.0 Alpha 8 release.
> Patch
>
>- [IDENTITY-6883 ] -
>MalformedURLException when wreply urls has a improper url value.
>
> Bug
>
>- [IDENTITY-6307 ] -
>Auth_time is changing to session updated time
>- [IDENTITY-6875 ] - role
>claim is missing with request path authentication for saml sp configuration
>
> Improvement
>
>- [IDENTITY-6239 ] -
>Improve Facebook\Google authenticators to handle claim transformation using
>a dedicated claim dialect
>
>
> *Contribute to WSO2 Identity Server*
>
> *Mailing Lists*
>
> Join our mailing lists and correspond with the developers directly. We
> also encourage you to take part in discussions related to the product in
> the architecture mailing list. If you have any questions regarding the
> product you can use our StackOverflow forum to raise them as well.
>
>- Developer List: dev@wso2.org
>- Architecture List: architect...@wso2.org
>- User Forum: StackOverflow
>
>
> Reporting Issues
> We encourage you to report issues, improvements, and feature requests
> regarding WSO2 Identity Server through our public WSO2 Identity Server
> JIRA .
>
> ~ The WSO2 Identity and Access Management Team ~
>
> *Jayanga Kaushalya*
> Software Engineer
> Mobile: +94777860160 <+94%2077%20786%200160>
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>



-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Senior Lead Solutions Engineer
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] {ESB} - Working with CRUD Operations - Issue on Sample Proxy

[Senuwan Withana]

Hi Waruna, and Vijtha,

Thanks for help. After adding the LDAP Zip file, I could able to deploy the
proxy without any issue. Shall we update the documentation and ask to link
[1] page, as well.

[1] - https://docs.wso2.com/display/ESBCONNECTORS/LDAP+Connector


Regards,

*Senuwan Withana*
Software Engineer - Support Team | WSO2

Email : senu...@wso2.com
Mobile: 94773212853
Web: http://www.wso2.com



On Fri, Nov 10, 2017 at 10:32 PM, Vijitha Ekanayake 
wrote:

> Hi Senuwan,
>
> As per the error, synapse doesn't recognize LDAP as synapse library. Have
> you installed the Idap connector properly, if so please check whether the
> connector is enabled?
>
> Thanks.
>
> On Fri, Nov 10, 2017 at 10:14 PM, Senuwan Withana 
> wrote:
>
>> Hi Team,
>>
>> I have tried out CRUD Operations sample proxy give in [1] documentation
>> Once I tried to save it I got below exceptions into the management console,
>> I would like to know the reason of that error.
>>
>> [1] - https://docs.wso2.com/display/ESBCONNECTORS/Working+with+
>> CRUD+operations+in+LDAP
>>
>> *Error Message:-*
>>
>> [2017-11-10 22:05:10,728] ERROR - MediatorFactoryFinder Unknown mediator
>> referenced by configuration element : {http://ws.apache.org/ns/synap
>> se}ldap
>> [2017-11-10 22:05:10,730] ERROR - RPCMessageReceiver Unknown mediator
>> referenced by configuration element : {http://ws.apache.org/ns/synap
>> se}ldap
>> java.lang.reflect.InvocationTargetException
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(
>> RPCUtil.java:212)
>> at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusi
>> nessLogic(RPCMessageReceiver.java:117)
>> at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invo
>> keBusinessLogic(AbstractInOutMessageReceiver.java:40)
>> at org.apache.axis2.receivers.AbstractMessageReceiver.receive(A
>> bstractMessageReceiver.java:110)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
>> essMessage(LocalTransportReceiver.java:169)
>> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
>> essMessage(LocalTransportReceiver.java:82)
>> at org.wso2.carbon.core.transports.local.CarbonLocalTransportSe
>> nder.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
>> at org.apache.axis2.transport.local.LocalTransportSender.invoke
>> (LocalTransportSender.java:77)
>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>> at org.apache.axis2.description.OutInAxisOperationClient.send(O
>> utInAxisOperation.java:430)
>> at org.apache.axis2.description.OutInAxisOperationClient.execut
>> eImpl(OutInAxisOperation.java:225)
>> at org.apache.axis2.client.OperationClient.execute(OperationCli
>> ent.java:149)
>> at org.wso2.carbon.proxyadmin.stub.ProxyServiceAdminStub.addPro
>> xy(ProxyServiceAdminStub.java:1272)
>> at org.wso2.carbon.proxyadmin.ui.client.ProxyServiceAdminClient
>> .addProxy(ProxyServiceAdminClient.java:102)
>> at org.apache.jsp.proxyservices.submit_jsp._jspService(submit_j
>> sp.java:147)
>> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.apache.jasper.servlet.JspServletWrapper.service(JspServl
>> etWrapper.java:439)
>> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServl
>> et.java:395)
>> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
>> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.se
>> rvice(ContextPathServletAdaptor.java:37)
>> at org.eclipse.equinox.http.servlet.internal.ServletRegistratio
>> n.service(ServletRegistration.java:61)
>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce
>> ssAlias(ProxyServlet.java:128)
>> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi
>> ce(ProxyServlet.java:68)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>> at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service
>> (DelegationServlet.java:68)
>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
>> lter(ApplicationFilterChain.java:303)
>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
>> licationFilterChain.java:208)
>> at org.apache.catalina.core.ApplicationDispatcher.invoke(Applic
>> ationDispatcher.java:747)
>> at 

[Dev] [IS] Multiple stubs version in 5.4.0 pack

[Harsha Thirimanna]

Hi Devs,

We have zipped two stub versions in IS 5.4.0 pack OOB. Any special reason
for that ?

org.wso2.carbon.identity.sso.saml.stub_5.1.3.jar
org.wso2.carbon.identity.sso.saml.stub_5.3.34.jar


thanks

*Harsha Thirimanna*
*Associate Tech Lead | WSO2*

Email: hars...@wso2.com
Mob: +94715186770
Blog: http://harshathirimanna.blogspot.com/
Twitter: http://twitter.com/harshathirimann
Linked-In: linked-in:
http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 ESB500 - ws security throws exception, AxisFault, Invalid Security

[Thivya Mahenthirarasa]

Hi team,

There are five legacy operations in that services(CRUD) in the WSDL.


When I try to use basic header authentications as I mentioned above it
works. But  When I invoke the service with the GET (2 methods) I am
observing the proper response (200 ok with the output), but for the POST,
PUT, DELETE methods I'm observing 202 Accepted response with some exception
in the log.

ERROR - NativeWorkerPool Uncaught exception
java.lang.UnsupportedOperationException: An access occurred that is not
valid.
at
org.apache.axis2.description.InOnlyAxisOperation.getMessage(InOnlyAxisOperation.java:117)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:324)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:188)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:261)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)


What could be the root cause of this behavior?


On Fri, Nov 10, 2017 at 10:53 PM, Thivya Mahenthirarasa 
wrote:

> Hi guys,
>
> I'm doing a doctor app where, I need to call a web service(legacy) that
> implements ws-security, rampart, which uses username token in SSL. When
> trying to call the service following SOAP message ends up as a response in
> the ESB log with the proceeding exception.
>
>
> ERROR - AxisEngine InvalidSecurity
> org.apache.axis2.AxisFault: InvalidSecurity
> at org.apache.rampart.handler.PostDispatchVerificationHandler.invoke(
> PostDispatchVerificationHandler.java:164)
> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
> at org.apache.synapse.transport.passthru.ClientWorker.run(
> ClientWorker.java:261)
> at org.apache.axis2.transport.base.threads.NativeWorkerPool$
> 1.run(NativeWorkerPool.java:172)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> [2017-11-10 22:38:05,475] ERROR - ClientWorker Fault processing response
> message through Axis2
> org.apache.axis2.AxisFault: InvalidSecurity
> at org.apache.rampart.handler.PostDispatchVerificationHandler.invoke(
> PostDispatchVerificationHandler.java:164)
> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
> at org.apache.synapse.transport.passthru.ClientWorker.run(
> ClientWorker.java:261)
> at org.apache.axis2.transport.base.threads.NativeWorkerPool$
> 1.run(NativeWorkerPool.java:172)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
>
> but when I encode username and password in the header as follows and send
> the request it works fine.
>
>scope="transport"
>  value="Basic dGhpdnlhOnRoaXZ5YTEyMw=="/>
>
>
> I did configure the rampart module as said in this question
> .
> Have written a password callback handler class and have added it to the
> /repository/components/lib is been successfully called. I have
> written a policy file in a registry resource and doing the necessary
> configurations
>
> Your guidance is more appreciated.
>
>
> Thanks,
> Thivya
>
> --
>
> *Thivya Mahenthirarasa*
>
> *Software Engineer -Support Team | WSO2*
>
>
> *Email: thi...@wso2.com *
>
> *Mobile: +94766461966 <+94%2076%20646%201966> *
> *Web: http://wso2.com *
>



-- 

*Thivya Mahenthirarasa*

*Software Engineer -Support Team | WSO2*


*Email: thi...@wso2.com *

*Mobile: +94766461966 *
*Web: http://wso2.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Charon] Charon 3 missing password setter method for User

[Johann Nallathamby]

Any SCIM experts who can answer this query?

Regards,
Johann.

On Thu, Nov 9, 2017 at 2:35 PM, Johann Nallathamby  wrote:

> *[+IAM Team]*
>
> On Thu, Nov 9, 2017 at 2:11 PM, Isuranga Perera  > wrote:
>
>> Hi All,
>>
>> Even though Charon 2 User class has setter methods for password and other
>> attributes Charon 3 doesn't provide most of those setter methods. So is
>> there any other way I can set the password and other attributes without
>> editing the encoded user object. Appreciate any help.
>>
>> Best Regards
>> Isuranga Perera
>>
>
>
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Senior Lead Solutions Engineer
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>



-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Senior Lead Solutions Engineer
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue when running mysql db script - APIM analytics HA setup

[Mariangela Hills]

Created a JIRA to track this task.

https://wso2.org/jira/browse/DOCUMENTATION-6396

Regards,
Mariangela


*Mariangela Hills*
Associate Lead Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185


On Tue, Nov 7, 2017 at 4:22 PM, Sanjeewa Malalgoda 
wrote:

> MySQL script on default product pack do not work as expected with mysql
> 5.7.19 . Please find updated one here.
>
> Thanks
> sanjeewa.
>
> On Tue, Nov 7, 2017 at 3:39 PM, Mariangela Hills 
> wrote:
>
>> - Removing dev@wso2.org
>>
>> Ack for docs!
>>
>> Regards,
>> Mariangela
>>
>>
>> *Mariangela Hills*
>> Associate Lead Technical Writer - WSO2, Inc. http://wso2.com
>> Committer and PMC member - Apache Stratos
>> email:mariang...@wso2.com | mobile: +94 773 500185
>> 
>>
>> On Tue, Nov 7, 2017 at 3:37 PM, Damith Wickramasinghe 
>> wrote:
>>
>>> As Harsha mentioned it should be some where common to all places.
>>>
>>> Regards,
>>> Damith
>>>
>>> On Tue, Nov 7, 2017 at 3:35 PM, Harsha Kumara  wrote:
>>>


 On Tue, Nov 7, 2017 at 3:18 PM, Chamalee De Silva 
 wrote:

> Hi Damith,
>
> mysql5.7.sql script has been added for MySQL 5.7 and later versions of
> databases.
> This is clearly described in the documentation on setting up MySQL
> documentation in [1].
>
> If we are going to add this special note, we may have to add this
> everywhere where mysql is used.
>
> @team, What is the best option ?
>
 Best option would be to point to setting up database link as it
 contains required information.

>
>
> [1] https://docs.wso2.com/display/AM200/Setting+up+MySQL
>
>
> On Tue, Nov 7, 2017 at 2:20 PM, Damith Wickramasinghe <
> dami...@wso2.com> wrote:
>
>> Hi all,
>>
>> I'm using mysql version 5.7.20. In order to populate userdb and regdb
>> i need to run mysql scripts and i have used the scripts in APIM analytics
>> pack(mysql.sql). When run below issue arises,
>>
>> ERROR 1067 (42000): Invalid default value for 'REG_CREATED_TIME'
>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
>> ERROR 1067 (42000): Invalid default value for 'REG_LAST_UPDATED_TIME'
>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE_HISTORY' doesn't exist
>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE_HISTORY' doesn't exist
>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE_HISTORY' doesn't exist
>> ERROR 1146 (42S02): Table 'regdb.REG_RESOURCE' doesn't exist
>>
>> Searching the issue found out i need to run NOT mysql.sql but
>> mysql5.7.sql. So for wt version does the mysql.sql works ? versions other
>> than  5.7 ? IF so we need to mention this clearly in the
>> docs . I found the same issue has been occurred for a customer as
>> well.  I followed [1].
>>
>> [1] - https://docs.wso2.com/display/AM210/Minimum+High+Availabilit
>> y+Deployment+for+WSO2+APIM+Analytics
>>
>> Regards,
>> Damith.
>>
>> --
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> 
>> lean.enterprise.middleware
>>
>> mobile: *+94728671315 <+94%2072%20867%201315>*
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "WSO2 Documentation Group" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to documentation+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout
>> .
>>
>
>
>
> --
> Thanks & Regards,
>
> *Chamalee De Silva*
> Software Engineer
> *WS**O2* Inc. :http://wso2.com/
>
> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>
>


 --
 Harsha Kumara
 Software Engineer, WSO2 Inc.
 Mobile: +94775505618 <+94%2077%20550%205618>
 Blog:harshcreationz.blogspot.com

>>>
>>>
>>>
>>> --
>>> Senior Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> 
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94728671315 <+94%2072%20867%201315>*
>>>
>>> --
>>> You received this 

Re: [Dev] Resolving a confusion about Openid as an inbound authentication

[Nilasini Thirunavukkarasu]

Hi Shanika,

Travelocity sample allows SAML & openid (not opeinid connect). Currently we
doesn't have one sample application which accepts both (SAML & openid
connect) protocol instead we are having travelocity sample for SAML &
playground sample for openid connect. In order try openid connect hope [1]
& [2] would be helpful for you.

[1] https://docs.wso2.com/display/IS530/Basic+Client+Profile+with+Playground
[2]https://docs.wso2.com/display/IS520/Session+Management+with+Playground

One more thing, openid feature is going to be deprecated so recommended way
is to use openid connect, Still if you want to find the configuration
detail you can find it through 5.1.0 doc[3].

[3] https://docs.wso2.com/display/IS510/Configuring+OpenID+Single-Sign-On

Thanks,
Nila.


On Wed, Nov 8, 2017 at 3:56 PM, Shanika Wickramasinghe 
wrote:

> Hi All,
>
> I raised a document JIRA related to the concern that I have mentioned in
> Question 2 [1]
> When I add a service provider the name that i give for the service
> provider is automatically taken as the Openid Realm value by the Identity
> Server. With that automatically taken Openid realm value I tred to access
> the openid (3 rd link ) in the travelocity login page. Then gave a error
> message as [2]. I found a reported JIRA [3] which mention that getting the
> service provider name automatically for the openid realm value is wrong and
> JIRA says that this issue was fixed. But it seems like yet the issue is not
> fixed.
> Appreciate any guidance on what is the correct input value for the openid
> realm and how a user can find what they need to input as the openid realm
> value.
>
>
> [1]. https://wso2.org/jira/browse/DOCUMENTATION-6378?filter=14372
> [2]. openid-login-error.png
> [3]. https://wso2.org/jira/browse/IDENTITY-2443
>
> On Wed, Nov 8, 2017 at 2:20 PM, Godwin Shrimal  wrote:
>
>> Hi Shanika,
>>
>> Please see my answers to your questions.
>>
>> Question1: This is not related to OAuth/Openid Connect Configuration
>> it's about OpenID Configuration. Those are basically two inbound protocols.
>> We need to enhance the documentation if there are gaps. Please create a
>> document Jira for this.
>>
>> Question1: It allows to authenticate using OpenID protocol and you need
>> to configure OpenID Realm under OpenID Configuration. Please create a
>> document Jira for this.
>>
>> Thanks
>> Godwin
>>
>>
>> On Tue, Nov 7, 2017 at 7:13 PM, Shanika Wickramasinghe > > wrote:
>>
>>> Hi All,
>>>
>>> I am Implementing a web app called doctors app for a Hospital
>>> Management System and want to implement the Application Login Using several
>>> Identity providers such as Facebook, Yahoo and Gmail. My application need
>>> to cover multiple login protocols such as SAML SSO , OAuth/Openid Connect,
>>> passive STS as the inbound authentication for the same application. To do
>>> this I followed the following steps
>>>
>>>
>>>-
>>>
>>>Developed a web app by allowing 3 options in the login page to login
>>>with Facebook , Yahoo and Gmail
>>>-
>>>
>>>Configured the web app as the service provider in WSO2 Identity
>>>Server
>>>-
>>>
>>>Configured both SAML SSO and OAuth/Openid Connect configurations as
>>>inbound authentication
>>>
>>>
>>> Now I am trying to map both of these protocols for the same web app
>>> login by giving two options in the login page.
>>>
>>> Question 1:
>>>
>>> When I refer into the Travelocity sample, in the travelocity login page
>>> there is a option as “login with openid”.
>>>
>>> Is it some thing related to the OAuth/Openid Connect Configuration or is
>>> it the link to access when we configure Openid configuration as the Inbound
>>> authentication?
>>>
>>> This is not much clear in the document [1].
>>>
>>> Question 2:
>>>
>>> What is the purpose of having OpenID Configuration in travelocity and
>>> what that inbound config will do?
>>>
>>> It is not documented in the IS Doc [2]
>>>
>>> [1].https://docs.wso2.com/display/IS530/Configuring+Inbound+
>>> Authentication+for+a+Service+Provider
>>>
>>> [2].https://docs.wso2.com/display/IS530/Configuring+Inbound+
>>> Authentication+for+a+Service+Provider
>>>
>>>
>>> Thank You,
>>>
>>> Shanika.
>>>
>>> --
>>> *Shanika Wickramasinghe*
>>> Software Engineer - QA Team
>>>
>>> Email: shani...@wso2.com
>>> Mobile  : +94713503563 <+94%2071%20350%203563>
>>> Web : http://wso2.com
>>>
>>> 
>>>
>>
>>
>>
>> --
>> *Godwin Amila Shrimal*
>> Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
>> *
>> twitter: https://twitter.com/godwinamila
>> 
>>
>
>
>
> --
> *Shanika Wickramasinghe*
> Software Engineer - QA Team
>
> Email: shani...@wso2.com
> Mobile  : +94713503563 <+94%2071%20350%203563>
> Web : 

Re: [Dev] Exception while invoking proxy service in ESB 5.0.0

[Vijitha Ekanayake]

Hi Dilusha,

Can you provide more context about the scenario and share the complete
configurations to provide you a solution.

Thanks.

On Fri, Nov 10, 2017 at 5:29 PM, Dilusha Alphonso  wrote:

> Hi All,
>
> I am working on the scenario. where I have to create a proxy service in
> ESB 5.0.0 using a WSDL of a SOAP backend service. When I invoke the proxy
> service using SOAPUI I am getting some error.
>
>  When I invoke the service with the GET method I get the proper response,
> but for POST method I could get 202 Accepted response with some exception
> in the log.
>
> java.lang.UnsupportedOperationException: An access occurred that
> is not valid.
> at org.apache.axis2.description.InOnlyAxisOperation.getMessage(
> InOnlyAxisOperation.java:117)
> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handle
> Message(SynapseCallbackReceiver.java:324)
> at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receiv
> e(SynapseCallbackReceiver.java:188)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at org.apache.synapse.transport.passthru.ClientWorker.run(Clien
> tWorker.java:261)
> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.
> run(NativeWorkerPool.java:172)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> Executor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> lExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
>
> Could you please advice on this?
>
> Thanks
> Dilusha
> --
>
>
> *Best Regards,Dilusha Alphonso*
>
> *Software Engineer - Support Team*
>
>
> *WSO2*
> *Mobile : *
>
> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature]
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Vijitha Ekanayake
Senior Software Engineer*, *WSO2, Inc.; http://wso2.com/
Mobile : +94 777 24 73 39 | +94 718 74 44 08
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Remove provisioning-config.xml

[Ruwan Abeykoon]

Hi Gayan,
Thanks for bringing this up.
We have not planned to do so.
+1 for removing unusable config elements.
Do you know the breakdown of usable and unusable elements. Can you create
an Improvement JIRA if you know them?
Lets keep the file for now, as not we are closing Beta9, and lets update
Doc about deprecation.

Cheers,
Ruwan

On Fri, Nov 10, 2017 at 5:46 PM, Gayan Gunawardana  wrote:

> Hi All,
>
> Do we have any plan to deprecate  *provisioning-config.xml *form IS 5.4.0
> ? Most of configurations it has are unusable right now.
>  Still we use fewer configurations like [1]. IMO it is better to remove
> this configuration file.
> true
>
> [1] https://docs.wso2.com/display/IS530/Extensible+SCIM+User+
> Schemas+With+WSO2+Identity+Server
>
> Thanks,
> Gayan
> --
> Gayan Gunawardana
> Senior Software Engineer; WSO2 Inc.; http://wso2.com/
> Email: ga...@wso2.com
> Mobile: +94 (71) 8020933
>



-- 

*Ruwan Abeykoon*
*Associate Director/Architect**,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] {ESB} - Working with CRUD Operations - Issue on Sample Proxy

[Vijitha Ekanayake]

Hi Senuwan,

As per the error, synapse doesn't recognize LDAP as synapse library. Have
you installed the Idap connector properly, if so please check whether the
connector is enabled?

Thanks.

On Fri, Nov 10, 2017 at 10:14 PM, Senuwan Withana  wrote:

> Hi Team,
>
> I have tried out CRUD Operations sample proxy give in [1] documentation
> Once I tried to save it I got below exceptions into the management console,
> I would like to know the reason of that error.
>
> [1] - https://docs.wso2.com/display/ESBCONNECTORS/Working+
> with+CRUD+operations+in+LDAP
>
> *Error Message:-*
>
> [2017-11-10 22:05:10,728] ERROR - MediatorFactoryFinder Unknown mediator
> referenced by configuration element : {http://ws.apache.org/ns/
> synapse}ldap
> [2017-11-10 22:05:10,730] ERROR - RPCMessageReceiver Unknown mediator
> referenced by configuration element : {http://ws.apache.org/ns/
> synapse}ldap
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.
> java:212)
> at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(
> RPCMessageReceiver.java:117)
> at org.apache.axis2.receivers.AbstractInOutMessageReceiver.
> invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
> at org.apache.axis2.receivers.AbstractMessageReceiver.receive(
> AbstractMessageReceiver.java:110)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(
> LocalTransportReceiver.java:169)
> at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(
> LocalTransportReceiver.java:82)
> at org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.
> finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
> at org.apache.axis2.transport.local.LocalTransportSender.
> invoke(LocalTransportSender.java:77)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at org.apache.axis2.description.OutInAxisOperationClient.send(
> OutInAxisOperation.java:430)
> at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(
> OutInAxisOperation.java:225)
> at org.apache.axis2.client.OperationClient.execute(
> OperationClient.java:149)
> at org.wso2.carbon.proxyadmin.stub.ProxyServiceAdminStub.addProxy(
> ProxyServiceAdminStub.java:1272)
> at org.wso2.carbon.proxyadmin.ui.client.ProxyServiceAdminClient.addProxy(
> ProxyServiceAdminClient.java:102)
> at org.apache.jsp.proxyservices.submit_jsp._jspService(submit_
> jsp.java:147)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.apache.jasper.servlet.JspServletWrapper.service(
> JspServletWrapper.java:439)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(
> JspServlet.java:395)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(
> ContextPathServletAdaptor.java:37)
> at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(
> ServletRegistration.java:61)
> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.
> processAlias(ProxyServlet.java:128)
> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.
> service(ProxyServlet.java:68)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.
> service(DelegationServlet.java:68)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> ApplicationFilterChain.java:303)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:208)
> at org.apache.catalina.core.ApplicationDispatcher.invoke(
> ApplicationDispatcher.java:747)
> at org.apache.catalina.core.ApplicationDispatcher.doInclude(
> ApplicationDispatcher.java:603)
> at org.apache.catalina.core.ApplicationDispatcher.include(
> ApplicationDispatcher.java:542)
> at org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.
> include(RequestDispatcherAdaptor.java:37)
> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$
> RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:369)
> at org.apache.jasper.runtime.JspRuntimeLibrary.include(
> JspRuntimeLibrary.java:955)
> at org.apache.jasper.runtime.PageContextImpl.doInclude(
> PageContextImpl.java:688)
> at 

[Dev] WSO2 ESB500 - ws security throws exception, AxisFault, Invalid Security

[Thivya Mahenthirarasa]

Hi guys,

I'm doing a doctor app where, I need to call a web service(legacy) that
implements ws-security, rampart, which uses username token in SSL. When
trying to call the service following SOAP message ends up as a response in
the ESB log with the proceeding exception.


ERROR - AxisEngine InvalidSecurity
org.apache.axis2.AxisFault: InvalidSecurity
at
org.apache.rampart.handler.PostDispatchVerificationHandler.invoke(PostDispatchVerificationHandler.java:164)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:261)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
[2017-11-10 22:38:05,475] ERROR - ClientWorker Fault processing response
message through Axis2
org.apache.axis2.AxisFault: InvalidSecurity
at
org.apache.rampart.handler.PostDispatchVerificationHandler.invoke(PostDispatchVerificationHandler.java:164)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:261)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

but when I encode username and password in the header as follows and send
the request it works fine.

 


I did configure the rampart module as said in this question
.
Have written a password callback handler class and have added it to the
/repository/components/lib is been successfully called. I have
written a policy file in a registry resource and doing the necessary
configurations

Your guidance is more appreciated.


Thanks,
Thivya

-- 

*Thivya Mahenthirarasa*

*Software Engineer -Support Team | WSO2*


*Email: thi...@wso2.com *

*Mobile: +94766461966 *
*Web: http://wso2.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Exception when Publishing API in API Manager 2.1.0

[Mushthaq Rumy]

Hi Piriya,

Was there any error logged in the console. If so could you please attach
the error log?

Thanks & Regards,
Mushthaq

On Fri, Nov 10, 2017 at 5:27 PM, Piriya Sivalingam  wrote:

> Hi,
>
> I am working on a task where I have followed the below steps:
>
>
>- There is a SOAP backend which is hosted on Application Server and
>secured UT over Transport.
>- I have created a proxy service in ESB 5.0.0 having the SOAP backend
>as the endpoint of the proxy.
>- Then I followed this [1] blog to create an API in API Manager 2.1.0
>having the created ESB as the endpoint of the API.
>- According to the blog when I create the API, I couldn't publish this
>API. I could notice some exception in the Publisher UI.
>
> I am attaching a screenshot of the Publisher when it gives the exception.
> Could you please suggest me the reason for this exception and whether I
> have done something wrong here and how can I solve this issue?
>
> [1] https://medium.com/@shenavi21/exposing-a-soap-
> service-as-a-managed-rest-api-288676e06418
>
> Highly appreciate your suggestion on this.
>
> Thanks.
> --
> Regards,
>
> *Piriya Sivalingam*
>
> *Software Engineer - Support Team*
>
> *WSO2*
> *Mobile : +94 77 8462039 <+94%2077%20846%202039>*
>
> [image: http://wso2.com/signature] 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Mushthaq Rumy
*Software Engineer*
Mobile : +94 (0) 779 492140 <%2B94%20%280%29%20773%20451194>
Email : musht...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.


___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] {ESB} - Working with CRUD Operations - Issue on Sample Proxy

[Waruna Jayaweera]

Hi Senuwan,
This error normally comes when you haven't enable the connector in
management console. Can you check whether the connector has been enabled.

Thanks,
Waruna


On Fri, Nov 10, 2017 at 10:14 PM, Senuwan Withana  wrote:

> Hi Team,
>
> I have tried out CRUD Operations sample proxy give in [1] documentation
> Once I tried to save it I got below exceptions into the management console,
> I would like to know the reason of that error.
>
> [1] - https://docs.wso2.com/display/ESBCONNECTORS/Working+with+
> CRUD+operations+in+LDAP
>
> *Error Message:-*
>
> [2017-11-10 22:05:10,728] ERROR - MediatorFactoryFinder Unknown mediator
> referenced by configuration element : {http://ws.apache.org/ns/synap
> se}ldap
> [2017-11-10 22:05:10,730] ERROR - RPCMessageReceiver Unknown mediator
> referenced by configuration element : {http://ws.apache.org/ns/synap
> se}ldap
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
> ssorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
> thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(
> RPCUtil.java:212)
> at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusi
> nessLogic(RPCMessageReceiver.java:117)
> at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invo
> keBusinessLogic(AbstractInOutMessageReceiver.java:40)
> at org.apache.axis2.receivers.AbstractMessageReceiver.receive(A
> bstractMessageReceiver.java:110)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
> essMessage(LocalTransportReceiver.java:169)
> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
> essMessage(LocalTransportReceiver.java:82)
> at org.wso2.carbon.core.transports.local.CarbonLocalTransportSe
> nder.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
> at org.apache.axis2.transport.local.LocalTransportSender.invoke
> (LocalTransportSender.java:77)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at org.apache.axis2.description.OutInAxisOperationClient.send(O
> utInAxisOperation.java:430)
> at org.apache.axis2.description.OutInAxisOperationClient.execut
> eImpl(OutInAxisOperation.java:225)
> at org.apache.axis2.client.OperationClient.execute(OperationCli
> ent.java:149)
> at org.wso2.carbon.proxyadmin.stub.ProxyServiceAdminStub.addPro
> xy(ProxyServiceAdminStub.java:1272)
> at org.wso2.carbon.proxyadmin.ui.client.ProxyServiceAdminClient
> .addProxy(ProxyServiceAdminClient.java:102)
> at org.apache.jsp.proxyservices.submit_jsp._jspService(submit_j
> sp.java:147)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServl
> etWrapper.java:439)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServl
> et.java:395)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.se
> rvice(ContextPathServletAdaptor.java:37)
> at org.eclipse.equinox.http.servlet.internal.ServletRegistratio
> n.service(ServletRegistration.java:61)
> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce
> ssAlias(ProxyServlet.java:128)
> at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi
> ce(ProxyServlet.java:68)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service
> (DelegationServlet.java:68)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
> lter(ApplicationFilterChain.java:303)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
> licationFilterChain.java:208)
> at org.apache.catalina.core.ApplicationDispatcher.invoke(Applic
> ationDispatcher.java:747)
> at org.apache.catalina.core.ApplicationDispatcher.doInclude(App
> licationDispatcher.java:603)
> at org.apache.catalina.core.ApplicationDispatcher.include(Appli
> cationDispatcher.java:542)
> at org.eclipse.equinox.http.servlet.internal.RequestDispatcherA
> daptor.include(RequestDispatcherAdaptor.java:37)
> at org.eclipse.equinox.http.helper.ContextPathServletAdaptor$Re
> questDispatcherAdaptor.include(ContextPathServletAdaptor.java:369)
> at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRunti
> meLibrary.java:955)
> at org.apache.jasper.runtime.PageContextImpl.doInclude(PageCont
> extImpl.java:688)
> at 

[Dev] {ESB} - Working with CRUD Operations - Issue on Sample Proxy

[Senuwan Withana]

Hi Team,

I have tried out CRUD Operations sample proxy give in [1] documentation
Once I tried to save it I got below exceptions into the management console,
I would like to know the reason of that error.

[1] -
https://docs.wso2.com/display/ESBCONNECTORS/Working+with+CRUD+operations+in+LDAP

*Error Message:-*

[2017-11-10 22:05:10,728] ERROR - MediatorFactoryFinder Unknown mediator
referenced by configuration element : {http://ws.apache.org/ns/synapse}ldap
[2017-11-10 22:05:10,730] ERROR - RPCMessageReceiver Unknown mediator
referenced by configuration element : {http://ws.apache.org/ns/synapse}ldap
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169)
at
org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82)
at
org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
at
org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.wso2.carbon.proxyadmin.stub.ProxyServiceAdminStub.addProxy(ProxyServiceAdminStub.java:1272)
at
org.wso2.carbon.proxyadmin.ui.client.ProxyServiceAdminClient.addProxy(ProxyServiceAdminClient.java:102)
at org.apache.jsp.proxyservices.submit_jsp._jspService(submit_jsp.java:147)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:439)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:747)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:603)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:542)
at
org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.include(RequestDispatcherAdaptor.java:37)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:369)
at
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:955)
at
org.apache.jasper.runtime.PageContextImpl.doInclude(PageContextImpl.java:688)
at
org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:682)
at sun.reflect.GeneratedMethodAccessor43.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:87)
at
org.apache.tiles.jsp.context.JspTilesRequestContext.include(JspTilesRequestContext.java:88)
at

[Dev] [C4] Question on Java9 support on Carbon 4 products

[Ruwan Abeykoon]

Hi Devs,
What do we need to do to get ${subject}.
I changed "wso2server.sh"


jdk_17=`$JAVA_HOME/bin/java -version 2>&1 | grep "[(1.7)|(1.8)|9]"`
if [ "$jdk_17" = "" ]; then
   echo " Starting WSO2 Carbon (in unsupported JDK)"
   echo " [ERROR] CARBON is supported only on JDK 1.7, 1.8 or 1.9"
fi


Running with this, i get complaint from Java9,

-Djava.endorsed.dirs=xx/endorsed is not supported. Endorsed standards and
standalone APIs

in modular form will be supported via the concept of upgradeable modules.

Error: Could not create the Java Virtual Machine.


Any Idea what we can do, can we remove this from "wso2server.sh"  to get it
working?
JAVA_ENDORSED_DIRS="..."


Cheers,
Ruwan
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Remove provisioning-config.xml

[Gayan Gunawardana]

On Fri, Nov 10, 2017 at 3:19 PM, Ruwan Abeykoon  wrote:

> Hi Gayan,
> Thanks for bringing this up.
> We have not planned to do so.
> +1 for removing unusable config elements.
> Do you know the breakdown of usable and unusable elements. Can you create
> an Improvement JIRA if you know them?
> Lets keep the file for now, as not we are closing Beta9, and lets update
> Doc about deprecation.
>
AFAIK we do not use anything other than
true

>
> Cheers,
> Ruwan
>
> On Fri, Nov 10, 2017 at 5:46 PM, Gayan Gunawardana  wrote:
>
>> Hi All,
>>
>> Do we have any plan to deprecate  *provisioning-config.xml *form IS
>> 5.4.0 ? Most of configurations it has are unusable right now.
>>  Still we use fewer configurations like [1]. IMO it is better to remove
>> this configuration file.
>> true
>>
>> [1] https://docs.wso2.com/display/IS530/Extensible+SCIM+User+Sch
>> emas+With+WSO2+Identity+Server
>>
>> Thanks,
>> Gayan
>> --
>> Gayan Gunawardana
>> Senior Software Engineer; WSO2 Inc.; http://wso2.com/
>> Email: ga...@wso2.com
>> Mobile: +94 (71) 8020933
>>
>
>
>
> --
>
> *Ruwan Abeykoon*
> *Associate Director/Architect**,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
>


-- 
Gayan Gunawardana
Senior Software Engineer; WSO2 Inc.; http://wso2.com/
Email: ga...@wso2.com
Mobile: +94 (71) 8020933
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Enabling REST to SOAP sample gives an error

[Praneesha Chandrasiri]

This is applicable only to WSO2 ESB 5.0.0 and is fixed in WSO2 EI.
Therefore, updated [1] accordingly.

Thanks for the support Vijitha and Milinda!

[1] https://docs.wso2.com/display/ESB500/Configuring+Specific+Use+Cases

On Fri, Nov 10, 2017 at 5:21 PM, Vijitha Ekanayake 
wrote:

> [++ documentation]
>
> The reason for the issue seems to be, ESB is preserving the Content-Type
> header as the default behavior. Since GET request doesn't have a
> Content-Type, ESB sends application/x-www-form-urlencoded as the
> Content-Type to the backend which is the reason for this failure. To
> overcome this issue you can comment out the following parameter in the
> passthru-http.properties.
>
> http.headers.preserve=Content-Type
>
> Thanks,
> Vijitha.
>
> On Fri, Nov 10, 2017 at 5:04 PM, Vijitha Ekanayake 
> wrote:
>
>> Hi Buddhimala,
>>
>> The reason for the issue seems to be, ESB is preserving the Content-Type
>> header as the default behavior. Since GET request doesn't have a
>> Content-Type, ESB sends application/x-www-form-urlencoded as the
>> Content-Type to the backend which is the reason for this failure. To
>> overcome this issue you can comment out the following parameter in the
>> passthru-http.properties.
>>
>> http.headers.preserve=Content-Type
>>
>> Thanks,
>> Vijitha.
>>
>>
>> On Fri, Nov 10, 2017 at 4:29 PM, Buddhimala Ranasinghe <
>> buddhim...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> Today I tried out "Enabling REST to SOAP" sample in ESB as per the
>>> following wso2 document.
>>>
>>> https://docs.wso2.com/display/ESB500/Configuring+Specific+Us
>>> e+Cases#ConfiguringSpecificUseCases-EnablingRESTtoSOAP
>>>
>>> But when I tried to invoke the API using the curl command, I got
>>> following error.
>>>
>>> The endpoint reference (EPR) for the Operation not found is
>>> /services/SimpleStockQuoteService and the WSA Action = null. If this
>>> EPR was previously reachable, please contact the server
>>> administrator.
>>>
>>> And the axis2 server side it gave the following error.
>>>
>>> [2017-11-10 16:25:33,268] ERROR {org.apache.axis2.engine.AxisEngine} -
>>> The endpoint reference (EPR) for the Operation not found is
>>> /services/SimpleStockQuoteService and the WSA Action = null. If this
>>> EPR was previously reachable, please contact the server administrator.
>>> org.apache.axis2.AxisFault: The endpoint reference (EPR) for the
>>> Operation not found is /services/SimpleStockQuoteService and the WSA
>>> Action = null. If this EPR was previously reachable, please contact the
>>> server administrator.
>>> at org.apache.axis2.engine.DispatchPhase.checkPostConditions(Di
>>> spatchPhase.java:102)
>>> at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
>>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>>> at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngi
>>> ne(RESTUtil.java:144)
>>> at org.apache.axis2.transport.http.util.RESTUtil.processXMLRequ
>>> est(RESTUtil.java:89)
>>> at org.apache.synapse.transport.nhttp.util.RESTUtil.processPOST
>>> Request(RESTUtil.java:213)
>>> at org.apache.synapse.transport.nhttp.ServerWorker.processEntit
>>> yEnclosingMethod(ServerWorker.java:468)
>>> at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWo
>>> rker.java:291)
>>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.r
>>> un(NativeWorkerPool.java:172)
>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>>> Executor.java:1142)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>>> lExecutor.java:617)
>>> at java.lang.Thread.run(Thread.java:748)
>>> [2017-11-10 16:25:33,270] ERROR 
>>> {org.apache.synapse.transport.nhttp.ServerWorker}
>>> -  Error processing POST request
>>> org.apache.axis2.AxisFault: The endpoint reference (EPR) for the
>>> Operation not found is /services/SimpleStockQuoteService and the WSA
>>> Action = null. If this EPR was previously reachable, please contact the
>>> server administrator.
>>> at org.apache.axis2.engine.DispatchPhase.checkPostConditions(Di
>>> spatchPhase.java:102)
>>> at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
>>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>>> at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngi
>>> ne(RESTUtil.java:144)
>>> at org.apache.axis2.transport.http.util.RESTUtil.processXMLRequ
>>> est(RESTUtil.java:89)
>>> at org.apache.synapse.transport.nhttp.util.RESTUtil.processPOST
>>> Request(RESTUtil.java:213)
>>> at org.apache.synapse.transport.nhttp.ServerWorker.processEntit
>>> yEnclosingMethod(ServerWorker.java:468)
>>> at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWo
>>> rker.java:291)
>>> at 

Re: [Dev] TensorFlow Stream Processor Extension

[Sriskandarajah Suhothayan]

Can we agree on a conversion on naming the output.
Please share what you have decided so far.

Regards
Suho

On Fri, Nov 10, 2017 at 6:48 AM Niruhan Viswarupan  wrote:

> I could get the extension to make predictions from the KMeans saved model
> I prepared. Please find the extension here
> 
>  and
> the test case here
> 
>
> Regards,
>
>
> *Niruhan Viswarupan*
> Engineering Intern | WSO2
> Phone: +94776468013
>
> On Fri, Nov 10, 2017 at 10:42 AM, Niruhan Viswarupan 
> wrote:
>
>> [-Analytics-group, -engineering-group, + dev]
>>
>> The output tensor can be a single scalar value or a multidimensional
>> array. It totally *depends on the model* and how its output is
>> configured.
>>
>> For example,
>>
>>1. if we have a model for classification and its prediction is
>>configured to send a string of the class name then we will get a *scalar
>>(A Tensor of 0 dimension)* string tensor.
>>2. If we have a clustering model it can output the coordinates of the
>>closest centroid as a tensor which can be a *vector (A tensor of 1
>>dimension) *with any length (For example vector length will be 2 in
>>the case of Cartesian plane, 3 in the case of 3D coordinate system etc).
>>
>> *(Note:* The above examples have only a few values in output Tensors.
>> But it is possible for someone to build a TensorFlow model that sends out a
>> Tensor with thousands of dimensions and thousands of length per dimension.)
>>
>> *Terminology:*
>> eg. Consider a 3x4 *matrix (a tensor of 2 dimensions)* as below,
>>
>> 1 2 3 4
>> 5 6 7 8
>> 9 1 2 3
>> This has 2 dimensions and length of 1st dimension is 3 and the 2nd
>> dimension is 4.
>>
>> Also *problems identified in sending out multidimensional arrays in the
>> output stream* are,
>>
>>1. Its a *challenge to create primitive type multidimensional arrays*
>>(This is the type supported by Tensors copying method) whose *dimensions
>>are unknown at compile time* in Java (I welcome any suggestion as to
>>how this could be done)
>>2. As pointed out by Tishan *other extensions of Siddhi are not
>>configured to handle arrays*. So cannot process the output arrays of
>>this extension further in Siddhi
>>
>> Considering the above issues we decided to flatten the Tensor and send
>> all the values in a tensor one by one in primitive type. *In most cases
>> output Tensor will have a small number of values*.
>>
>> Regards,
>>
>> *Niruhan Viswarupan*
>> Engineering Intern | WSO2
>> Phone: +94776468013 <+94%2077%20646%208013>
>>
>> On Thu, Nov 9, 2017 at 11:41 PM, Sriskandarajah Suhothayan > > wrote:
>>
>>> Does Tensor always output multidimensional array or only for some cases?
>>> If it returns a multidimensional array what sort of processing the user
>>> should be doing to get sense out of it?
>>>
>>> My doubt is having a way to send multidimensional array out will solve
>>> the user's problem.
>>>
>>> Regards
>>> Suho
>>>
>>> On Thu, Nov 9, 2017 at 8:45 AM, Niruhan Viswarupan 
>>> wrote:
>>>
 Hi,

 This is regarding supporting predictions from TensorFlow saved models
 using stream processor.

 The *predictions (outputs) from a TensorFlow model in Java API will be
 a Tensor
 
 object*. This can have any number of dimensions and any shape. This
 means that *we will not know the shape of the output multidimensional
 array in the compile time*. This will only come to light in the run
 time when the user input model is loaded. I was stuck with creating
 multidimensional arrays of run time specified shape. It is solvable for
 object arrays since they can be recursively built. But the copyTo()
 
  method
 of Tensor works only for primitive type arrays.

 So after a discussion with Tishan we *decided to flatten the
 multidimensional Tensor* and output them as one-by-one primitive types
 that Siddhi handles. For example a 2x3 matrix Tensor [ [1,2,3], [4,5,6] ]
 will be output as 6 separate int into the event.

 Please find the *user story here
 *
  and
 the preliminary *coding works here
 *
 .

 Regards,

 

Re: [Dev] Enabling REST to SOAP sample gives an error

[Vijitha Ekanayake]

[++ documentation]

The reason for the issue seems to be, ESB is preserving the Content-Type
header as the default behavior. Since GET request doesn't have a
Content-Type, ESB sends application/x-www-form-urlencoded as the
Content-Type to the backend which is the reason for this failure. To
overcome this issue you can comment out the following parameter in the
passthru-http.properties.

http.headers.preserve=Content-Type

Thanks,
Vijitha.

On Fri, Nov 10, 2017 at 5:04 PM, Vijitha Ekanayake 
wrote:

> Hi Buddhimala,
>
> The reason for the issue seems to be, ESB is preserving the Content-Type
> header as the default behavior. Since GET request doesn't have a
> Content-Type, ESB sends application/x-www-form-urlencoded as the
> Content-Type to the backend which is the reason for this failure. To
> overcome this issue you can comment out the following parameter in the
> passthru-http.properties.
>
> http.headers.preserve=Content-Type
>
> Thanks,
> Vijitha.
>
>
> On Fri, Nov 10, 2017 at 4:29 PM, Buddhimala Ranasinghe <
> buddhim...@wso2.com> wrote:
>
>> Hi All,
>>
>> Today I tried out "Enabling REST to SOAP" sample in ESB as per the
>> following wso2 document.
>>
>> https://docs.wso2.com/display/ESB500/Configuring+Specific+Us
>> e+Cases#ConfiguringSpecificUseCases-EnablingRESTtoSOAP
>>
>> But when I tried to invoke the API using the curl command, I got
>> following error.
>>
>> The endpoint reference (EPR) for the Operation not found is
>> /services/SimpleStockQuoteService and the WSA Action = null. If this EPR
>> was previously reachable, please contact the server
>> administrator.
>>
>> And the axis2 server side it gave the following error.
>>
>> [2017-11-10 16:25:33,268] ERROR {org.apache.axis2.engine.AxisEngine} -
>> The endpoint reference (EPR) for the Operation not found is
>> /services/SimpleStockQuoteService and the WSA Action = null. If this EPR
>> was previously reachable, please contact the server administrator.
>> org.apache.axis2.AxisFault: The endpoint reference (EPR) for the
>> Operation not found is /services/SimpleStockQuoteService and the WSA
>> Action = null. If this EPR was previously reachable, please contact the
>> server administrator.
>> at org.apache.axis2.engine.DispatchPhase.checkPostConditions(Di
>> spatchPhase.java:102)
>> at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>> at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngi
>> ne(RESTUtil.java:144)
>> at org.apache.axis2.transport.http.util.RESTUtil.processXMLRequ
>> est(RESTUtil.java:89)
>> at org.apache.synapse.transport.nhttp.util.RESTUtil.processPOST
>> Request(RESTUtil.java:213)
>> at org.apache.synapse.transport.nhttp.ServerWorker.processEntit
>> yEnclosingMethod(ServerWorker.java:468)
>> at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWo
>> rker.java:291)
>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.
>> run(NativeWorkerPool.java:172)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:748)
>> [2017-11-10 16:25:33,270] ERROR 
>> {org.apache.synapse.transport.nhttp.ServerWorker}
>> -  Error processing POST request
>> org.apache.axis2.AxisFault: The endpoint reference (EPR) for the
>> Operation not found is /services/SimpleStockQuoteService and the WSA
>> Action = null. If this EPR was previously reachable, please contact the
>> server administrator.
>> at org.apache.axis2.engine.DispatchPhase.checkPostConditions(Di
>> spatchPhase.java:102)
>> at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>> at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngi
>> ne(RESTUtil.java:144)
>> at org.apache.axis2.transport.http.util.RESTUtil.processXMLRequ
>> est(RESTUtil.java:89)
>> at org.apache.synapse.transport.nhttp.util.RESTUtil.processPOST
>> Request(RESTUtil.java:213)
>> at org.apache.synapse.transport.nhttp.ServerWorker.processEntit
>> yEnclosingMethod(ServerWorker.java:468)
>> at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWo
>> rker.java:291)
>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.
>> run(NativeWorkerPool.java:172)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:748)
>>
>> Please help to resolve.
>>
>> Regards,
>> Buddhimala
>> --
>>
>>
>> *Buddhimala Ranasinghe*
>> Software Engineer-Support Team | WSO2

Re: [Dev] Enabling REST to SOAP sample gives an error

[Vijitha Ekanayake]

Hi Buddhimala,

The reason for the issue seems to be, ESB is preserving the Content-Type
header as the default behavior. Since GET request doesn't have a
Content-Type, ESB sends application/x-www-form-urlencoded as the
Content-Type to the backend which is the reason for this failure. To
overcome this issue you can comment out the following parameter in the
passthru-http.properties.

http.headers.preserve=Content-Type

Thanks,
Vijitha.


On Fri, Nov 10, 2017 at 4:29 PM, Buddhimala Ranasinghe 
wrote:

> Hi All,
>
> Today I tried out "Enabling REST to SOAP" sample in ESB as per the
> following wso2 document.
>
> https://docs.wso2.com/display/ESB500/Configuring+Specific+Use+Cases#
> ConfiguringSpecificUseCases-EnablingRESTtoSOAP
>
> But when I tried to invoke the API using the curl command, I got following
> error.
>
> The endpoint reference (EPR) for the Operation not found is
> /services/SimpleStockQuoteService and the WSA Action = null. If this EPR
> was previously reachable, please contact the server
> administrator.
>
> And the axis2 server side it gave the following error.
>
> [2017-11-10 16:25:33,268] ERROR {org.apache.axis2.engine.AxisEngine} -
> The endpoint reference (EPR) for the Operation not found is 
> /services/SimpleStockQuoteService
> and the WSA Action = null. If this EPR was previously reachable, please
> contact the server administrator.
> org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation
> not found is /services/SimpleStockQuoteService and the WSA Action = null.
> If this EPR was previously reachable, please contact the server
> administrator.
> at org.apache.axis2.engine.DispatchPhase.checkPostConditions(
> DispatchPhase.java:102)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
> at org.apache.axis2.transport.http.util.RESTUtil.
> invokeAxisEngine(RESTUtil.java:144)
> at org.apache.axis2.transport.http.util.RESTUtil.
> processXMLRequest(RESTUtil.java:89)
> at org.apache.synapse.transport.nhttp.util.RESTUtil.
> processPOSTRequest(RESTUtil.java:213)
> at org.apache.synapse.transport.nhttp.ServerWorker.
> processEntityEnclosingMethod(ServerWorker.java:468)
> at org.apache.synapse.transport.nhttp.ServerWorker.run(
> ServerWorker.java:291)
> at org.apache.axis2.transport.base.threads.NativeWorkerPool$
> 1.run(NativeWorkerPool.java:172)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> [2017-11-10 16:25:33,270] ERROR 
> {org.apache.synapse.transport.nhttp.ServerWorker}
> -  Error processing POST request
> org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation
> not found is /services/SimpleStockQuoteService and the WSA Action = null.
> If this EPR was previously reachable, please contact the server
> administrator.
> at org.apache.axis2.engine.DispatchPhase.checkPostConditions(
> DispatchPhase.java:102)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
> at org.apache.axis2.transport.http.util.RESTUtil.
> invokeAxisEngine(RESTUtil.java:144)
> at org.apache.axis2.transport.http.util.RESTUtil.
> processXMLRequest(RESTUtil.java:89)
> at org.apache.synapse.transport.nhttp.util.RESTUtil.
> processPOSTRequest(RESTUtil.java:213)
> at org.apache.synapse.transport.nhttp.ServerWorker.
> processEntityEnclosingMethod(ServerWorker.java:468)
> at org.apache.synapse.transport.nhttp.ServerWorker.run(
> ServerWorker.java:291)
> at org.apache.axis2.transport.base.threads.NativeWorkerPool$
> 1.run(NativeWorkerPool.java:172)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
>
> Please help to resolve.
>
> Regards,
> Buddhimala
> --
>
>
> *Buddhimala Ranasinghe*
> Software Engineer-Support Team | WSO2
> Emil: buddhim...@wso2.com
> Mobile:+94771563138 <+94%2077%20156%203138>
> Web:http://wso2.com
> [image: https://wso2.com/signature] 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Vijitha Ekanayake
Senior Software Engineer*, *WSO2, Inc.; http://wso2.com/
Mobile : +94 777 24 73 39 | +94 718 74 44 08
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Remove provisioning-config.xml

[Gayan Gunawardana]

Hi All,

Do we have any plan to deprecate  *provisioning-config.xml *form IS 5.4.0 ?
Most of configurations it has are unusable right now.
 Still we use fewer configurations like [1]. IMO it is better to remove
this configuration file.
true

[1]
https://docs.wso2.com/display/IS530/Extensible+SCIM+User+Schemas+With+WSO2+Identity+Server

Thanks,
Gayan
-- 
Gayan Gunawardana
Senior Software Engineer; WSO2 Inc.; http://wso2.com/
Email: ga...@wso2.com
Mobile: +94 (71) 8020933
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Exception while invoking proxy service in ESB 5.0.0

[Dilusha Alphonso]

Hi All,

I am working on the scenario. where I have to create a proxy service in ESB
5.0.0 using a WSDL of a SOAP backend service. When I invoke the proxy
service using SOAPUI I am getting some error.

 When I invoke the service with the GET method I get the proper response,
but for POST method I could get 202 Accepted response with some exception
in the log.

java.lang.UnsupportedOperationException: An access occurred that is
not valid.
at org.apache.axis2.description.InOnlyAxisOperation.getMessage(
InOnlyAxisOperation.java:117)
at org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(
SynapseCallbackReceiver.java:324)
at org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(
SynapseCallbackReceiver.java:188)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at org.apache.synapse.transport.passthru.ClientWorker.run(
ClientWorker.java:261)
at org.apache.axis2.transport.base.threads.NativeWorkerPool$
1.run(NativeWorkerPool.java:172)
at java.util.concurrent.ThreadPoolExecutor.runWorker(
ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

Could you please advice on this?

Thanks
Dilusha
-- 


*Best Regards,Dilusha Alphonso*

*Software Engineer - Support Team*


*WSO2*
*Mobile : *

*+94766837098[image: http://wso2.com/signature] *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Enabling REST to SOAP sample gives an error

[Buddhimala Ranasinghe]

Hi All,

Today I tried out "Enabling REST to SOAP" sample in ESB as per the
following wso2 document.

https://docs.wso2.com/display/ESB500/Configuring+Specific+Use+Cases#ConfiguringSpecificUseCases-EnablingRESTtoSOAP

But when I tried to invoke the API using the curl command, I got following
error.

The endpoint reference (EPR) for the Operation not found is
/services/SimpleStockQuoteService and the WSA Action = null. If this EPR
was previously reachable, please contact the server
administrator.

And the axis2 server side it gave the following error.

[2017-11-10 16:25:33,268] ERROR {org.apache.axis2.engine.AxisEngine} -  The
endpoint reference (EPR) for the Operation not found is
/services/SimpleStockQuoteService and the WSA Action = null. If this EPR
was previously reachable, please contact the server administrator.
org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation
not found is /services/SimpleStockQuoteService and the WSA Action = null.
If this EPR was previously reachable, please contact the server
administrator.
at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:102)
at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at
org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:144)
at
org.apache.axis2.transport.http.util.RESTUtil.processXMLRequest(RESTUtil.java:89)
at
org.apache.synapse.transport.nhttp.util.RESTUtil.processPOSTRequest(RESTUtil.java:213)
at
org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:468)
at
org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:291)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
[2017-11-10 16:25:33,270] ERROR
{org.apache.synapse.transport.nhttp.ServerWorker} -  Error processing POST
request
org.apache.axis2.AxisFault: The endpoint reference (EPR) for the Operation
not found is /services/SimpleStockQuoteService and the WSA Action = null.
If this EPR was previously reachable, please contact the server
administrator.
at
org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:102)
at org.apache.axis2.engine.Phase.invoke(Phase.java:329)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at
org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:144)
at
org.apache.axis2.transport.http.util.RESTUtil.processXMLRequest(RESTUtil.java:89)
at
org.apache.synapse.transport.nhttp.util.RESTUtil.processPOSTRequest(RESTUtil.java:213)
at
org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:468)
at
org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:291)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

Please help to resolve.

Regards,
Buddhimala
-- 


*Buddhimala Ranasinghe*
Software Engineer-Support Team | WSO2
Emil: buddhim...@wso2.com
Mobile:+94771563138
Web:http://wso2.com
[image: https://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API Manager 2.0.0 - Cannot add SAML inbound authentication config to Service Provider

[Prakhash Sivakumar]

Hi Chamila,

This issue is still there on AM 2.1.0 WUM updated pack as well, any plans
of getting this fixed or should I still follow the workaround?

Thanks


On Fri, Oct 21, 2016 at 10:38 AM, Chamila Adhikarinayake 
wrote:

> Hi Tharidu,
> You could use the workaround suggested in [1] .
>
> [1] http://stackoverflow.com/a/34990864/1110305
>
> Chamila
>
> On Wed, Oct 19, 2016 at 10:52 AM, Tharindu Edirisinghe  > wrote:
>
>> Thanks !
>>
>> On Wed, Oct 19, 2016 at 10:45 AM, Abimaran Kugathasan 
>> wrote:
>>
>>> Hi Tharindu,
>>>
>>> Yes, This is a known issue, yet to be fixed. Reported through [1]
>>>
>>> [1] : https://wso2.org/jira/browse/APIMANAGER-4493
>>>
>>> On Wed, Oct 19, 2016 at 10:27 AM, Tharindu Edirisinghe <
>>> tharin...@wso2.com> wrote:
>>>
 Hi Devs,

 I'm using a fresh pack of API Manager 2.0.0 and added a Service
 Provider. It got registered correctly.

 Then I edit the SP and try to add SAML inbound authentication and then
 I get an empty page. Tested this on both Firefox and Chrome and the
 behavior is same.

 Here's the backend error. Is this known issue ? or is there a patch ?


 TID: [-1234] [] [2016-10-19 10:15:36,464] ERROR
 {org.apache.tiles.jsp.context.JspTilesRequestContext} -  JSPException
 while including path '/sso-saml/add_service_provider.jsp'.
 {org.apache.tiles.jsp.context.JspTilesRequestContext}
 javax.servlet.jsp.JspException: ServletException while including page.
 at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:102)
 at org.apache.tiles.jsp.context.JspTilesRequestContext.include(
 JspTilesRequestContext.java:88)
 at org.apache.tiles.jsp.context.JspTilesRequestContext.dispatch
 (JspTilesRequestContext.java:82)
 at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesC
 ontainer.java:465)
 at org.apache.tiles.jsp.taglib.InsertAttributeTag.render(Insert
 AttributeTag.java:140)
 at org.apache.tiles.jsp.taglib.InsertAttributeTag.render(Insert
 AttributeTag.java:117)
 at org.apache.tiles.jsp.taglib.RenderTagSupport.execute(RenderT
 agSupport.java:171)
 at org.apache.tiles.jsp.taglib.RoleSecurityTagSupport.doEndTag(
 RoleSecurityTagSupport.java:75)
 at org.apache.tiles.jsp.taglib.ContainerTagSupport.doEndTag(Con
 tainerTagSupport.java:80)
 at org.apache.jsp.admin.layout.template_jsp._jspx_meth_tiles_00
 5finsertAttribute_005f7(template_jsp.java:661)
 at org.apache.jsp.admin.layout.template_jsp._jspService(templat
 e_jsp.java:377)
 at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.ja
 va:70)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
 at org.apache.jasper.servlet.JspServletWrapper.service(JspServl
 etWrapper.java:439)
 at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServl
 et.java:395)
 at org.apache.jasper.servlet.JspServlet.service(JspServlet.java
 :339)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
 at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
 at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.j
 ava:80)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
 at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.se
 rvice(ContextPathServletAdaptor.java:37)
 at org.eclipse.equinox.http.servlet.internal.ServletRegistratio
 n.service(ServletRegistration.java:61)
 at org.eclipse.equinox.http.servlet.internal.ProxyServlet.proce
 ssAlias(ProxyServlet.java:128)
 at org.eclipse.equinox.http.servlet.internal.ProxyServlet.servi
 ce(ProxyServlet.java:68)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
 at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service
 (DelegationServlet.java:68)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
 lter(ApplicationFilterChain.java:303)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
 licationFilterChain.java:208)
 at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilte
 r.java:52)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFi
 lter(ApplicationFilterChain.java:241)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(App
 licationFilterChain.java:208)
 at org.apache.catalina.core.ApplicationDispatcher.invoke(Applic
 ationDispatcher.java:747)
 at org.apache.catalina.core.ApplicationDispatcher.processReques
 t(ApplicationDispatcher.java:485)
 at org.apache.catalina.core.ApplicationDispatcher.doForward(App
 licationDispatcher.java:410)
 at org.apache.catalina.core.ApplicationDispatcher.forward(Appli
 

Re: [Dev] EI 6.0.0 and HL7 transport activation

[Thomas LEGRAND]

Hello again!

Finally, I made a diff of the directory via the command comp   (I am on Windows). So, something like that:

C:\Users\t.legrand>comp
> D:\ProjetESB\wso2ei-6.0.0-bis\wso2\components\plugins
> D:\ProjetESB\wso2ei-6.0.0\wso2\components\plugins /A > test.log
> Comparer d’autres fichiers (O/N) ? n
>

This generated a file where I could see some messages like

Comparaison de
> D:\ProjetESB\wso2ei-6.0.0-bis\wso2\components\plugins\axis2-transport-mqtt_2.0.0.wso2v1.jar
> et
> D:\ProjetESB\wso2ei-6.0.0\wso2\components\plugins\axis2-transport-mqtt_2.0.0.wso2v1.jar...
> Comparaison des fichiers OK
>
Comparaison de
> D:\ProjetESB\wso2ei-6.0.0-bis\wso2\components\plugins\org.wso2.carbon.business.messaging.hl7.common_4.6.6.jar
> et
> D:\ProjetESB\wso2ei-6.0.0\wso2\components\pluginsorg.wso2.carbon.business.messaging.hl7.common_4.6.6.jar...
>
>
Impossible de trouver/ouvrir le fichier:
> D:\ProjetESB\wso2ei-6.0.0\wso2\components\plugins\org.wso2.carbon.business.messaging.hl7.common_4.6.6.jar
>

So, in the end, the installed libraries were:

- openjpa-all_2.2.2.wso2v1
- org.wso2.carbon.business.messaging.hl7.common_4.6.6.jar
- org.wso2.carbon.business.messaging.hl7.message_4.6.6
- org.wso2.carbon.business.messaging.hl7.store.ui_4.6.6.jar
- org.wso2.carbon.business.messaging.hl7.store_4.6.6.jar
- org.wso2.carbon.business.messaging.hl7.transport_4.6.6.jar

So, I dropped those in my dropins directory, in the EI installation without
the feature installed, and that works!

Regards,

Thomas



2017-11-10 5:13 GMT+01:00 Vinod Kavinda :

> [Adding few more people]
>
> On Thu, Nov 9, 2017 at 9:27 PM, Thomas LEGRAND <
> thomas.legr...@versusmind.eu> wrote:
>
>> Hello again!
>>
>> That works nicely after I installed the thingy. But, I am behind a proxy
>> which causes problems so I had to download the whole Wilkes repository and
>> modify the elements metadataRepository & artifactRepository to point to it
>> (something like file:///to/my/local/repo). And I am disappointed because it
>> installs directly in the components directory which make the installation
>> on production a more painful. I think this is overkill to deploy a 2 Gb
>> repository to install jar (And I don't think I am the only person who think
>> that :))).
>>
>> Is there a way to extract the jars that was installed to install them
>> "manually" on another platform? Except by making a diff of the directory
>> /wso2/components? And if I copy/paster them manually, will that
>> work or P2 make some hidden configuration on the EI too?
>>
>> Regards,
>>
>> Thomas
>>
>> 2017-11-09 16:08 GMT+01:00 Thomas LEGRAND :
>>
>>> Hello Vinod,
>>>
>>> This is embarrassing... :$
>>>
>>> I did not "see" this paragraph thinking that it was just a *boring*
>>> introduction (like we have in every tutorial on the net) so I jumped
>>> directly to the "Enabling the transport" part via the summary. :$
>>>
>>> Regards,
>>>
>>> Thomas
>>>
>>> 2017-11-09 16:04 GMT+01:00 Vinod Kavinda :
>>>
 Hi Thomas,
 The HL7 feature is not shipped with EI 6 by default, due to the
 licensing issues. Did you install the HL7 feature as mentioned in the first
 paragraph of the doc [1]?

 [1] https://docs.wso2.com/display/EI600/HL7+Transport

 Regards,
 Vinod

 On Thu, Nov 9, 2017 at 4:07 PM, Thomas LEGRAND <
 thomas.legr...@versusmind.eu> wrote:

> Hello,
>
> I have a use case where I have a directory in which are dropped HL7
> messages in the ER7 format (the pipe one). So I created an inbound 
> endpoint
> which monitors this directory and eat every .hl7 file it founds. But, it
> does not know how to parse them correctly because it displays some error
> about a mistake in the file prolog (expecting a < and found a M). OK, so 
> it
> tries to read my HL7 file like if it was an XML one.
>
> So I check the doc and found that [1]. Nice! Let's try this!
>
> And... BOOM:
>
> Caused by: org.apache.axis2.deployment.DeploymentException:
> org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener
> cannot be found by axis2_1.6.1.wso2v20
> at org.apache.axis2.deployment.Ax
> isConfigBuilder.processTransportReceivers(AxisConfigBuilder.java:639)
> at org.apache.axis2.deployment.Ax
> isConfigBuilder.populateConfig(AxisConfigBuilder.java:130)
> at org.wso2.carbon.core.CarbonAxi
> sConfigurator.populateAxisConfiguration(CarbonAxisConfigurat
> or.java:341)
> at org.wso2.carbon.core.CarbonAxi
> sConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:192)
> ... 41 more
> Caused by: java.lang.ClassNotFoundException:
> org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener
> cannot be found by axis2_1.6.1.wso2v20
>
> I searched a little and I found a class [2] which seems to be in a
> business-adaptors