I am using embedded jetty with my application, in which I migrated from 6 to 9 version, which has more complexity in terms of implementation.
For JAASUserRealm now as JAASLoginService - not sure about how to setRoleName classes for LoginSevice
tried with User,Principal, etc.,
Related
I am trying to install ColdFusion 5 but it looks like data2.cab file is missing from my copy. I understand on Adam Cameron's Dev Blog he had a copy of Coldfusion 5 from the document he wrote about installing it on Windows 7 64bit. Does anyone have a copy of the software please?
You can find installers for older versions of ColdFusion on a community maintained site: http://www.cfmlrepo.com/
I doubt you'll be able to get it up and running reliably as it's a 32-bit installer and won't run on modern Windows. It's pre-Java, so you'll also have issues with C compatibility for things like custom CFX tags. If you've got an old OS on a server somewhere, maybe you can do something with it.
What problem are you trying to address? Working on a legacy application? CF 5 should no longer be running any kind of production sites as there are a world of security issues given the modern Internet.
If possible, I'd suggest trying to run the code on the open source Lucee CFML engine https://www.lucee.org/. Depending on the complexity of your application, it won't just be a matter of setting up data sources and running the code. But in the long run, if this app needs to exist for a while more, it'll be a safer and less expensive solution.
If you have more questions about CF 5, you'll probably find more help on the CFML Slack channel. You can get an invite here: https://cfml-slack.herokuapp.com/
When I am trying to migrate to Jetty 9.4.18 from Jetty 8.1.12, I am getting errors because of following issues.
we are using org.eclipse.jetty.server.AsyncContinuation. Which is not present in Jetty 9.4.18
We are using AbstractHttpConnection. specifically AbstractHttpConnection.getCurrentConnection() method. Which is not present in Jetty 9.4.18.
We are using org.eclipse.jetty.security.MappedLoginService which is not present in Jetty 9.4.18.
we are using connector.getConnection() method. which is not present in Connector class in Jetty 9.4.18.
I did not find any documentation in Jetty upgrade page for these issues.
Welcome to Stackoverflow!
It is not a great idea to ask multiple unrelated questions on a single question.
1) we are using org.eclipse.jetty.server.AsyncContinuation. Which is not present in Jetty 9.4.18
AsyncContinuation is an Jetty 7 and older concept.
It was kept in Jetty 8 as a transition to the Servlet spec specific behaviors regarding async that were introduced in Servlet 3.0 (supported in Jetty 8.x).
Switch to using javax.servlet.AsyncContext instead. (You'll find many of the methods names to be similar, so the transition shouldn't be that problematic).
2) We are using AbstractHttpConnection. specifically AbstractHttpConnection.getCurrentConnection() method. Which is not present in Jetty 9.4.18
If you are accessing the raw Connection you will have an endless stream of issues ahead of you. The Connection object no longer represents the physical connection, it often represents a virtual connection and can mutate or be swapped out through the lifespan of a physical connection. You have failed to explain why you need this, and under what kind of situations and environments you need this.
Create a new question on stackoverflow explaining why you need this, and what goal you are attempting to solve. (not the techniques you were using before, the goal, the end result)
3) We are using org.eclipse.jetty.security.MappedLoginService which is not present in Jetty 9.4.18
The entire Security layer was refactored, without details on what you are attempting, it would be impossible to point you to the correct place to look.
Create (another) question on stackoverflow for this one too. Explain what you are attempting to solve, show some code. When detailing your question focus on the goal first, then the techniques you have attempted.
4) we are using connector.getConnection() method. which is not present in Connector class in Jetty 9.4.18.
This seems to overlap with question 3, perhaps.
But there's nothing to work with on this kind of question.
Is the Drupal 8 template engine ready for a new development?
I plan to use Drupal 8, and since I will start first with the design, I want to know if the template engine (I understand it uses Twig) will suffer significative changes that doesn't make it a good choice to start now.
Drupal 8 is currently in Beta 1, and according to the Beta 1 release notes:
Drupal 8 beta 1 for designers, translators, and documentation writers
Drupal 8's user interface, interface text, and markup are not
finalized until the first release candidate, so it's too early to
focus on user-facing documentation, translations, or themes (though by
all means, adventurous contributors should start now to provide
feedback while we can still fix things). Note that localize.drupal.org
does not yet support the full Drupal 8 API and does not have all
translatable strings.
https://www.drupal.org/drupal-8.0.0-beta1
Drupal 8 is now released. If you're looking for a couple of theming how-to overviews we've written a couple:
Custom Drupal 8 Theme + Sass, Singularity, Breakpoint, LiveReload and Gulp and Kickstarting with Drupal 8 themes.
Hope you find them helpful!
I am cleaning up a build system for a product that uses Jetty. Currently the project has
javax.servlet.jsp:jsp-api:2.1
as a dependency. Given that I am using Jetty for my project I suspect using
org.mortbay.jetty:jsp-api-2.1:6.1.5
would be the better option. Am I right/wrong? Can they be used interchangeably? Does jsp-api-2.1 leverage a different implementation? Or is it simply a repackage if jsp-api to assert compatibility with Jetty?
I've been trying to find information about this on the web, so far nothing has come up.
Update: Seems like org.mortbay.jetty:servlet-api-2.5:6.1.5 and javax.servlet.jsp:servlet-api:2.1 have the same relationship.
Jetty has a long and colorful history with jsp, having no jsp implementation of our own we have leveraged other implementations often, judging by the version numbers your looking at those are very old versions where we were maintaining patches on top of the glassfish jsp implementation. I think it was a patch for supporting logging in jetty and then a bug fix or three.
Now a days we have been using the jsp artifacts from the java.net project which was spun out from glassfish a while back. However that doesn't seem to be tracking bug fixes very regularly either so we are kicking around trying the jasper implementation in tomcat.
Back on your question, the jsp-api artifacts are typically just repackaged artifacts since the api doesn't change frequently. We historically rebundled them to keep them paired with the patched implementation.
Now, you are obviously using a jetty-6 setup since your still using org.mortbay packaging but jetty6 and jetty7 are both servlet-api 2.5 so you might be able to get away with using the jetty7 jsp setup, we have a handy pom that declares these artifacts here:
http://central.maven.org/maven2/org/eclipse/jetty/jetty-jsp/7.6.5.v20120716/jetty-jsp-7.6.5.v20120716.pom
These are glassfish bundles as well, repackaged and made into osgi bundles in the process so they can be used with jetty in osgi environments....they ought to work normally though, we package them in our jetty7 distributions.
I have an application developed with Delphi 2006 using Indy 10. Does anyone know how to add the executable file a WebService feature so users can interact with it via SOAP? I've seen that the examples provided by Delphi need to have Indy 9, and since our application depends on Indy 10, going back to 9 is not an option, and unfortunately I haven't seen any other packages to provide this functionality.
With the current release 10.5.7 of Indy (Tiburon branch) I sucessfully used this article to write a simple stand alone SOAP Server with Delphi 2009:
http://www.digicoast.com/delphi_soap_standalone.html
It should work fine with Delphi 2006 too (I am using the Indy 10 Tiburon branch even in Delphi 6).
The SOAP service can be consumed with Java (JAX-RPC) web clients, but I have not tested all possible datatypes.
What if you encapsulated your logic into an Apache module (you will end up with a TWebModule) and serve it using Apache?
I use remobjects sdk for this. IIRC it works with both Indy 9 and 10. Might be a bit expensive for you though. http://www.remobjectssdk.com/