instantiation

In my CakePHP 2 application I have such vendor. I need to create an instance of this vendor class inside my controller class. So I will use that instance inside my controller's different functions. App::import('Vendor', 'fancyVendor', array('file' => 'fancyVendor.php')); class MyController extends AppController { public $fancyVendor; function beforeFilter() { $fancyVendor = new fancyVendor(); $fancyVendor->setValue("12"); } function showMe() { echo $fancyVendor->getValue(); } } Inside my showMe function, I can't get the value that I set inside my beforeFilter function. Is there a proper way to

While there are countless resources on Application, Activity etc lifecycle seen from an API perspective ( onCreate/Destroy/Whatnot() methods) there is scarcely any information on the actual object's lifecycle for these components from the Java perspective . So for instance I saw (on a YouTube marakana video) that services are basically singletons - and this left me wondering on the state of an IntentService - can it be shared ? Or is this a singleton too ? I guess initially a process is created (by Zygote ?), along with a DalvikVM instance and then the classes for all components that are

I'm using the android version of cocos2d located here: https://github.com/ZhouWeikuan/cocos2d I'm an iPhone guy checking out android who already has familiarity with cocos2d iPhone. Ideally i would be able to create the particle from a plist file in the package/bundle. I can't seem to even get the "premade" default style particles working ie CCParticleFireworks (I've only tried in the simulator though). I was disappointed that there is very little sample code out there for cocos2d android so if anyone has a good resource on this I would be interested as well. I'm just learning java as well so

I am getting RuntimeException Enum types may not be instantiated I don't know why. What I want is to identify a year by an integer value like i have 9 so the year for other Methods is 2006. Code: public class P21Make { enum Catalog { year2005(9),year2006(12),year2007(15),year2008(18), year2009(21),year2010(23),year2011(25),year2012(28), year2013(31),year2014(33),year2015(36),year2016(39), year2017(42),year2018(45),year2019(48),year2020(51); private int id; Catalog(int c){ this.id=c; } } public P21Make() { Catalog c = new Catalog(9); // The Exception } } You cannot instantiate enum like this .

I've got a problem with VB6. I have a form with several ComboBox objects on it. I wish to populate the ComboBoxes via a function that takes a SQL query as a parameter. So the code looks like this Private Function FillComboBoxFromMDB(ByVal sDBName As String, _ ByVal sSQL As String) As ComboBox '/* ' * Execute SQL in MDB and fill the ComboBox with the results ' * Returns filled ComboBox ' */ Dim DB As Database Dim DBRecordset As Recordset On Error GoTo FillComboBoxFromMDB_ErrHandler Set DB = OpenDatabase(sDBName, False, False) If Not DB Is Nothing Then Set DBRecordset = DB.OpenRecordset(sSQL) If

I'm working with a domain, view and controllers. Each containing their own classes. The domain contains a lot of classes that should not be instantiated in classes outside of the domain. I was under the impression the default access modifier was going to help me. Making my domain classes their constructors package visible. Turns out any class can still use the constructors after importing the right package.class file. How can I prevent this from happening? When you say 'Turns out any class can still use the constructors after importing the right package.class file.' I guess you are talking

Recently, I have been working with XML parsers. This is just beginning for me and I managed to understand how to use DOM parser classes in java i.e. DocumentBuilderFactory and DocumentBuilder to parse an XML document. DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance(); DocumentBuilder db = dbf.newDocumentBuilder(); What I am asking myself is how come an abstract classes, such as DocumentBuilderFactory and DocumentBuilder , are allowed to instantiate new instances? And then in another example I see: Calendar calendar = Calendar.getInstance(); System.out.println(calendar.get

which declaration/instantiation is better and WHY ? public class MainWindow { private Test _test; public MainWindow() { _test = new Test(); } } OR public class MainWindow { private Test _test = new Test(); public MainWindow() { } } Ask yourself this question: what happens when you add other constructors to MainWindow ? Do you want to then have to remember to invoke other constructors to ensure that _test is correctly initialized? Or is it okay for _test to not be initialized if another constructor is used? Personally when creating a UI component I would move as many points of failure out of