7 Replies Latest reply on Nov 30, 2004 3:29 AM by starksm64

    migrate IIS to tomcat, then migrate the whole .net architect

    qbsu21th

      Dear Sir/Madam:

      Our company has the software product based on the .net
      framework with the IIS middle ware. because of the
      requirement of our current market, we need to migrate
      the whole architecture to J2ee based one.

      we plan to start with changing the presentation layer
      IIS to j2ee based one. the following are the list of
      questions we need to figure out urgently. it will be
      very appreciated if you can help on these.

      1. do you think the tomcat web server a good option
      for us or the other ones?

      2. what should be the approach we should apply to
      replace the IIS only at this stage?

      3. how can we replace IIS with tomcat on windows and
      keep all the existing binaries?

      4. if the tomcat is a good option, then after
      installing the tomcat, does the apache need to be
      installed as well? if it is, why?

      5. what is the next step for us to migrate the
      architecture to j2ee based one after replace IIS with
      tomcat?

      6. do you recommend weblogic or websphere for us at
      this stage? why?

      7. we have one staff knows only the .net architecture
      and don't know j2ee one, the other one knows only some
      of the j2ee architecture and don't know .net one. we
      want these two staff to work together to figure out a
      way to migrate from .net to j2ee in a very tight time
      frame. what can you suggest us to achieve this? what
      documentation or books we need to do this without
      recruiting additional resource?

      8. if we change the whole .net to j2ee based, what
      else we need to install, except of the tomcat? for the
      whole migration, how can we map the
      applications/components from .net to j2ee for this
      migration, like, asp.net(.net) to jsp(j2ee), iis(.net)
      to tomcat(j2ee), (sql server(.net) to oracle(j2ee)
      etc..

      it will be very appreciated if you can help on the
      above as soon as you can.

      Thanks and regards!
      David

        • 1. Extending the ActivationSpec JavaBean semantics
          qbsu21th

          I have created a JavaMail inflow resource adaptor and we only support ActivationSpecs that have String properties. If the natural type for an ActivationSpec property is not type String, then the property setter has to handle the type conversion. This seems highly non-JavaBean like given that you have to duplicate all of the PropertyEditor behavior in each non-native String setter.

          Given that these are JavaBeans as per the spec, it does not seem a big stretch to support the same semantic we do with MBeans in that we use String to bean property conversion via PropertyEditors and introspection.
          I added a generic utility method to org.jboss.util.propertyeditor.PropertyEditors

          mapJavaBeanProperties(Object bean, Properties beanProps)
           throws IntrospectionException
          


          which will do the mapping given the string/string key/value forms of the properties so this is an easy change. This is a pure superset of the existing behavior. Adrian voiced a portability concern that someone who writes a rar that works on jboss will be surprised when the same does not deploy elsewhere due to the extended behavior. I would argue that anything less is not actually supporting the JavaBean spec properly.

          I'll look at supporting this with a testcase in head. I guess the question is why should this every be disabled?


          • 2. Re: migrate IIS to tomcat, then migrate the whole .net archi
            darranl

            David,

            Tomcat is leading servlet/jsp container in the java industry. JBoss is a J2EE-1.4 compatible application server that includes tomcat in it's distribution. The Tomcat lead developer actually is a member of the JBoss core team.

            J2EE-1.4 compatibility could be crucial if your projects involves Web Services and other cutting edge technology. The JBoss APS does not have the largest market share yet, but with >5Mio downloads it is the fastes growing in the industry.

            From 10.000 feet I would suggest you send your people to a J2EE training to make sure they head of in the right direction. Ideally, if you are going JBoss this would be provided by JBoss core developers. We offer intro/admin/advanced trainings and provide development/production support at various levels.

            To give more qualified answers regrading your specific IIS based application, I would need to know more technical details.
            On this forum the JBoss community offers free technical support to people who have already opted for JBoss technology.

            Please contact JBoss Inc. to help you make your descission. They should be able to answer all your pre sales questions.




            • 3. 3857275
              starksm64

              According to the spec (and this is discutable that's why they added those styles) you have to use portlet-section- for both sections and tables.

              Using CSS you can define different styles for:

              <span class="portlet-section-header">
              

              and
              <th class="portlet-section-header">
              

              I agree that it is not great, i am not sure if we will extend the spec as many did (And is becoming a de-facto standard) or strictly follow the standard (and curiously portlets made for other portals (using portlet-table-* ) won't look the same ....

              This in open to discussion.

              • 4. Re: migrate IIS to tomcat, then migrate the whole .net archi
                thomas.diesler

                6) we recommend JBoss :)

                Please do not spam this forum. Here we discuss J2EE Web Services with JBossWS

                • 5. Re: migrate IIS to tomcat, then migrate the whole .net archi
                  thomas.diesler

                  David,

                  Tomcat is leading servlet/jsp container in the java industry. JBoss is a J2EE-1.4 compatible application server that includes tomcat in it's distribution. The Tomcat lead developer actually is a member of the JBoss core team.

                  J2EE-1.4 compatibility could be crucial if your projects involves Web Services and other cutting edge technology. The JBoss APS does not have the largest market share yet, but with >5Mio downloads it is the fastes growing in the industry.

                  From 10.000 feet I would suggest you send your people to a J2EE training to make sure they head of in the right direction. Ideally, if you are going JBoss this would be provided by JBoss core developers. We offer intro/admin/advanced trainings and provide development/production support at various levels.

                  To give more qualified answers regrading your specific IIS based application, I would need to know more technical details.
                  On this forum the JBoss community offers free technical support to people who have already opted for JBoss technology.

                  Please contact JBoss Inc. to help you make your descission. They should be able to answer all your pre sales questions.




                  • 6. Re: migrate IIS to tomcat, then migrate the whole .net archi
                    qbsu21th

                    Dear Thomas:

                    thanks for this. can i ask you for the contact detail of the Jboss Inc., like email address?

                    thanks!
                    David

                    • 7. Re: migrate IIS to tomcat, then migrate the whole .net archi
                      thomas.diesler