Package name convention

Hallo,
Is there any recommended convention for package names? I have seen several projects using such convention that all Panels are in a *.panels package, all Events in a *.events package etc. Do you recommend such convention?
Thank you,
Ladia

If you are working for a commercial company, then the general packaging structure is
com.<my-company>.<my-product>.<my-module>
Suppose if you are working for some company "ladia" some product whose name is "portfolio" and you have the modules - view, model,config in your product, then you have to use the package structure like,
package com.ladia.portfolio.view.<my-class-name>;
package com.ladia.portfolio.model.<my-class-name>;
package com.ladia.portfolio.config.<my-class-name>;
You can have sub folders in view, model etc.. also.
Thanks,
Kalyan

Similar Messages

Package Names

This is another of my questions related with naming. My problem is that I care so much on naming of packages, classes, methods, variables, etc because I want to make my code as readable as possible.
I read from google about some standards when creating a new package. It states that it must the company domain in reverse. This means "com.companyname.xxxx" or "org.organizationname.xxxx" like "org.eclipse.xxxx" or "com.nokia.xxxx". So far so good...
My problems comes when I have to devide the application classes. I most often use the MVC. so what I do is having
org.organizationname.applicationname.view
org.organizationname.applicationname.control
org.organizationname.applicationname.model
org.organizationname.applicationname.utilHowever I am finding this a little stupid. My problem is I never seen any full application code and so I had to invent these myself. I sometimes change from .control to .business or .services.
My question is how do you usually name the packages to identify between the view, model, control classes??
I also get confused on how to set the package name for an application that will make use of a webservice. Because a webservice is a service, but you could have other things that can be a service. And you can not make your package name too long either!!

This is another of my questions related with naming.
My problem is that I care so much on naming of
f packages, classes, methods, variables, etc because
I want to make my code as readable as possible.
I read from google about some standards when creating
a new package. It states that it must the company
domain in reverse. This means "com.companyname.xxxx"
or "org.organizationname.xxxx" like
"org.eclipse.xxxx" or "com.nokia.xxxx". So far so
good...
"Must" is a very strong word. I believe "recommends" is more correct. We use the reversed URL convention for package names where I work, but it's not mandatory.
My problems comes when I have to devide the
application classes. I most often use the MVC. so
what I do is having
org.organizationname.applicationname.view
org.organizationname.applicationname.control
org.organizationname.applicationname.model
org.organizationname.applicationname.util
However I am finding this a little stupid. What's so stupid? That's the way I see it done.
I think it's only a problem if (1) you can't touch type, (2) you don't have an IDE like IntelliJ that can automatically insert the package name for you when create a class in a package, or (3) you're bothered by a bit of verbosity.
My
problem is I never seen any full application code and
so I had to invent these myself. I sometimes change
from .control to .business or .services.
My question is how do you usually name the packages
to identify between the view, model, control
classes??Yes.
I also get confused on how to set the package name
for an application that will make use of a
webservice. Because a webservice is a service, but
you could have other things that can be a service.Every service is not a web service - two different things. It's a packaging/deployment issue. The fact that you choose to deploy a particular service as a Web service doesn't change its essence.
And you can not make your package name too long
g either!!What do you mean by "too long"?
Do you have a point or a question here?
%

Wlsc problem with package name

I am using wlsc ant task to generate my java code for a web service. Unlike the simplistic examples (HelloWorld and Complex) I have my complex types split into a separate .xsd file instead of putting them directly into the WSDL file.
Is there a way to set the package name that will be generated for these types? It seems to generate everything into a java package based on the namespace (which is different than the wsdl).
The wlsc ant task has an argument called "packageName" which I am setting. The java classes for the service itself use that package, just not the types defined in the xsd file(s). :(
Thanks for any help

see SAP documentation for package naming convention:
Packages
The following namespaces are available for packages:
Package names beginning with a letter from A to S, or from U to X.
Package names beginning with these letters are reserved for objects of the SAP standard system from the SAP namespace. You cannot create customer objects or objects from prefix namespaces in these packages.
Note that the package name must be no more than 30 characters long. The name of the main package should reflect the content of the package Adjacent packages should have similar names.
The Transport Organizer records changes to objects in these packages, so that they can be transported.
These packages belong to the "SAP" transport layer and are assigned to an SAP software component (such as SAP_BASIS, SAP_APPL).
Package names beginning with Y or Z
You can create customer-specific objects from the customer namespace in these packages.
The Transport Organizer records changes to objects in these packages, so that they can be transported, provided the SAP System has been set up appropriately. (For more information, see Setting the System Change Option). These packages are assigned to the software component HOME.
So create the packages accordingly...

Package name in business content

when i am trying to activate a cube in business content,when i click install and transport,i am getting a pop up window asking for a package name
can somebody please give me some info on this,what is a package name,is it just like a folder or anything else

You can go to se80 and open any Package and F1 over the name of the package and you can see the sap Help...
Package
Packages extend the concept of development classes to improve modularization, encapsulation, and decoupling in the SAP System.
Development classes, used until now, are simple containers for development objects, provided with a transport layer that specifies how they were to be transported. As an enhancement to development classes, packages include the following attributes: nesting, interfaces, visibility, and use accesses.
Nesting is the ability of a package to include other packages within the package hierarchy.
Visibility is an attribute of package elements. A development element can be visible from outside the package. (It is always visible inside its own package, though not necessarily all the packages embedded in this package). A development element is visible externally if it is included in at least one package interface.
The use access gives a package the right to use the development elements in the package interface of another package. Note that this right is one-way only.
Package
Definition
Related objects in the ABAP Workbench are grouped together in a package. The assignment of an object to a package is entered in the object directory (TADIR). The package determines the transport layer that defines the transport attributes of an object.
The packages are entered in the table TDEVC. They can be maintained in the following transactions:
Transaction SE80 -> Enter package -> Double-click the package
Transaction SM30 - Table/view name V_TDEVC
The packages are themselves objects of the ABAP Workbench. They belong to their own packages.
In contrast to its predecessor, the development class, a package has the following additional characteristics:
Packages can be nested.
Packages can contain their 'visible development objects' (visible outside of the package) in package interfaces.
Packages can have use access defined for other package interfaces.
Use
When an ABAP Workbench object is created, the system prompts you to assign it to a package. The package should describe the area that the object belongs to.
The representation of the object tree in the ABAP Workbench (transaction SE80) uses the package as a navigation aid. If there are more than 100 objects of a certain type (that is, ABAP programs), the object tree can no longer be clearly represented and it becomes increasingly difficult to use the ABAP Workbench. In this case, we recommend creating new packages with the same transport layer and distributing the objects to the new packages on the basis of the areas they belong to.
The following naming conventions for packages determine the packages' functions:
Package begins with A-S or U-X:
These packages are for SAP standard objects. Customer objects cannot be created in them. Changes to objects of these packages are recorded by the Transport Organizer (Request management) and can be transported (see field transport layer.
Package begins with Y or Z:
Customer objects can be created in these packages. Changes to objects in these packages are recorded by the Transport Organizer (Request management). The objects can be transported to other SAP Systems (see the field transport layer ).
Package begins with T (private test package):
When you create a package of this type, you can specify whether you want changes to be recorded. If so, objects that are edited are recorded in local requests by the Transport Organizer. This package does not belong to a transport layer. Objects can only be transported to other SAP Systems if a transport request is created.
Package begins with $ (local package):
Changes to objects are not recorded by the Transport Organizer. The package does not belong to a transport layer. The objects cannot be transported.
Package begins with a namespace prefix:
If you have reserved a namespace, then you can create packages (and other objects) whose names begin with the namespace prefix.
(Example of a namespace prefix /COMPANY/, example of a corresponding package /COMPANY/DEVCLASS)
Changes to these packages are recorded by the Transport Organizer, and can be transported.

Mapping namespace to generated package name (clientgen)

Hello,
We have a need to map the namespace of the generated bean artifacts from clientgen to a different package name. This could be done prior to weblogic 10 with the typePackageName attribute of clientgen but this is no longer supported in weblogic 10. Is there another way to do this? Note we cannot change the namespace of the webservice wsdl we are generating the client for.
Thank you!
Julia Allen

Use the <binding> child element to specify one of the following:
* For JAX-WS, one or more customization files that specify one or more of the following:
o JAX-WS and JAXB custom binding declarations. For more information, see “Customizing XML Schema-to-Java Mapping Using Binding Declarations” in Getting Started With WebLogic Web Services Using JAX-WS.
o SOAP handler files. For more information, see “Creating and Using SOAP Message Handlers” in Programming Advance Features of WebLogic Web Services Using JAX-WS.
* For JAX-RPC, one or more XMLBeans configuration files, which by convention end in .xsdconfig. Use this element if your Web Service uses Apache XMLBeans data types as parameters or return values.
The <binding> element is similar to the standard Ant <Fileset> element and has all the same attributes. See the Apache Ant documentation on the Fileset element for the full list of attributes you can specify.
Note: The <binding> element replaces the <xsdConfig> element, which is deprecated as of version 10.0 of WebLogic Server.
See here for detail.

Standard for package names

Hi,
There is some standard convention for naming a package?
I've seen before that they use to name it something like this:
com.<companyname>.<blah>.<blah>.<blah>
This is correct?
Thanks in advance,
Gabriel

The general pattern promotoed by sun is to start package names with the reversed form of your domain name.
For instance
com.java....
com.ibm....
org.w3c...
org.omg...
If you don't have a domain name (small company or independent developer) you should use some unique value based on your name, your email address, etc.
Chuck

Package name when the doman name contains "-"

Recently I'm working for a project for a company whose domain name like www.my-donkey.com. By convention, the Java package name should start with com.my-donkey.xxx, unfortunately the hypen is not allowed in the package name.
What is the standard Java convention to address this?

Remember that the package naming convention is exactly that: a convention. It isn't a rule, nothing checks them and you don't have to follow it. It was just an idea that someone came up with to make it less likely that package names from different organisations would collide. Go with Kaj's idea, package names don't have any legal ramifications or anything

I need to remove "air." from package name. I'm get a Layout xml error when repackaging android app..

So, i'm doing this on my own app. I made an update for an older app that was build using Native Android. But this time, i used Adobe AIR... The catch is Adobe likes to append a "air." to the front of your package name without asking you. So basically I can't upload my update because it has a new package name is now "air.com.mycompany.myapp" rather than the original "com.mycompany.myapp"
Basically I'm going through this guide..
http://helpx.adobe.com/air/kb/opt-out-air-application-analytics.html
I followed all the steps, made all the adjustments to the androidmanifest.xml like it asks.
But after going along with the above guide, with no issues when i get to the step that says
"Run the following command to create the resource file for the updated AndroidManifest.xml:"
I run this..
    "/Users/brybam/Documents/eclipse/android-sdk-mac_x86/platform-tools/aapt" package -f -M AndroidManifest.xml -F resources.arsc -I "/Users/brybam/Documents/eclipse/android-sdk-mac_x86/platforms/android-8/android.jar" -S ./res
But I keep getting the same error regarding the xml files in res/layout
    ./res/layout/expandable_chooser_row.xml:1: error: Error parsing XML: not well-formed (invalid token)
    ./res/layout/expandable_multiple_chooser_row.xml:1: error: Error parsing XML: not well-formed (invalid token)
    ./res/layout/main.xml:1: error: Error parsing XML: not well-formed (invalid token)
    ./res/layout/multiple_file_selection_panel.xml:1: error: Error parsing XML: not well-formed (invalid token)
    ./res/layout/ssl_certificate_warning.xml:1: error: Error parsing XML: not well-formed (invalid token)
The guide doesn't say anything about these xml files, and im not sure what to do with these or how to handle them.
If i go into the res/layout folder, and just delete these (i know they're necessary. But i just deleted them as a test, to get through the rest of the guide...)
I was able to get through the rest of the steps in the guide fine, make an apk, and put it on my phone...only to find out the app will crash the moment you try to run it. Probably because i deleted the layout xml files...But i cant get the command i need to run above to accept them!
So, earlier in the guide they have me use thing thing called the "AXMLPrinter2.jar" to make the AndroidManifest.xml readable so i can edit it.
I run something like this:
    java -jar "/Users/brybam/Desktop/repackage/AXMLPrinter2.jar" AndroidManifest.xml > AndroidManifest.xml.bk
This makes a new file "AndroidManifest.xml.bk" and i can edit that.
So, I was thinking with all of these layout xml files, maybe I could run this "AXMLPrinter2.jar" on them and then edit them. Because right now if you open them they're not human readable, and its hard for me to work on them if they're not...
I tried this thinking i could do the same thing...
    java -jar "/Users/brybam/Desktop/repackage/AXMLPrinter2.jar" main.xml > main.xml.bk
Just get a blank file and a console erorr when trying to use the AXMLPrinter2.jar on the layout xml files...
    java.lang.ArrayIndexOutOfBoundsException: 67
              at android.content.res.StringBlock.getShort(StringBlock.java:231)
              at android.content.res.StringBlock.getString(StringBlock.java:91)
              at android.content.res.AXmlResourceParser.getName(AXmlResourceParser.java:140)
              at test.AXMLPrinter.main(AXMLPrinter.java:56)
So, I think my whole issue is based around these XML files not being converted to human readable before i try and re-package....
EDIT:::
Ok, so I found a site that talks about the error I'm getting but it's in chinese, and even after translating the page...I'm still not well versed with terminal and this stuff to get it.
It reads:
"Error.
Final conclusion:
In minSdkVersion <= 7, AXMLPrinter2.jar can normally decompile xml file
Greater than 7 can not be normal decompile xml file (AndroidManifest.xml except)
Give way to share a batch decompile xml file:
First, create a *. Txt file
Stresses inside the content authoring
for / r layout%% a in (*. xml) do @ java-jar AXMLPrinter2.jar "%% a" >> "%% a". txt
Then this txt file extension into bat form, and this BAT the file and AXMLPrinter2.jar on the same directory will be decompiled xml into the layout directory
Decompilation results can be generated by executing the bat file multiple xml files."
- http://hi.baidu.com/ghcghc/item/ecbaa1ce997cb225a0b50ac2
Maybe someone with more know-how could explain what they're explaining? I get that he's saying the issue im seeing appears when you're using minSdK <=7 but I need to use minSdk 8. Does anyone understand this work around? And how I might go about it on a Mac with terminal?
I wish adobe would make it easy to remove the "air." from the package name. If they want to convert old Native devs to AIR devs...the transition needs to be seamless. But now I'm about to have to go back to Native because I can't update an app I already have out on the market with an air app.

Hello~
     I also tried to remove "air." package name in air application. And i encounter the same problem.
     I do not find any solution to decode the xml inside res folder by AXMLPrinter2.jar. And those xml inside is compressed which is unreadable.
     However, what you can do is copying the structure of res folder. And go to your air sdk file path - adobeair-sdk-folder/lib/android/lib/resources/
     Replace those file exists in your res folder. And copy "values" folder to your res folder.
     Hope this solve your problem~

Class name and package name clashing

When i have a class and a package with the same name, I cannot access classes in the package. For example I have 3 classes and 1 package as below
- Test.java
- PackageName.java
+ PackageName // this is a directory
- MyClass.java
Below are the codes of .java files
Test.java
=======
public class Test { PackageName.MyClass a = new PackageName.MyClass ();}
PackageName.java
===============
public class PackageName{ }
MyClass.java
==========
package PackageName; public class MyClass { }
I can compile PackageName.java and MyClass.java but not Test.java. It says
cannot resolve symbol
symbol : class MyClass
location: class PackageName
PackageName.MyClass a = new PackageName.MyClass ();
But if I remove the PackageName.java, I can compile Test.java perfectly. I think when I use PackageName.MyClass, java thinks that I try to access an inner class MyClass of PackageName class, and that does not exists. Is there any way to solve this ambiguation, other than making the package name and class name different? Thank you very much.

This works fine: just add an import to Test.java.
import PackageName.MyClass;
public class Test
    public static void main(String [] args)
        MyClass a = new MyClass();
public class PackageName {}
package PackageName;
public class MyClass {}It's a pretty wacky, useless example, but it works.
Plus I thought inner classes would have a dollar sign in their .class file names. When I compile this:
public class OuterClass
    public static void main(String [] args)
        OuterClass outer = new OuterClass();
        System.out.println(outer);
    public String toString() { return "I'm an OuterClass"; }
    class InnerClass
        public String toString() { return "I'm an InnerClass"; }
}I see two .class files: OuterClass.class and OuterClass$InnerClass.class
Why make up examples like this? It's hard enough writing code, and it's easy to disambiguate for the compiler.

How to change the package name of Managed Bean class

Hi: Gurus, when ever I create a new JSP page the Creator creates a code behind file with a package name untitled. Is there any way to change this package name? Can't the Creator gives us an option before genereating manged bean page to choose a package name? And then create the Java source directory structure on the basis of the pakcage name?
Regards,
Rashid.

In the Project Navigator (default location is middle right), go to Java Sources, and you can rename the package ("untitled") to something else by right-clicking it or by left-clicking (just like Windows Explorer).
I agree, though, that giving the developer an option during creation of the JSP page would be nice.

The package name The Gallbladder-4.itmsp contains an invalid character(s). The valid characters are: A-Z, a-z, 0-9, dash, period, underscore, but the name cannot start with a dash, period, or underscore

I have an iBook on itunes and I am trying to upload a new version of the book. I am following the workflow through iBooks Author and when I fell out all of the infromation for the package on iTunes producer i then hit the deliver button and I get the following error message:
The package name The Gallbladder-4.itmsp contains an invalid character(s). The valid characters are: A-Z, a-z, 0-9, dash, period, underscore, but the name cannot start with a dash, period, or underscore.
As far as I can tell the file that is being referenced does not meet the criteria axpressed in the erro message and in fact that file has been created by iBooks Author so one would think there shouldnt be an error.
I also get the following to error messages:
Apple's web service operation was not successful
Unable to authenticate the package: The Gallbladder-4.itmsp
Would ove any help.
Thanks,
Jeff

Thank you so much for your help.
For anyone that would like to check out this book it can be downloaded at:
https://itunes.apple.com/us/book/the-gallbladder/id598317335?ls=1
Please check out our free medical education blog by Jeffrey Eakin using iBooks Author at:
http://free-medical-education-ibooks-author.blogspot.com

Difficult to get good package names with ojspc in automated build

If I understand the documentation for "ojspc" correctly, there is an aspect of its functionality that makes it difficult to have a convenient automated build which can also get good package names for the generated Java source files.
If you don't specify the "-packageName" option, ojspc will build a package name relative to the current directory, including sub-directories. However, specifying "-packageName" will ONLY use that package, and will not create sub-packages associated with sub-directories.
If you don't use the "-packageName" option, then you have to run the build from the root directory of your JSP files. When you're running an automated build with ANT, it's not convenient to do this.
The likely result of this is that I would have to make sure that all of my JSP files are named differently, even if they're in different directories, and use the "-packageName" option to specify a particular package name for all of the generated source files.

After more careful reading, I realized that using the "-appRoot" option (without using "-packageName") makes it possible for an ANT build to generate good package names (with directories).
The following note, however, in the ojspc documentation is kind of odd:
"It is advisable that you run ojspc once for each directory of your JSP application, so files in different directories can be given different package names, as appropriate."
I assume this is referring to using the "-packageName" option. If you don't need to use "-packageName", especially if you have multiple directories of JSP pages, it is much easier to just let ojspc pick the package names.

Not allowed to import classes without package names?

Hi,
I have a few questions on Packages and importing?
1. Is the following true that it is illegal to import classes in the same package as the current class, will this cause a comilation error? If this is the case where in the Java Language specification is this actually written as I could not find it?
2. This has probably been answered by question 1 but if I have 2 classes in the same package and if I import 1 of the classes into the other class, is it illegal to import it by just using the class name and not the package name as well, ie
if the package name is ie.tcd
and the 2 class names are exp1.class and exp2.class, can I do this in class 2
package ie.tcd;
import exp1;
public class exp2 {
3. Is it illegal to import classes that are not explicitly part of any package or must a class be part of a package to be imported. I read somewhere that while this was always illegal it is only after jdk 1.4.2 that this is being enforced? If this is the case where in the Java Language specification is this actually written as I could not find it either?
Thanks very much for any help,
John

Was just also wondering, 1 other thing, I am looking
at someone elses code they have 2 classes (Class A
and Class B) in the same package (pkg). The person
imports class A into B:
package pkg;
import A;
public class B {
Is this legal code (or was it ever)?Not if A is really in pkg.A. If there is an A in the unnamed package it was legal, or at least it was understood by the compiler, and now it isn't (to both).
Can you import or is there a point in importing a class in the same
package?Only by naming the package in the import statement. If the current and the import statement are in the same package the import is redundant.
If there is a point would you import just be
using the class name (this would be illegal after jdk
1.4) or should you use the whole package name even
though it is in the package anyways?As I understand it you must always use the whole package name in imports.

Package name in Solaris 10

Hi,
I try to uninstall the following path:
/usr/spool/lp/model/ppd/system/foomatic
for all the printer model files.
Is there a Solaris 10 Package name associate with these files that I can use pkgrm to do?
Thanks!

You can get the associated package name by running:
grep lp\/model\/ppd\/system\/foomatic /var/sadm/install/contents | awk '{ print $10 }' | sort -u

How to get the package name of a procedure used in a process flow activity

Hi all. I'm on OWB 11.2.0.2.0.
When I used a packaged procedure or function in a mapping operator, I can find out the package.program_unit name by getting the operator's FUNCTION_NAME property. For example,
OMBRETRIEVE MAPPING '$mapName' OPERATOR '$operName' GET PROPERTIES (FUNCTION_NAME)
But when the same is used in a process flow activity, I can't find a property name that will give me the same information. I can get the BOUND_NAME, it does not tell me the package name. It must be stored in the activity properties because when you pull up the Synchronize dialog for the activity, it knows the package name.
Is there a way to get this via an OMBRETRIEVE?
Thanks.

ANA, this is exactly what I needed. Thank you so much. I saw REFs also in the OMBRETRIEVE MAPPING/OPERATOR syntax, but went cross-eyed trying to figure out if I could use the same there. The closest I found was GET BOUND_OBJECT.
Thanks again!

Package name convention

Similar Messages

Maybe you are looking for