Do you mean ASP or JSP? JSP certainly. ASP, as fara s I know not yet.
SCJP 1.0,1.1,2 SCJA 2
posted 20 years ago
I'm asking about ASP not JSP. Thanks for ur feedback. If u find something pls. let me know.
posted 20 years ago
You certainly cannot access EJB from ASP without having an EJB server that supports it. It would at least need to support a naming service that is suitable for COM probably. I don't know of anthing that exists at present. In your position I would consider replacing the ASP with JSP code. JSP is far superior to ASP. If you are going to the expense of purchasing an EJB server then make sure you get one that support servlets & JSP. Aaron
Interesting comment that JSP is far superior to ASP. I would appreciate it if you could elaborate a little bit on that comment. Thanks, Joe
posted 20 years ago
Benefits of JSP over ASP. Because ASP uses ActiveX controls for its components, ASP technology is basically restricted to Microsoft Windows-based platforms. Offered primarily as a feature of Microsoft IIS, ASP technology does not work easily on a broader range of Web servers because ActiveX objects are platform specific. Although ASP technology is available on other platforms through third-party porting products, to access components and interact with other services, the ActiveX objects must be present on the selected platform. If not present, a bridge to a platform supporting them is required. Not suprisingly M$ does not support this. I wonder why. Extensible JSP Tags The first difference apparent to any page author are the JSP tags themselves. While both ASP and JSP use a combination of tags and scripting to create dynamic Web pages, JSP technology enables developers to extend the JSP tags available. JSP developers can create custom tag libraries, so page authors can access more functionality using XML-like tags and depend less on scripting. With custom tags, developers can shield page authors from the complexities of page creation logic and extend key functions to a broader range of authors. Reusability Across Platforms The Java Advantage JSP technology uses the Java language for scripting, while ASP pages use Microsoft VBScript or JScript. The Java language is a mature, powerful, and scalable programming language that provides many benefits over the Basic-based scripting languages. For example, the Java language provides superior performance to the interpreted VBScript or JScript languages. Because they use Java technology and are compiled into Java servlets, JSP pages provide a gateway to the entire suite of server-side Java libraries for HTTP-aware applications. The Java language makes the developer's job easier in other ways as well. For example, it helps protect against system crashes, while ASP applications on Windows NT systems are susceptible to crashing. The Java language also helps in the area of memory management by providing protection against memory leaks and hard-to-find pointer bugs that can slow application deployment. Plus, JSP provides the robust exception handling necessary for real-world applications. Easier Maintenance Scripting languages are fine for small applications, but do not scale well to manage large, complex applications. Because the Java language is structured, it is easier to build and maintain large, modular applications with it. JSP technology's emphasis on components over scripting makes it easier to revise content without affecting logic, or revise logic without changing content. Because JSP technology is an open, cross-platform architecture, Web servers, platforms, and other components can be easily upgraded or switched without affecting JSP-based applications. This makes JSP suitable for real-world Web applications, where constant change and growth is the norm. Also, how does ASP manage conversational state for a web transaction? I believe it can only use URL rewriting. Correct me if I'm wrong.
I wouldn't make any blanket statement that JSP is superior to ASP, or vice versa. It really depends on many things, like your platform, financial resources, and developer skill set. JSP is more broadly supported by vendors than ASP and is more aligned with the OO design approach, but IMHO ASP is easier to develop and is no less robust. There are a couple of interesting articles comparing JSP vs. ASP by James Cooper in JavaPro Magazine (April and July 2000), which have generated quite a bit of interesting feedback from readers, primarily ASP developers. They are worthy of reading (not available online, unfortunately). Coming back to the original question, if you are talking about a regular JavaBean, or a regular Java class, not a EJB bean, you can certainly call it from your ASP pages on a Windows platform. The below article shows you how: http://www.asptoday.com/articles/19991227.htm Another JSP/ASP article is at: http://www.asptoday.com/articles/19991022.htm I know any time JSP/ASP comparison is made, it can create passionate debate. Just throw in my 2 cents and not to flame anyone. Eric Ma
posted 20 years ago
I just want to add that there is nothing that ASP cannot do that JSP can do. In ASP session info is managed using the built-in Session object, much like JSP's implicit session object. The use of COM components written in VB, VC++, VJ++, or Delphi works just like the custom tags in JSP. The visual studio set of tools make debugging components mauch less painful. As a side, I have not been able to deploy a .war file from Tomcat 3.1 to WebLogic 5.1. There is a certain way to go before we can say "write once, deploy anywhere" with confidence. Eric Ma
ASP vs JSP Just to let you all know.. We are in the process of migrating a FULLY M$ oriented system of COM objects, ASP pages, VB dll's etc etc into a Java solution that will eventually be using EJB components with Webshpere. To make it painless and seamless we have converted most of our COM objects to Java Classes and then just registered them on the OS. So now the "beginner/intermediate" ASP programmers are still using the ASP and the COM objects they are used to now realising they are actually Java Beans and classes registered using Javareg. I don't say this is a best approach, but once we move to FULL Java and take out the ASP part all the 'grunt' (Controller) work is already done for us. This also allows to to least effect out deliverable timelines AND totally change the underlying technology that a poorly designed system was built on. Painless and a fun topic to throw around at parties.
SOURCE CODE should be SURROUNDED by "code" tags.
What are you doing in my house? Get 'em tiny ad!
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop