nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Maintaing code

ProfessorX

Where do/would you let you your java developers develop the code for a WAS application?

We currently have TS doing vitalization with Websphere. Basically pointing the websphere website application package (.ear file) to the WA of TS.

This enables our content contributors to see the results of there changes
I am thinking of letting are java developers edit the java and JSP files right on TS. If they need to compile, they could do that outside of TS and then just drop the class files in to TS and restart the WAS App.

What do you think? (We are not doing EJBâ€™s)

The reason I ask is how much will this interfere with out content contributors?

I donâ€™t want to avoid maintaining another set of code on our TS Dev server.

And strategies, white papers, best practices would be much appreciated.

The Professor-

Find more posts tagged with

Comments

Migrateduser

There's an article available on DevNet that describes some best practices. It was originally written for TeamCode, but the principles apply, even if you are not using that product.

http://devnet.interwoven.com/site.fcgi/techlib/049531

lissa

Johnny

Hi James,

I noticed you mentioned you achieved WAS virtualisation (.ear) within TeamSite workareas.

Our WAS 'experts' here told us that it isnt possible to configure the approot on an per app (.ear) basis.

Would you mind sharing your experience with us as to how WAS can use another directory, (including multiple directories for each .ear) residing inside TeamSite?...

To get around this we have been using tomcat for virtualisation, which actually works pretty well, though WAS would be the preferred choice.

We are using WAS 3 & 4 for some newer apps.

Your help would be really appreciated!!

Thanks again

John Cuiuli