Hard to find ripping naming conventions

?In Mediasource Player 3.3, I had a really hard time finding the naming convention settingsdialog. It is in the media folder format settings option. I ended up with a bunch of ripped tracksthat had the track name twice and couldn't find the option. Hopefully this thread will help someoneso they don't have to struggle as much as I did. In the Settings pop-up the PC Music Library tab,and the Properties button under the first item which is the name of your current PC Music libraryname. I had failed to change the last box on the bottom right from track name to none. Ta paj692

I guess the argument against your argument is that your code should be as self-documenting as possible. In your code, I'll see "Event". Great. java.awt.Event? No (annoyance #1 already). Your base Event? I wouldn't know, need to check the imports first. Aaahh, scrolled up and saw: your special implementation Event it was. Although, I will not see that if I'm not familiar with your package structure and you're doing package imports.
Create packages for functional groups, otherwise you'll end up with loads of unnecessary public declarations because your helper classes are splattered all over the place and can't just rely on in-package visibility.
And by the way, using polymorphism properly like you don't seem to do, you'll screw yourself, because you'll in future have to do things like:
Event ev = new com.mystuff.special.implementation.Event();Because you can't import both the interface/superclass and the implementation. Congratulations.

Similar Messages

  • Naming Conventions

    Hi All
    Im new to BI implementation
    Can any1 Please Tell me the Naming Convention to be Given for a Scenario which is Completely Customised.
    Please Specify the Naming Conventions for each of the Following Objects:
    1)Datasource
    2)Infopackage
    3)Transfer Rules
    4)Infosource
    5)Update Rules or DTP
    6)DSO
    7)Update Rules
    8)Cube
    9)Multiprovider
    10)Query
    11) Infobjects
    Points are assured
    Thanks

    Hello,
    There is no specific Naming convention and it all depends how the company adopts, anyway you can use these naming conventions for better understanding
    Please find the naming convention in the end of each line
    1)Datasource - DS
    2)Infopackage - IP
    3)Transfer Rules - TR
    4)Infosource - IS
    5)Update Rules or DTP UR or DTP
    6)DSO - DSO
    7)Update Rules - UR
    8)Cube - IC
    9)Multiprovider - MP
    10)Query - QRY
    11) Infobjects - IOC (Chars)  or IOK (Keyfigures)
    Sometimes its better if your are Customizing the standard to prefix with Z .
    Example if you want to customize 0SD_C01 InfoCube, then ZSD_C01 will be easy to maintain
    Thanks
    Chandran
    Edited by: Chandran Ganesan on Mar 7, 2008 3:02 PM

  • Naming convention of calculated keyfigure

    Hi Experts,
    This is the first time we are creating any calculated keyfigure in our system and while creating we are getting authorization error. When we contacted our basis friends they told that its a naming convention issue. I want to know what would be the naming convention of a calculated key figure in our system. Can you please help me how to find this naming convention?
    Thanks in advance for your help.
    Regards,
    Brahma Reddy

    "You do not have authorization to add or create".
    This message purely indicates it is authorization issue. Work with your Basis guys to  get the required access.
    May be some of the roles are not assigned to your user id. or
    In which system you are making changes, if it is prodcution try not to make any changes and make changes in dev system and move to production system.
    Hope this helps.
    Regards,
    Reddy

  • Storage Location Naming Convention without WM!

    Dear all
    We are facing serious problem in our Storage Location for Raw Material.
    We have 4 types of Raw Material Seating (S), Panel (P), Metal (M), Wood (W). And they are all stored under Storage Location: RWSL.
    Requirement:
    Although we have visual guideline as to which industrial rack will store the type of Material, it is insufficient. We need a more refined storage location down to which BIN of the rack we will put the Raw Material.
    Due to limited time and resource, we cannot have WM implemented right now. Thus, we have come out with 2 alternative to overcome this problem:
    Alternative 01:
    We will use the Fixed Bin field in Storage Data 02 by putting the Bin number assigned to each Rack.
    E.g. For Seating material code:SEAT01, we will maintain the Fixed Bin as R12A01/A02, it means this Seating material SEAT01 will be stored at Rack 12, fixed bin A01 or A02.
    Question to Alternative 01: Will it cause problem in GR, GR, Transfer Posting and Stock Count?
    Alternative 02:
    Instead of going into details to put Fixed Bin field in Storage Data 2, we will abandan the existing Storage Location RMSL by introducing new format for Storage Location
    Here is the example of Alternative 02:
    For raw materials, we will use 4 digits location numbers, consistent with other Storage locations, the 4 digits storage location will start with u201CR _ _ _u201D to represent each location
    And,
    R _ _ _ is:
    R = Raw materials
    2nd digit = Division (S= Seating, P =Panel, W=Wood, M=Metal and W=Wood)
    3rd digit = Rack Number (A, B, C, Du2026 and etc.)
    4th digit = Rack Zone - each rack will broken down into zone, each rack can possibility have 2 to 3 zone. 1 Zone can be 1 colume of the Rack
    An example of a possible location and its meaning will be
    RSA1 = Raw materials warehouse, Seating division, Rack A, Zone 1
    RPB3 = Raw materials warehouse, Panel Division, Rack B, Zone 3
    The challenge of this is that instead of having 1 Raw Material Storage Location like RMSL, we will have a lot more storage locations each for division of Raw material due to the Rack Number we have as well as the Rack Zone.
    Question to Alternative 02:
    If we use this alternative, will it impact our future implementation of WM? From design wise, is it feasible?
    Please advise what is the best approach and the feasible design on it.
    Many thanks in advance.
    Edited by: Daimos on May 13, 2009 10:15 AM

    Hi, here is the Pro and Co of both approaches:
    Method 01: Use existing SLOC and add the Storage Bin info
    e.g. SLOC: STM1
             Storage Bin: RSC3, where RS = Rack Seating, C3 = column 3
    Pro 01:
    It will cause less effort as we only need to use LSMW for material master to add in the Storage Bin data for all material of SCM.
    Pro 02:
    I have tested out that in TCode MIGO, apart from SLOC, the pertaining Storage Bin data also appear.  Based on my discuss with Xian Chen, sometimes they use MB1C(GR), MB1A(GI) rather than MIGO due to speed issue, I will need to check the field status if can have Storage Bin field APPEAR, if can, it will solve the problem
    Con 01:
    The Storage Bin information will only appear in MMBE (Stock Overview) but will not appear in the standard SAP Inventory Report (e.g. MB52 Warehouse Stock). To view it from SAP Inventory Report, we may need to customize the standard report to show the new field Storage Bin. It needs Abap effort.
    Con 02:
    We must have a very good naming convention for Storage Bin. And again, in the above example, if a material is put in SLOC STM1 at Storage Bin RA A1 or C4, it will set a very rigid rule in the future if we need to change it, as I fear that one the Storage Bin has been used up. It will not allow us to change (need to do testing to find out)
    Con 03:
    Do we have the time to define all the Storage Bin for each SLOC? Operation wise, the store personnel needs to design it
    Method 02: Use the new SLOC
    Pro 01:
    RSA1 = Raw materials warehouse, Seating division, Rack A, Zone 1. More organized. Easy to tell the material is at which  Rack and which Zone of the Rack.
    Assumption:
    01. we must not have too many rack for one Seating division and also not too many Zone for each
          Division, else it will cause confusion
    02. 1 material should stick to 1 Rack 1 zone as much as possible, else later the PP consultant will 
         have hard to to perform GI due to too many SLOC assigned to a material.
    Pro 02:
    In report wise, we are able to show the SLOC in inventory report. No need to enhance the existing inventory report as we do not use Storage Bin.
    Con 01:
    If there are too many SLOC creation due to it. It may cause problem for PP perform GI as too many selection available for a material. This can be avoided if stick to the General Rule that one material is tied with one SLOC.
    Edited by: Daimos on May 16, 2009 5:07 AM

  • How to create new check for SELECT* , Naming conventions etc..

    Hi all,
       I would like have a solution for the below checks are possible or not in ABAP - CODE INSPECTOR. If possible can you please give me the solution..
    a). Performance checks i.e, SELECT* , LOOP without field strings, FOR ALL ENTRIES IN SELECT STATEMENT.
    b). Custom naming conventions.
    c). to check if further modularization can be done in the program,
    d). also the coding standards.
    PLEASE help me , i am struck with it for long time in getting the solution...

    > a). Performance checks i.e, SELECT* , LOOP without field strings, FOR ALL ENTRIES IN SELECT STATEMENT.
    > b). Custom naming conventions.
    > c). to check if further modularization can be done in the program,
    > d). also the coding standards.
    the code inspector allows the creation of new checks, you should consult the documentation how to do it.
    The main problem of the code inspector are hits, which are actually no problem. And I think this is a problem with your checks:
    + SELECT*  this is no performance problem, only in cases when the table is really wide then a field list makes sense, i.e your check
       will find a lot of false hits
    + LOOP without field strings  ... you mean fs =field symbols, same as with SELECT *
    + FOR ALL ENTRIES IN SELECT STATEMENT   ???? FOR ALL ENTRIES is fine
    + Custom naming conventions  ... hmmm be more precise, I think it can be hard
    + to check if further modularization can be done in the program,
        before you want to program can you please explain how you check manually .... I would be interested
    +  also the coding standards.   .... what is that?

  • Is it possible to control the naming convention used by Aperture when importing photos?  If so, how

    When I import photos from my camera, I have them placed into projects based on the date the photos were taken. However, I do not like the naming convention used by Aperture as it causes the projects to sort into a non-chronologial order. The convention is MMM-DD-YYYY and I want to change it to YYYY-MM-DD. Is it possible in Aperture 3.2.4 to do this?

    In the Import  panel you can edit the preset for the file name format to "Image year - image month - image day - index" for example; the preset for folder names seems to be gone in Aperture 3,3 - at least I cannot find it any longer. You only seem to be able to enter the folder name manually in the Import panel.

  • Looking for best practice on naming conventions

    Does anyone out there have a best practice on naming conventions that they could share.
    I'm starting to find the need to create objects and associated variables and actions.
    I can see this getting very messy, very quickly and would love to learn if someone has come up with a good set of guidelines that are both easy to follow and make perfect sense. (I know....what a balance to ask for!)
    Thanks
    Alan

    Hi Alan,
    Welcome to Adobe Community.
    There are couple of things that you can keep in mind while naming objects.
    When creating custom text caption styles, be sure to follow the correct naming conventions. Each caption style has a unique name, and you must
    use this name at the beginning of each associated bitmap filename. For example, if you create a text caption style named “Brightblue,” the five
    bitmap images that constitute the new style should be named as follows:
    Brightblue1.bmp, an image with no callouts
    Brightblue2.bmp, an image with a callout to the right or upper-right
    Brightblue3.bmp, an image with a callout to the left or upper-left
    Brightblue4.bmp, an image with a callout to the lower right
    Brightblue5.bmp, an image with a callout to the lower left
    Flash button-naming conventions
    Each SWF button contains three layers: a button, an icon, and an action layer.
    The SWF filename consists of the following elements:
    Acronym for playback control (“pbc”)
    Playback element identifier (“Btn” for button, “Bar” for bar, and so on)
    Name of the button (“play”).
    Hope this helps!
    Thanks!

  • AppleScript To Save Messages As PDFs With Specific Naming Convention

    I am looking for an Applescript that:
    1: Prompts and allows the user to select one or more Apple Mail email messages from within Mail (10.4, 10.5, 10.6).
    2: Prompts and allows the user to select a save-to folder.
    3: For each message, saves it as a PDF file in the save-to folder, using the following naming convention for the PDF file:
    "YYYY-MM-DD HH.MM.SS Email From FIRSTNAME LASTNAME - SUBJECT",
    "YYYY-MM-DD HH.MM.SS Email To FIRSTNAME LASTNAME - SUBJECT",
    where in the email date-sent stamp (if I am the sender) or date-received stamp (if I am the recipient):
    YYYY = the year
    MM = the two-digit month
    DD = the two-digit day
    HH = the two-digit hour (in 24-hour time)
    MM = the two-digit minute
    SS = the two-digit second
    FIRSTNAME is the email sender's first name for email that I receive (or is the email recipient's first name for email that I send)
    LASTNAME is the email sender's last name for email that I receive (or is the email recipient's first name for email that I send)
    SUBJECT = the email's subject line
    For example: 2010-04-10 16.32.48 Email From Kris Ryan - Status Of Payroll Updates.pdf
    For example: 2010-04-10 16.33.55 Email To Sue Anderson - RE Status Of Payroll Updates.pdf (Colon omitted after "RE".)
    4: For each attachment to the message, saves it as a PDF file in the same directory using the naming convention:
    "YYYY-MM-DD HH.MM.SS Email From FIRSTNAME LASTNAME Z Attachment - NUMBER - FILENAME",
    where:
    YYYY-MM-DD HH.MM.SS Email From FIRSTNAME LASTNAME = as above
    NUMBER = an integer representing the attachment number (1, 2, ...) sorted according to filename alphabetical order
    FILENAME = the name of the file attached to the email, including its extension (.docx, .xlsx, etc.)
    The letter "Z" sorts the attachment PDFs after its respective parent email in the directory.
    For example: 2010-04-10 16.32.48 Email From Kris Ryan Z Attachment - 1 - List Of Suggestions To Moore.doc.pdf
    For example: 2010-04-10 16.32.48 Email From Kris Ryan Z Attachment - 2 - Proposed Salary Adjustments.xls.pdf
    For example: 2010-04-10 16.32.48 Email From Kris Ryan Z Attachment - 3 - Salary History.pps.pdf
    Note: The email attachment may consist of a PDF or MS Office file (Word, Excel, Power Point); however, a smart implementation will be able to handle any attachment kind. If the attachment is a PDF file, then save it "as is" using the stipulated naming convention, without passing it through Distiller.
    Thank you.
    Kurt Todoroff

    Well, that's quite a spec sheet.
    Here's a start, you can easily edit the script to get what you need:
    <pre style="
    font-family: Monaco, 'Courier New', Courier, monospace;
    font-size: 10px;
    font-weight: normal;
    margin: 0px;
    padding: 5px;
    border: 1px solid #000000;
    width: 720px; height: 340px;
    color: #000000;
    background-color: #E6E6EE;
    overflow: auto;"
    title="this text can be pasted into the AppleScript Editor">
    Set a Mail Rule to Save Message and Attachment to Desktop.
    To save attachments to another another folder on the desktop (i.e. Attachments) create the folder and then
    change tell application "Finder" to set pathToAttachments to (path to desktop folder as string) & "Attachments:"
    using terms from application "Mail"
    on perform mail action with messages theMessages
    tell application "Finder" to set ptd to (path to desktop folder) as string
    tell application "Finder" to set pathToAttachments to (path to desktop folder) as string
    tell application "Mail"
    repeat with theMessage in theMessages
    set d_recd to date received of theMessage as string
    set d_recd to ReplaceText(d_recd, ":", " ") of me
    set d_recd to ReplaceText(d_recd, ",", " ") of me
    set theText to content of theMessage
    if theMessage's mail attachments is not {} then
    repeat with theAttachment in theMessage's mail attachments
    set theFileName to pathToAttachments & (theMessage's subject) & " (Attachment From " & (theMessage's sender) & " Sent " & d_recd & ")" & space & theAttachment's name
    try
    save theAttachment in theFileName
    on error errnum
    end try
    end repeat
    end if
    set theFile to ptd & (theMessage's subject) & " (From " & (theMessage's sender) & " Sent " & d_recd & ")" & ".txt"
    set theFileID to open for access file theFile with write permission
    write theText to theFileID
    close access theFileID
    end repeat
    end tell
    end perform mail action with messages
    end using terms from
    on ReplaceText(theString, fString, rString)
    set current_Delimiters to text item delimiters of AppleScript
    set AppleScript's text item delimiters to fString
    set sList to every text item of theString
    set AppleScript's text item delimiters to rString
    set newString to sList as string
    set AppleScript's text item delimiters to current_Delimiters
    return newString
    end ReplaceText</pre>

  • Variable naming conventions

    Hi all,
    I come from a mostly JAVA background. Big emphasis in that arena on encapsulation and modularization of code to help facilitate ease of maintenance and reuse...in theory I sometimes struggle with variable naming conventions within my ABAP code because I'm not all together certain there are any. In C or C++ I might use a derivation of Hungarian notation to name varaibles...and in JAVA I might observe certain object oriented rules regarding varaible naming...I find myself using a combination of those two protocols in my ABAP code. Does anyone have any suggestions for how I might name global and lcoal variables within my code?
    regards,
    Mat

    Hi,
    Please check this links perhaps they may help.
    http://help.sap.com/saphelp_nw04/helpdata/en/92/c2b084bc1d11d2958700a0c94260a5/content.htm
    https://websmp101.sap-ag.de/~sapdownload/011000358700004455192006E/NameConventions.pdf
    http://help.sap.com/saphelp_nw04/helpdata/en/2a/6b0b1f547a11d189600000e829fbbd/content.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/011ccf90-0201-0010-92a7-b319adf89b73
    http://web.mit.edu/sapr3/dev/newdevstand.html
    Regards,
    Ferry Lianto

  • JSP Naming Convention in JIT/JFF

    Any kind of naming standards they follow in naming the JSPs ? I'm finding pretty long named confusing JSP file names. The first 3 character was the module name "qot" , that was one information i could understand from :-)

    yes i tried . it is working . but it looks very odd in the URL and i did not see any site that contains the _(underscore )
    in their file name.
    But still i am not sure whether i use it or not . Because I have less idea about naming convention of jsp apges

  • Logical System Naming Convention

    Hi Guruz,
    Is it mandatory to name your logical system starting with SAP system name. I went through SAP Documentation for creating logical system, it says <sap system name>CLNT<client number>. I didn't put my SAP system name for the first part<sap system name> instead some random letters. I know this question may sound stupid but I am right now in the middle of the integration so, I don't want to change it. Please confirm.

    I'm work for the customer who has ~4000 logical systems defined (not all represent SAP boxes though). Which I find quite a lot, yet given the rules of naming convention helps a lot.
    I would say that having the system name should be used whenever we talk about Logical Systems representing SAP boxes. But in case of external non-SAP applications, it is helpful to represent them by the external system.
    Say, you have 20 SAP installations, each sending interface to application A. Then it is easier to monitor in XI/PI interfaces for single receiving logical system 'A'. But if you want to find out messages from given sending SAP system, then using SAP system name is recommended to extract such data quickly.
    Regards,
    Dominik Modrzejewski

  • SAP Naming Conventions for DB Data Files

    Hi Everyone!
    We are about to install a SAP ECC 6.0 SR3 ABAP on Windows Server 2008 (R2) & SQL Server 2008 SP1 and we want to name the DB data files as follows:
    <sid>DB_Data_001.MDF/NDF
    Do you see any problem with this or think this could lead to a problem in the future?
    We were unable to find a SAP note or SAP recommendation about this, we only found SAP Note 27428 but itu2019s for Oracle.
    Thanks in advance!
    Best Regards,
    Nicolas

    Hi Nicolas,
    I thought about all corners where this could possibly lead to a problem (e.g. monitoring, DB13, ...) but couldn't think of a single report or transaction where this would cause problems.
    To the database itself the names of the files do not matter at all and in the SAP transactions the datafiles are only read to display them in monitoring transactions like DB02 or RZ20. These transaction do not expect a certain naming convention so I don't see anything that would count against using different filenames.
    Regards,
    Beate Grötschnig

  • ADF BC naming convention suggestions

    Ok, I havent found too many topics on this matter, but here is a list of naming conventions our team is debating over. I would also like to hear the rest of the community's thoughts.
    Entity: Use underlying table's name and postfix with Eo. If the table is a W view, it should prefix with W.
    eg. EmployeeEo, WEmployeeEo
    View Object (Single entity based): Use the Entity's name postfix with Vo.
    eg. EmployeeVo, WEmployeeVo
    View Object (Multiple entity based): Use the primary entity's name followed by a "busniess task" name.
    eg. DepartmentEmployeeSearchVo (employee search being the task).
    View Object (Non-entity based): Use the primary query table name followed by a "busniess task" name.
    eg.EmployeeCountVo
    View Link & Association: Combine the master entity name and child entity name postfix with Vl/Ao.
    eg. DepartmentEmployeeVl, DepartmentEmployeeAo
    (The issue with this is our legacy tables are not that intuitivly named, so its hard to distinguish the master/child tables. I was thinking of splitting it with lets say 2, like Department2EmployeeVl)
    Application Module: Apply a "busniess process" name and suffix with AppModule.
    eg. AcmeAccountingAppModule.
    If anyone has any suggestions or see any conventions left out please post them.
    Thanks,
    Z

    Without discounting your object name conventions, don't forget the Java package they are placed in helps gives context for the object. This is what I tend to do:
    com.acme.appmodules
    com.acme.entities (all entities)
    com.acme.entities.associations
    com.acme.views (common VOs)
    com.acme.views.links (common VO links)
    com.acme.views.reference (common read only VO lookups)
    com.acme.views.<business task> (to group logical business VOs together)
    com.acme.views.<business task>.links
    ...the last 2 are repeated for each business task area (eg. HR, accounts, etc)
    My ideas partially based on the SRDemo from the JDev team.
    Hope this helps.
    CM.

  • Question about Best Practices - Redwood Landscape/Object Naming Conventions

    Having reviewed documentation and posts, I find that there is not that much information available in regards to best practices for the Redwood Scheduler in a SAP environment. We are running the free version.
    1) The job scheduling for SAP reference book (SAP Press) recommends multiple Redwood installations and using export/import to move jobs and other redwood objects from say DEV->QAS->PROD. Presentations from the help.sap.com Web Site show the Redwood Scheduler linked to Solution Manager and handling job submissions for DEV-QAS-PROD. Point and Shoot (just be careful where you aim!) functionality is described as an advantage for the product. There is a SAP note (#895253) on making Redwood highly available. I am open to comments inputs and suggestions on this issue based on SAP client experiences.
    2) Related to 1), I have not seen much documentation on Redwood object naming conventions. I am interested in hearing how SAP clients have dealt with Redwood object naming (i.e. applications, job streams, scripts, events, locks). To date, I have seen in a presentation where customer objects are named starting with Z_. I like to include the object type in the name (e.g. EVT - Event, CHN - Job Chain, SCR - Script, LCK - Lock) keeping in mind the character length limitation of 30 characters. I also have an associated issue with Event naming given that we have 4 environments (DEV, QA, Staging, PROD). Assuming that we are not about to have one installation per environment, then we need to include the environment in the event name. The downside here is that we lose transportability for the job stream. We need to modify the job chain to wait for a different event name when running in a different environment. Comments?

    Hi Paul,
    As suggested in book u2018job scheduling for SAP from SAPu2019 press it is better to have multiple instances of Cronacle version (at least 2 u2013 one for development & quality and other separate one for production. This will have no confusion).
    Regarding transporting / replicating of the object definitions - it is really easy to import and export the objects like Events, Job Chain, Script, Locks etc. Also it is very easy and less time consuming to create a fresh in each system. Only complicated job chains creation can be time consuming.
    In normal cases the testing for background jobs mostly happens only in SAP quality instance and then the final scheduling in production. So it is very much possible to just export the verified script / job chain form Cronacle quality instance and import the same in Cronacle production instance (use of Cronacle shell is really recommended for fast processing)
    Regarding OSS note 895253 u2013 yes it is highly recommended to keep your central repository, processing server and licencing information on highly available clustered environment. This is very much required as Redwood Cronacle acts as central job scheduler in your SAP landscape (with OEM version).
    As you have confirmed, you are using OEM and hence you have only one process server.
    Regarding the conventions for names, it is recommended to create a centrally accessible naming convention document and then follow it. For example in my company we are using the naming convention for the jobs as Z_AAU_MM_ZCHGSTA2_AU01_LSV where A is for APAC region, AU is for Australia (country), MM is for Materials management and then ZCHGSTA2_AU01_LSV is the free text as provided by batch job requester.
    For other Redwood Cronacle specific objects also you can derive naming conventions based on SAP instances like if you want all the related scripts / job chains to be stored in one application, its name can be APPL_<logical name of the instance>.
    So in a nutshell, it is highly recommend
    Also the integration of SAP solution manager with redwood is to receive monitoring and alerting data and to pass the Redwood Cronacle information to SAP SOL MAN to create single point of control. You can find information on the purpose of XAL and XMW interfaces in Cronacle help (F1). 
    Hope this answers your queries. Please write if you need some more information / help in this regard.
    Best regards,
    Vithal

  • Java bean field naming convention

    I posted this under the Desktop -> JavaBeans, but wasn't sure if that was the right place, so I'm posting here to:
    I have an object with a field "iATANumber".
    I have getters and setters like this:
        public String getIATANumber() {
            return iATANumber;
        public void setIATANumber(String iATANumber) {
            this.iATANumber = iATANumber;
        }In my jsp I'm trying to print it out like this:
    ${foo.iATANumber}and it doesn't work. I just get nothing, while all the other fields on my object work, and it prints out the number I want if I call the getter from a scriptlet.
    Everything works great though if I change the field to iataNumber (note the change in case), and change the getter, setters and jstl to match. Then the jsp works fine.
    The getter and setter names for iATANumber were generated useing IntelliJ, are they not right, and that's why ${foo.iATANumber} won't work?
    Thanks in advance.

    The JavaBeans naming convention falls on its face if a property starts with a lower-case letter followed by an upper-case letter. The commonest way to find this problem is to call your property "eMailAddress" but you have found a different way.
    You also found a solution. Workarounds are the best you can do here.

Maybe you are looking for