Re: Flex BlazeDS Missing War and

2023-07-21 Thread Abhay Singh
; configuration scripts. > > > spiros > > -Original Message- > From: Josh Tynjala [mailto:joshtynj...@bowlerhat.dev] > Sent: Wednesday, July 12, 2023 10:24 PM > To: dev@flex.apache.org > Subject: Re: Flex BlazeDS Missing War and > > Apache's version of Bl

RE: Flex BlazeDS Missing War and

2023-07-13 Thread spiros
t.dev] Sent: Wednesday, July 12, 2023 10:24 PM To: dev@flex.apache.org Subject: Re: Flex BlazeDS Missing War and Apache's version of BlazeDS doesn't offer an equivalent to Adobe's turnkey bundle. Currently, the closest thing is our "binary release", which includes the Bl

Re: Flex BlazeDS Missing War and

2023-07-12 Thread Josh Tynjala
Apache's version of BlazeDS doesn't offer an equivalent to Adobe's turnkey bundle. Currently, the closest thing is our "binary release", which includes the BlazeDS .jar files, but we don't bundle Tomcat or any samples in there at this time. If all goes well with my efforts to reintroduce updated sa

Re: Flex BlazeDS Missing War and

2023-07-12 Thread Abhay Singh
i see, thanks for the clarification. I actually referred few URL which talks about "turnkey versions of blazeds which contains ready to use version f Tomcat (version 6.0.14) in which the the BlazeDS WAR file has already been deployed and configured along with a variety sample applications.The turn

Re: Flex BlazeDS Missing War and

2023-07-12 Thread Josh Tynjala
As I understand it, BlazeDS doesn't have its own .war file. I don't think it would make much sense, since BlazeDS isn't an application on its own. It's a library that you can use as part of building an application. In other words, you need to build your own .war that contains your custom Java appli